How to pitch a decision to executives in two minutes

You have ten minutes on the leadership agenda and one thing you need: a yes, a no, or a choice between two paths. The pitch that gets it opens with that ask, not with the history of how you got there.

Nancy Duarte, of the presentation firm Duarte, Inc., puts the problem bluntly in her guide to presenting to senior executives: "So they won’t sit still for a long presentation with a big reveal at the end. They’ll just interrupt you before you finish your shtick." Her fix is a timing exercise: if you are given 30 minutes, write the opening as if the slot had been cut to 5 minutes. That pressure is what pushes the recommendation to the front.

The structure below takes that idea one step further for a single decision: an answer, then four short parts, spoken in about two minutes.

Why do executives want the answer before the explanation?

An executive's job in your meeting is to choose, not to research. They need to know early what you are asking for, because it tells them how to listen to everything that follows. A PM who opens with "so, back in July we started looking at checkout" makes the executive do the work of guessing where the story ends.

Duarte's advice for slides follows the same logic. She recommends a short set of summary slides at the front and the rest as an appendix, with a "10% rule": "If your appendix is 50 slides, create 5 summary slides, and so on." The summary is the pitch. The appendix exists for the questions.

The limit of that advice is that it was written for presentations, and most product decisions do not need a deck at all. The principle still holds in a meeting, a Slack thread or a hallway: answer first, evidence on request.

What are the four parts of a decision pitch?

After the one-sentence answer, a decision pitch has four parts. Each one answers a question the executive would otherwise ask.

Part	Question it answers	Spoken length	What to leave out
Situation	What is true right now?	2 to 3 sentences	How you found out, who was in which meeting
Stakes	What happens if we do nothing?	1 to 2 sentences	Every possible risk; name the one that matters
Options	What could we do instead?	One line per option, 2 or 3 options	Options nobody would pick
Decision	What do you recommend, and what do you need?	2 sentences	Hedging; say it plainly

The whole thing fits in about two minutes when spoken. That is short on purpose. A pitch that needs ten minutes to deliver usually contains the analysis, and the analysis belongs in the appendix or the pre-read.

What does a decision pitch sound like before and after?

Take a hypothetical case. You are the PM for a redesigned checkout planned to launch to all customers in two weeks. A staged rollout to a small share of traffic shows payment failures running higher than on the old checkout, and the fix touches a payment provider integration your team does not own. You want to delay the launch by three weeks.

Before: the chronological version.

"So, a quick update on the new checkout. We started the staged rollout on the 3rd, and at first everything looked fine. Then on day four the support team flagged a few tickets about failed payments, so we pulled the logs with engineering. It took a while to reproduce, but we found that some card types fail on the new flow when the provider asks for extra verification. We have talked to the payments team and they think the fix is doable, though they have their own roadmap. We are looking at a few options, and we think it might make sense to maybe move the date, depending on what everyone thinks."

Every fact in that version is useful. The ask arrives in the last sentence, hedged twice, and an executive who interrupted at "day four" never heard it.

After: answer first, then the four parts.

• Answer: "I'm asking to move the checkout launch from the 14th to the 5th of next month."
• Situation: "The staged rollout shows more failed payments on the new checkout than on the old one, concentrated in cards that need extra verification. The fix sits in the payments team's integration, not ours."
• Stakes: "If we launch on the 14th, every customer with one of those cards hits the failure, and failed payments are lost revenue plus support tickets."
• Options: "One: launch on the 14th and accept the failures. Two: launch on the 14th with the old checkout as a fallback for those card types, which adds about a week of our own work. Three: delay three weeks while the payments team ships the fix."
• Decision: "I recommend option three. It costs three weeks and no rework, and the payments team has committed to the date. I need your call today so marketing can move the announcement."

The second version is shorter and contains fewer facts. What it adds is an order: by sentence one, the executive knows what decision they are being asked to make.

How do you present options without stacking the deck?

Present options you would actually accept. A pitch where options one and two are obviously bad is a request for approval with decoration, and experienced executives spot it immediately. If you only have one real option, say so and ask for approval directly.

Give each option its cost in the same unit (time, money, risk to a named metric) so they can be compared without a calculator. Include doing nothing whenever it is a real choice, because it is often the option an executive is quietly considering.

Say whether the decision can be undone. Jeff Bezos drew that line in Amazon's 2016 letter to shareholders: "Many decisions are reversible, two-way doors. Those decisions can use a light-weight process." A delayed launch is usually a two-way door. Deleting a pricing tier customers already pay for is not, and it deserves more than two minutes.

What if you don't have all the data?

You rarely will. The same Bezos letter says "most decisions should probably be made with somewhere around 70% of the information you wish you had. If you wait for 90%, in most cases, you’re probably being slow." That figure is one CEO's rule of thumb, not a measured threshold, and it was written for a company that treats speed as a strategy. It is still a useful permission slip: name what you do not know, say how you would find out you were wrong, and recommend anyway.

In the pitch itself, the missing data goes into the stakes or the decision line, in one sentence: "We don't yet know whether the failures affect mobile more than desktop; we'll know by Friday, and it doesn't change the recommendation."

What should you do when an executive interrupts or disagrees?

Answer the question, then go back to whichever part of the pitch still matters for the decision. If the interruption was about the options, you may never need the rest. Because the answer came first, nothing important is lost when the pitch is cut short.

When an executive disagrees with the recommendation, ask what would change their mind, then ask for the decision anyway: "If we go with option one, I'd like it on record that we expect higher payment failures for three weeks, so support can prepare." A clear decision you disagree with is more useful than an open question that drifts to next month's meeting. For the harder version, where the answer you owe is a no, see how to say no to stakeholders.

When is a two-minute pitch the wrong format?

When the decision is large, hard to reverse, and depends on evidence the room has not seen. A pricing overhaul, a platform migration or killing a product line needs a written document people read before the meeting, so the discussion starts from shared facts instead of first reactions. The four parts still work as the document's outline, but the options section grows into real analysis.

It is also the wrong format when the executive needs to understand a trend before they can decide anything. That is a data presentation, and it has its own structure: see data storytelling for turning numbers into a narrative. If you are writing the pitch up rather than saying it, AI for executive summaries covers drafting the written version, and AI for stakeholder updates covers the routine updates that should not be pitches at all.

How do you get better at pitching decisions?

Practise on small decisions. Write the answer sentence for the next thing you need from your manager before you write anything else, and time yourself saying the four parts out loud. If it runs past two minutes, the extra material is almost always in the situation part.

The Product Storytelling bootcamp is a 1-week programme with 2 live sessions, part of the Product Management Starter Track and the Product Leadership Track, directed by Andre Albuquerque. Its public curriculum includes stakeholder persuasion (handling objections, framing risks) and storytelling for strategy and roadmaps, and its practical challenge has you diagnose three failed investor pitches for the same product and write the one that works. For the storytelling fundamentals behind the four parts, start with what product storytelling is.

Builders Camp runs live and self-paced bootcamps in product management and AI product building. See the Product Storytelling bootcamp for the next cohort and the self-paced version.