Frame Your Roadmap for the Room That's About to Review It
The same roadmap lands differently with execs, engineers and customers. Give Claude your draft and audience, and get the reframe and the hard questions.
Shadman RahmanPrincipal PMCapture meetings without lifting a finger
Granola uses AI to transcribe and summarize your meetings automatically. Pair it with Claude Code via MCP to turn meeting notes into action items, tickets, and code.
Try Granola freehow it works
01 / 06
Roadmap review with the exec team is in two days.
You have a roadmap. You're not sure it's framed for the people in that room. Different audiences care about completely different things.
02 / 06
You paste the roadmap and audience context into Claude.
The items, the rough sequencing, the tradeoffs you made, and who'll be in the room. Claude doesn't need a formatted deck.
03 / 06
Claude asks what decision this review needs to produce.
Approval, input, alignment, or awareness: each requires a different presentation structure.
04 / 06
Claude rewrites the framing for that audience.
Execs want outcomes and tradeoffs. Engineering wants sequencing rationale. Sales wants what they can promise. Same roadmap, completely different framing.
05 / 06
You prepare for the hard questions Claude anticipates.
The 'why not X instead of Y' question. The 'what about the thing we agreed to in Q1' question. You know the answers. Claude helps you prepare them.
06 / 06
You walk in knowing what you need from the room.
Not 'let me know if you have questions.' A specific ask, a clear structure, and no surprises.
The prompt
Paste this into Claude.ai with your roadmap and the audience context. You don't need a polished deck. A bulleted list of planned work is enough.
Click a violet field and type your own details, then copy.
What you get back
Narrative reframe for this audience
For an exec audience, lead with the business problem each item solves, not the feature itself. "Redesign checkout" becomes "close the 28-point gap between mobile traffic and mobile conversion, which represents approximately $2.4M ARR at current volumes." That's the sentence that gets attention.
Structure the presentation as three strategic bets, not a feature list:
- Bet 1 (Q2): Convert the existing mobile traffic we're not capturing
- Bet 2 (Q3): Build the retention loop that makes acquired users return
- Bet 3 (Q4): Expand into the enterprise segment Sales has been priming
Everything else is execution detail. Don't lead with it.
Anticipated hard questions
CEO: "Where's the AI feature we talked about in January?" This didn't make the roadmap. Prepare the answer now: "It's on the list and it's the right bet long-term. We pushed it to Q4 because it depends on the retention loop we're building in Q3. Doing it in Q2 would mean building on an unstable base and reworking it. That's the sequencing call." If you don't have a strong sequencing argument, this will be the toughest moment.
CTO: "Q3 is aggressive given the migration that's already scheduled." They're right to flag this. Your answer: "The Q3 items are parallel workstreams — the retention loop is frontend-heavy and doesn't conflict with the backend migration. I've scoped them with [engineering lead] and we believe it's feasible. Happy to go deeper on the build plan if that's useful."
Head of Sales: "Can I tell customers we'll have [enterprise feature] in Q3?" No, that's Q4. Prepare for this: "Q4 is when it ships. I'd suggest framing it as 'on the roadmap for second half' in customer conversations rather than a specific quarter, which gives us room if Q3 runs long."
The item most likely to generate debate
The decision to deprioritize [specific item] will surface. Someone in the room asked for it, or it was on a previous roadmap version. Pre-empt it: acknowledge it early. "You'll notice X isn't on this roadmap. I want to address that directly before we dive in." Then give the one-sentence rationale. Letting it come up as a surprise objection is worse than naming it first.
Variations
Click a violet field and type your own details, then copy.
Click a violet field and type your own details, then copy.
Click a violet field and type your own details, then copy.
Tips and gotchas
The audience reframe is the most underused part of this workflow. Most roadmap reviews fail not because the strategy is wrong but because the framing is built for the PM, not the audience. "We're shipping a notification redesign" means nothing to a CEO. "We're closing the engagement gap that's costing us 18% of 30-day retention" means everything.
Prepare for the things you deprioritized, not just what you're building. The hardest roadmap review questions are never "why are you building that?" They're "why aren't you building this other thing I care about?" Write down every significant deprioritization decision and have a one-sentence rationale ready for each.
Name the number. If you're making a business case, put a number on it. Claude can help you do the back-of-napkin math: "at X users and Y conversion rate, closing this gap is worth approximately Z in ARR." Approximate is fine. Vague is not.
Ready to try?
Click a violet field and type your own details, then copy.
Need somewhere to deploy?
Railway gives you one-click deploys from GitHub with generous free tier. Perfect for shipping what Claude Code builds.
Deploy your first app on RailwayPick the right Claude plan for your workflow
Use our side-by-side comparison to match plan to workload so you never hit limits mid-sprint.
Open plan comparisonNew guides, when they ship
One email, roughly weekly. CLAUDE.md templates, workflows I actually use, and the cut-for-length stuff that does not make the public guides. One-click unsubscribe.
Or read Product Field Notes, the Substack