Draft a Now/Next/Later Quarterly Roadmap Tied to One Outcome Metric
You get a one-quarter roadmap grouped into Now, Next and Later, with every item linked to your outcome metric, a confidence level, a leading signal and parked items.
Prompt
You are a senior product manager who builds outcome-based roadmaps for small and mid-size product teams.
Your job: turn my goals and initiatives into a one-quarter roadmap grouped as Now / Next / Later, not a dated feature list.
First ask me these questions in one message, then wait for my answers:
1. What is the product and who uses it?
2. What is this quarter's main outcome metric, with current value and target?
3. What initiatives or ideas are on the table? (A rough list is fine.)
4. What team capacity and fixed constraints do you have?
Rules:
- Every item names the metric it moves and the expected direction; items that move nothing go to Parked.
- Now holds at most 3 items the team can start within 4 weeks with current capacity.
- Next and Later items are written as problems to solve, not features.
- No delivery dates; use confidence levels (High, Medium, Low) instead.
- Each item lists one leading signal to check within 2 weeks of shipping.
Output format:
1. Outcome statement: metric, baseline, target in one sentence
2. Table with columns: Horizon | Item | Problem it solves | Metric it moves | Confidence | Leading signal
3. Parked: each item with a one-line reason
4. Top 3 risks or dependencies
End with one line naming the biggest assumption and the data needed to confirm it.Example output
Tips and common edits
Why this works
- Requiring every item to name the metric it moves forces cuts and makes the Parked list as useful as the roadmap.
- Confidence levels instead of dates stop the roadmap from turning into promises the team can't keep.
- Writing Next and Later as problems keeps scope open until the team has learned from the Now items.
Use before quarterly planning or a stakeholder review. Have your target metric, its current value, a rough initiative list and team size ready. Works in ChatGPT, Claude or Gemini.
Common edits
- Add a column for owner or team if several squads share the roadmap.
- Ask for a one-slide summary version for executive or board updates.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Design an A/B Test Plan with Sample Size Math and Pre-Set Stop Rules
Get a complete A/B test plan with one primary metric, a clear hypothesis, a worked sample size calculation, runtime, and stop rules fixed before launch.
Diagnose a Sudden Metric Drop with a Ranked List of Likely Causes
Get a ranked table of likely causes for a metric drop, covering tracking, segments, platforms, releases, seasonality and external factors, each with an exact check.
Run a Post-Launch Retrospective Comparing Goals to Actual Results
Get a blameless launch retrospective with a goal-versus-actual table, facts kept apart from causes, and lessons that each carry an owner and a change for the next launch.
Write a Go-to-Market Launch Plan with Owners, Dates and Go/No-Go Criteria
Get a tiered launch plan with a T-minus timeline, one owner role per task, measurable go/no-go criteria, an hour-by-hour launch-day checklist and week-one metrics.
Write an Event Tracking Plan Where Every Event Maps to a Success Metric
Get a tracking plan table with object_action event names, exact triggers, typed properties and the success metric each event feeds, plus a list of events to cut.
Build a Competitor Feature Comparison and Positioning Summary
Get a feature comparison table with every cell tagged as user-provided or needing verification, plus win/lose points, a positioning statement and a fact-check list.