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

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

At a glanceNow / Next / Later roadmap for activationGoal: first invoice within 7 days from 31% to 40% this quarter
  1. Prefilled sample invoiceNowHigh confidence; fixes the blank-form drop-off
  2. Cut sign-up fields from 9 to 4NowHigh confidence; lifts sign-up completion
  3. Day-2 walkthrough emailNowMedium confidence; brings day-1 leavers back
  4. Logo and payment details setupNextMedium confidence; invoices look professional
  5. Card payments from the invoiceNextMedium confidence; depends on provider review
  6. Spreadsheet client importLaterLow confidence; speeds setup for many clients
  7. Mobile invoice sendingLaterLow confidence; helps phone sign-ups finish

Example for: a B2B invoicing app for freelancers, 4 engineers and 1 designer, aiming to raise new-user activation.

1. Outcome statement

Raise the share of new sign-ups who send their first invoice within 7 days from 31% to 40% by the end of the quarter.

2. Roadmap

HorizonItemProblem it solvesMetric it movesConfidenceLeading signal
NowPrefilled sample invoice on first loginNew users face a blank form and leaveActivation ↑High% of new users who open the sample within session 1
NowCut sign-up fields from 9 to 4Drop-off between sign-up and first screenActivation ↑HighSign-up completion rate
NowDay-2 email with a 60-second invoice walkthroughUsers who leave on day 1 rarely returnActivation ↑MediumEmail click-to-invoice-start rate
NextUsers don't know how to add their logo and payment detailsInvoices look unprofessional, so users hesitate to sendActivation ↑MediumShare of first invoices with logo added
NextClients can't pay by card from the invoiceFreelancers stall when clients ask how to payActivation ↑, payment time ↓MediumCard payments on first invoices
LaterFreelancers import clients from spreadsheets by handSetup takes too long for users with many clientsActivation ↑LowImport starts per new account
LaterNo mobile way to send an invoice on the goUsers who sign up on phones don't finishActivation ↑ (mobile)LowMobile sign-up to first-send rate

3. Parked

  • Dark mode: requested often, but no link to activation.
  • Multi-currency reports: serves existing power users, not new users.
  • Accounting software sync: high effort; revisit after Next items prove out.

4. Top 3 risks or dependencies

  1. Card payments depend on the payments provider's review, which can take several weeks.
  2. The designer is shared with marketing for 2 weeks in month one, which may slow the sample invoice.
  3. The activation event is logged client-side; ad blockers may undercount it.

Biggest assumption: blank-form friction, not lack of intent, is the main reason users don't send an invoice. Confirm with 8 to 10 short calls with non-activated users and a funnel view of where they exit the invoice form.

Written by AI from this prompt. Your results will vary.

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 in Product Management