Build an integrated program roadmap across workstreams
Combines several workstream plans into one roadmap showing milestones, cross-workstream dependencies, and integration points.
The prompt
Help me build an integrated roadmap for a program with several workstreams.
Program goal: [OUTCOME and target date]
Workstreams: [LIST each with its lead, scope, and key milestones with dates]
Known dependencies between workstreams: [e.g. "Training can't start until the system is configured"]
External dates: [regulatory deadlines, contract dates, business calendar events, freeze periods]
Planning horizon and granularity: [e.g. "18 months, by month"]
Steps:
1. Lay out each workstream's milestones on a common timeline.
2. Map cross-workstream dependencies and check each one: does the provider's date land before the consumer needs it? Flag conflicts and tight handoffs (less than 2 weeks of buffer).
3. Identify integration points - moments where outputs from several workstreams must come together (e.g. end-to-end testing, launch readiness) - and treat these as program-level milestones.
4. Find periods of overload where several workstreams peak at once and compete for the same people or approvals.
5. Suggest program-level checkpoints for leadership review.
Rules: keep each workstream's dates as given; flag problems rather than silently moving dates. Mark any assumption as [ASSUMED].
Return:
1. A roadmap table: period | workstream | milestone | depends on | integration point?
2. A dependency list with status: OK / tight / conflict.
3. The top 5 program-level risks from the roadmap.
4. A one-page summary view for executives: phases, major milestones, and decision points.
5. A description of how to draw it as a swimlane chart.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- OUTCOME and target date
- LIST each with its lead, scope, and key milestones with dates
- e.g. "Training can't start until the system is configured"
- e.g. "18 months, by month"
- ASSUMED
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Build evaluation criteria and a scoring plan for a public solicitationWeighted, defensible proposal evaluation criteria, scoring guides, and evaluator instructions that hold up if a bidder protests.
- Plan a CACFP-compliant weekly menu for my childcare programA Monday-to-Friday menu with age-based portions, required meal components, and seasonal produce that meets USDA CACFP meal patterns.
- Write a procurement category strategyA sourcing plan for a spend category: market, needs, options, and roadmap.
- Build an AI adoption roadmap for my team or functionA phased plan for adopting AI in sales, marketing, HR, finance, legal, engineering, support, or operations — with use cases, guardrails, and metrics.