“Your roadmap gets re-litigated from scratch in every exec review.”

The struggle

Third month running. You open the same roadmap, and forty seconds in, the same VP asks the same question — “why is billing ahead of the mobile work again?” — and the room resets to zero. You have an answer. You had it last month too. But it lives in your head, or in a Slack thread from March, or in a customer call nobody else heard, so it doesn’t survive contact with a confident senior person who remembers the conversation differently. By minute twenty you’re not defending a roadmap, you’re re-negotiating it, and you’ll walk out with an action item to “come back with more data.”

The obvious fix is a better deck, so you spend six hours on one, and it doesn’t work — because the deck was never the problem. The problem is that the reasoning behind each priority isn’t inspectable: nobody can trace “billing is first” back to the customer signal that put it there, so it degrades into your opinion versus theirs, and opinions get re-litigated for free. This playbook makes the reasoning traceable, rehearses the objections before the room raises them, and cuts prep to about two hours — so the review spends its time on decisions instead of on archaeology.

The chain

Step 1 — Make the priority order traceable · Productboard

Before any slide exists, make Productboard the thing you present from, not a tool you export out of. For each of the top items on the roadmap, confirm three attachments: the customer insights linked to it (Productboard’s whole point is that feedback notes attach to features), the score that put it in that position, and the objective it ladders to. Then build the one view you’ll actually show — features ordered by score, with insight counts visible. See the Prioritization and Roadmapping and Customer Insights sections of the support hub for how linking and roadmap sharing work.

The point of this step is a specific sentence you’ll be able to say out loud: “Billing is first because 23 accounts raised it, 9 of them in the enterprise segment, and here they are.” That sentence is not re-litigable. “I think billing matters more” is.

When to skip: if your priorities aren’t scored yet, stop — you don’t have a defense problem, you have a prioritization problem, and no amount of downstream tooling fixes it. Score first (RICE with AI is a fast first pass), then come back.

Step 2 — Draft the narrative, then attack it · Claude

Any frontier model runs this step. ChatGPT and Gemini do this job as well as Claude does; the prompt is plain text in, text out. We name Claude because that’s what we field-tested with (see last field-tested above) — not because it’s required. Use whichever you already pay for.

Export or paste your ordered list — item, score, insight count, objective, one-line rationale — into Claude. First the narrative:

You are helping me write the narrative for a monthly exec roadmap review. Below is my
prioritized roadmap: each item has a score, a linked-customer-insight count, the objective
it serves, and my one-line rationale.

Write a 6-beat narrative in this order:
1. The decision this review needs from the room (one sentence).
2. What changed since last month.
3. The top 3 priorities, each with the evidence that justifies its rank.
4. What we are explicitly NOT doing this quarter, and what that buys us.
5. The risks I'm accepting.
6. The specific asks.

Rules: use only the numbers and rationales I gave you. Do not invent metrics, customer
counts, revenue figures, or dates. Where a claim needs a number I haven't supplied, write
[NEEDS DATA: <what exactly>] inline instead of estimating. Keep it under 500 words.

Roadmap:
"""
<paste>
"""

The [NEEDS DATA] markers are the useful output. They’re a list of the exact holes in your argument, generated before an exec finds them for you.

Then, in the same conversation, run the pre-mortem:

Now switch roles. You are the most skeptical person in that exec review — a VP whose
own priority did not make the top 3.

Write the 8 hardest objections this room will raise, ranked by how much damage each does
to the decision I'm asking for (most damaging first). For each objection give:
- the objection in the words an exec would actually use,
- why it lands (what weakness in my reasoning it exploits),
- the specific data I would need to answer it — name the metric, the segment, and the
  time window.

Do not invent data I haven't given you, and do not answer the objections for me. If an
objection cannot be answered with data at all because it's a values or strategy
disagreement, label it POLITICAL rather than dressing it up as an analysis gap.

Ranking by damage is what makes this usable — you’re not going to answer eight objections in a 30-minute review, and the ranking tells you which three to spend Saturday on. The POLITICAL label matters too: those objections need a pre-meeting with a person, not a chart. (Pre-mortem before you ship is the same technique aimed at a launch instead of a review.)

Step 3 — Turn the approved narrative into the deck · Gamma

Only now does a slide exist. Paste the finished narrative into Gamma and generate — one beat per slide, 8–12 slides, then drop in the Productboard view as the evidence slide. Fix the two or three slides where the generator over-designed a simple point, and stop. See the Gamma help center for paste-and-generate and embeds.

Honest trade-off: if your company runs on a locked-down corporate template and decks get reused in board packs, generation will cost you more in re-formatting than it saves; Plus AI works inside Google Slides and respects your template. And if your review is a doc review, skip this step entirely — the narrative from step 2 is the artifact. (Write the exec summary before the slides.)

Step 4 — Pre-answer the top three objections, with real data (40 minutes, not optional)

Take the three highest-damage objections from step 2 and go get the actual numbers — the segment breakdown, the churn figure, the support-ticket volume. Put each answer on a backup slide, not in the main flow, and cite the source on the slide.

Then apply the rule that makes this playbook honest: if you cannot answer an objection with data, that’s not a slide problem — that’s a signal your priority might be wrong. Go change the order, or go say out loud in the review “we ranked this on judgment, not evidence, and here’s the judgment.” Both of those end debates. A confident non-answer does not.

For anything labeled POLITICAL, book fifteen minutes with that person before the review. The objection you defuse in a hallway never costs you the room.

Where it breaks

• A pretty deck doesn’t fix an un-defensible priority. Gamma will make a beautiful slide out of a ranking you can’t justify, and beautiful makes the challenge sharper, not softer. If step 4 keeps producing unanswerable objections, the output of this playbook is a re-ordered roadmap, not a deck.
• The AI has no idea what’s actually happening in your company. It doesn’t know the VP of Sales has a number to hit this quarter, that the mobile team was promised something in a reorg, or that your CEO has a pet feature. It generates the objections an average skeptical exec would raise. The ones that will actually cost you the meeting are political and specific, and you’re the only person in the loop who can name them — which is why the prompt makes it label POLITICAL instead of faking an analysis.
• Re-litigation is usually a decision-rights problem wearing a slide-quality costume. If the same debate returns every month no matter how good your evidence is, nobody in that room knows who actually decides. Fix that instead — Bain’s RAPID exists for exactly this, and one named decider plus a written decision log will do more for you than any deck. Tara Seshan’s ongoing stack rank (paywalled) is the lightweight version: keep the ranking visible and continuously shared, so the review is a checkpoint, not a first reveal.
• Stale insight links. Traceability is only worth something if it’s true. A feature linked to 23 insights from eighteen months ago, half of them from churned accounts, is worse than no number at all — because someone will check. Re-verify the links on the top three items each month; that’s most of step 1’s twenty minutes.
• The pre-mortem becomes theatre. Running the objection prompt and reading the output feels like preparation. It isn’t. The only part that changes the meeting is step 4 — going and getting the data, or changing the priority. Skip it and you’ve spent two hours making a confident-looking version of the same un-defended roadmap.