The short answer: two decks product managers bring to leadership again and again, the decision deck and the regular update, fail with AI for the same reason. The agent buries the point and fills gaps with things you never said. Give it your notes and a method that puts the answer and the ask on slide 1, sets every option out with the same numbers, says “unknown” when a cause isn’t known, and adds no plans of its own. In our blind test, a reviewer would send 12 of 12 Claude product updates made this way, against 0 of 12 without it, and 9 of 12 decision decks, against 3.

Why do product decks fail with leadership?

Product managers say it plainly. One of the most upvoted posts on r/ProductManagement about decks shares a six-slide update format that ends with what the PM needs from leaders. Another title sums up the problem: “My ‘solid’ status updates were the reason my VP never actually made a decision.” Reviewers check “whether the headline matches the nuance in the data”.

AI makes this worse in two ways. It produces clean slides with no position: three number tiles on slide 1 and the ask on slide 5. And when your notes leave a gap, it fills it: a likely cause for a number, a deadline, an owner, a recommendation. Your VP can’t tell which lines you stand behind.

How do you make a product decision deck with AI?

Give the AI the decision, who decides, the options with their numbers, and your recommendation if you have one. A method for decision decks should then:

  1. Put the answer and the ask on slide 1, so a reader who stops there knows what you want.
  2. Make the titles the argument. Read in order, they make the case.
  3. Set every option out with the same numbers, including waiting, and add up the totals the decision turns on.
  4. Show the decisive tradeoff in one picture: a to-scale comparison, a timeline or a table.
  5. Turn gaps into questions. A choice only the reader can make goes on the slide as a question; a fact only you know comes back to you in the agent’s reply. Never “TBD”.
  6. Use only your facts, and let the content set the length.
Two slides from each pricing-review deck made by Claude Opus 5.5. On its own: a title slide with no answer, the recommendation waiting until slide 10, and four identical number tiles. With the decision method: slide 1 recommends charging heavy users, not every seat, with the ask, and slide 2 is one chart showing the top 10% of workspaces drive 55% of usage costs.
A pricing review for a CFO and head of product, same request and same agent. On its own, the recommendation waits until slide 10. With the method, slide 1 gives it with the ask, and one chart makes the case.

How do you make a product update deck with AI?

Give it the goals and targets, the results for the period, what changed, what you know and don’t know about why, and what you need from the reader, if anything. A method for updates should:

  1. Say on slide 1 how you’re doing against the goal and what you need.
  2. Show every result against its target and the previous period.
  3. Match the headline to the nuance. A total that rises while one part falls is said on the same slide.
  4. Give a cause only when the notes give one. An unknown cause is called unknown, with the possibilities the notes name.
  5. Spend the slides on what missed or moved. On-track results share one scorecard.
  6. Make one update from several teams, not a pasted slide per team.
  7. Report only the asks, plans, owners and dates in your notes. If there’s no ask, say so.
Two slides from each CEO growth update made by Claude Opus 5.5. On its own: three number tiles on slide 1 with the ask left to slide 5, and a slide giving a cause the notes don't give. With the update method: slide 1 says subscriptions beat target and churn rose, with the ask; slide 2 says the cause is unknown, names both possible causes and charts actual against target.
A five-slide growth update for the CEO, where the notes say nobody knows yet why subscriptions jumped. On its own, Claude supplied a cause. With the method, slide 1 gives the state and the ask, and slide 2 says “cause unknown”.

On their own, both agents explained numbers the notes couldn’t explain, in 10 of 24 decks. Asked to let leadership “decide whether we build”, 3 of 4 decks recommended building anyway.

How do you set it up?

  1. Give your agent the method. In Claude Code or Codex: npx skills add arunai30/super-document-skills --agent claude-code --skill create-html-presentation --copy (or --agent codex). In Claude in the browser, connect share/artifacts and Claude fetches the same recipes.
  2. Paste your notes and say what the deck is for. A one-off decision goes to the decision method and a regular update to the update method: 12 of 12 decision requests and 24 of 24 update requests went to the right one on both agents.
  3. Let it check every slide, answer its questions, and share the deck as an HTML file, a PDF or a link you update in place. It isn’t a PowerPoint file.

The full guide for Claude Code and Codex covers each step, and the roadmap guide covers the third deck PMs bring to leadership.

How we tested

Six product decisions and six product updates, written like real asks with notes; three of each were held out, so the method was never tuned on them. Claude Code (Claude Opus 5.5) and Codex (GPT-6.1 Sol) each made every deck twice on their own and twice with the method. A Claude model that didn’t know which was which read every slide and said whether it would send each deck as it is.

Would send as it is, 12 decks per agent each way
DeckClaude on its ownClaude with the methodCodex on its ownCodex with the method
Product decision3938
Product update012211
Decks the reviewer flagged, 12 per agent each way
ProblemClaude on its ownClaude with the methodCodex on its ownCodex with the method
Decision: states something not in the notes8382
Decision: broken layout5060
Decision: looks like a template8000
Update: states something not in the notes11050
Update: too long5060
Update: working notes left on a slide4091

What’s next: decision decks still have a few lines the reviewer couldn’t trace (16 decks down to 5, not 0), Codex still leaves some working notes on decision slides (8 down to 5), and some updates come out plain when there’s little to show. No product managers have judged these decks yet; we’re putting the principles in front of working PMs next. Every request and number: decision decks and product updates.