Given my draft roadmap and quarter context below, write a roadmap rationale memo. Use this structure:
1. Rationale: one paragraph. Why these priorities, in the order shown. Anchor to evidence (data, customer feedback, business constraint).
2. Pushback 1 (skeptical exec): name the most likely exec-level objection. Pre-answer it.
3. Pushback 2 (frustrated engineer): name the engineering objection (scope, sequencing, technical debt). Pre-answer it.
4. Pushback 3 (missed-out PM): name the objection from a peer PM whose work got de-prioritized. Pre-answer it.
Each pre-answer must acknowledge the pushback before responding to it. Reframe, don't dismiss.
My draft roadmap and context:
{{roadmap_and_context}}
Roadmap rationale memo
Add to PromptPaste
Download PromptPaste for MacDownload PromptPaste for iPhoneDownload PromptPaste for iPadDownload PromptPaste for Mac & iPhone
the prompt
Example output
Rationale: We're prioritizing the cross-device sync work this quarter over the new analytics dashboard because (1) the sync gap is the #1 churn reason in the last 50 churned-power-user interviews, (2) the eng work for sync is mostly known (8 weeks, 2 engineers), and (3) the analytics dashboard requires a redesign that's still in discovery. Sync is high-confidence high-impact; analytics is medium-confidence medium-impact.
Pushback 1 (skeptical exec): 'Sync feels like infrastructure, not growth. Where's the new acquisition surface?'
Pre-answer: Retention math says a 5% reduction in power-user churn equals ~3 months of acquisition output at current spend. Sync is growth, just retention-shaped.
Pushback 2 (frustrated engineer): 'You're putting us on iCloud sync again - we burned a quarter on this in 2025.'
Pre-answer: 2025 attempted CloudKit; this round uses the simpler app-group + UserDefaults approach. Confirmed feasible by infra Tuesday. Scope is intentionally narrower.
Pushback 3 (missed-out PM): 'My team's analytics work gets pushed - what does my Q3 look like?'
Pre-answer: Analytics work moves to Q3 with the design discovery starting in Q2 week 8. No team is idle; the sequencing reflects discovery readiness, not priority of the surface.
Common mistakes
Don't list more than three pushbacks - if you list six, none of them feel load-bearing and the memo loses focus. Pick the three you actually expect. Also: do not write a pre-answer that's a defense rather than an acknowledgment. 'Sync is growth, just retention-shaped' is a reframe that respects the pushback. 'Sync is obviously growth' dismisses it. The model will sometimes default to dismissive pre-answers - rewrite those by hand.
More from AI Prompts for Product Managers
PRD draft from a one-line problem
Act as a senior product manager. I'm going to give you a one-line problem statement. Before drafting any PRD, do this: 1. State the…
Customer interview synthesis
Read the raw customer interview transcripts below. Produce: 1. The top 5 themes ranked by frequency (number of interviews where the theme…
Stakeholder weekly update
Convert my raw bullets below into a weekly stakeholder update. Use exactly three sections: 1. Shipped: each item with a one-line outcome,…
Why it works
Roadmap memos are the prompt PMs are most likely to outsource to AI badly. The mistake is asking for 'a roadmap rationale' and getting a generic strategy doc that doesn't anticipate the actual pushbacks. This prompt produces a memo built to survive review: it states the rationale in one paragraph, names the three most likely pushbacks (from a skeptical exec, a frustrated engineer, a missed-out PM), and pre-answers each. The pre-answer pattern is the differentiator - it forces the memo to address the actual debate rather than just present the conclusion. PMs who do this well find their roadmap reviews shorter and decisions sticker. Tested cleanest on Claude Opus 4.7.