Dependency And Risk Register For A Release
Builds a release risk register mapping dependencies, likelihood, impact, owners, and contingency triggers.
Prompt
ROLE: You are a release-driving PM who keeps cross-team launches on track by managing dependencies and risk proactively. CONTEXT: Release: [RELEASE_NAME]. Target date: [DATE]. Teams/systems involved: [TEAMS_SYSTEMS]. Known dependencies and unknowns: [DEPENDENCIES]. Critical path notes: [CRITICAL_PATH]. TASK: 1. Inventory dependencies: internal teams, external vendors/APIs, data migrations, legal/compliance, and infra — note which are on the critical path. 2. Build a risk register: for each risk, rate likelihood (L/M/H) and impact (L/M/H), compute a priority, and assign an owner. 3. For each high-priority risk, define a leading indicator (early warning) and a contingency plan with a trigger condition. 4. Identify the single biggest schedule risk and the decision point at which you'd cut scope or move the date. 5. Recommend a go/no-go checklist for the release decision. OUTPUT FORMAT: Dependency map, Risk register table (Risk | Likelihood | Impact | Priority | Owner | Early Signal | Contingency), Biggest schedule risk note, Go/no-go checklist. CONSTRAINTS: Every risk gets an owner and a contingency, not just a description. Be explicit about the critical path. Recommend de-scoping options before slipping dates.
How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Product Management
Pressure-Tested Product Requirements Document
Drafts a complete, engineering-ready PRD with problem framing, scope boundaries, success metrics, and explicit non-goals.
RICE Prioritization Scoring Engine
Scores and ranks a backlog using RICE with transparent assumptions, sensitivity flags, and a defensible recommendation.
Jobs-To-Be-Done Interview Synthesis
Turns raw user interview notes into JTBD job statements, forces of progress, and prioritized opportunity areas.
Quarterly Product Roadmap Narrative
Builds an outcome-driven quarterly roadmap organized by themes and bets, with confidence levels and dependencies surfaced.