Build a quarterly project roadmap

Create a quarter-level roadmap that aligns multiple workstreams, resources, and stakeholders around a 90-day delivery plan.

Workflow · Project ManagementRole · Program Manager●●● AdvancedUpdated 2026-07-31

The prompt

Copy and customize

prompt.txt
**Role:** You are a Program Manager building the {quarter} quarterly roadmap for program {program_name}.

**Context:**
A quarterly roadmap sits between strategic vision and daily execution. It gives leadership confidence in the delivery plan while giving teams enough flexibility to handle unexpected challenges. Good quarterly roadmaps show the sequence of major milestones, dependencies, and resource allocation — not individual tasks.

**Task:**
Build a comprehensive quarterly roadmap that serves as the single source of truth for {quarter}. Apply tree-of-thoughts: consider sequencing trade-offs — which milestone order minimizes risk? Which sequencing maximizes early value delivery?

**Input Available:**
- {program_name}: Program or initiative name
- {quarter}: Quarter being planned (e.g., Q3 2026)
- {strategic_objectives}: 2–3 organizational objectives this program contributes to
- {workstreams}: List of workstreams with their leads and current status
- {key_milestones}: Major deliverables expected this quarter
- {resources}: Team headcount and budget available
- {known_constraints}: Holidays, dependencies, external events, regulatory dates
- {carryover_from_last_quarter}: Unfinished items from last quarter

**Output Format:**
1. Quarter summary: Headline deliverables and success criteria (3–5 items)
2. Gantt-style timeline by month: Workstream | Month 1 | Month 2 | Month 3 (text-based)
3. Milestone table: Milestone | Owner | Target Week | Dependencies | Risk Level
4. Resource allocation summary: Who is doing what in which month
5. Key decisions required this quarter: Decision | Who decides | By when
6. Risks and mitigation for the quarter
7. What is explicitly NOT in scope this quarter (to manage expectations)

**Guardrails & Quality Control:**
- Milestones must be deliverables, not activities — 'launch X' not 'work on X'
- Every milestone must have a single owner
- Include carryover items prominently — hiding them creates false optimism
- Flag if the roadmap is overloaded: a good quarter plan has 20% slack for unplanned work
- 'Not in scope' is as important as 'in scope' — be explicit

How to use

Run this prompt in four steps

  1. 1Run this 2–3 weeks before the quarter starts to allow for stakeholder review.
  2. 2Validate resource allocation with team leads before finalizing.
  3. 3Share with all workstream leads and get explicit commitment to milestones.
  4. 4Review the roadmap mid-quarter and adjust as needed — treat it as a living document.

When to use

When to use this prompt

Use at the start of each quarter for any program with multiple workstreams or teams.

Limitations · Worth knowing

This prompt has limitations you must understand.

AI cannot know your organization's informal constraints — political priorities, team morale issues, or upcoming organizational changes. Supplement with human context.