Presenting Recommendations to Decision Makers

The meeting is for judgment, not for reading aloud

A common failure mode in corporate life looks like this: forty slides, twelve attendees, no decider identified, and twenty minutes spent on chart animations nobody asked for. The presenter reads bullet points. The CFO (chief financial officer, executive responsible for finance, budget, and financial reporting) checks email. The COO (chief operating officer, executive responsible for day-to-day operations) wonders when capacity planning appears. The meeting ends with "let's take this offline," which is often code for "no decision today."

Presentations to decision makers are not documentaries. They are structured conversations that move a specific person from understanding to commitment. Slides support that conversation. They do not replace you, and they should not be a novel the audience reads while you narrate. Lesson 1 taught you to put the recommendation first in a memo. The same logic applies on screen: the governing idea leads, evidence follows, and the meeting ends with an explicit ask.

When presentations fail, the cost is not embarrassment. It is delayed capital, ambiguous priorities, and teams that execute the wrong version of "yes." A board that cannot see tradeoffs defers a product bet until a competitor moves. A CEO who hears features before strategy approves scope creep. Your job is to design a layered deck: shallow enough for a hallway decision, deep enough for skeptics, and honest about what you do not know (Lesson 4).

You are the presentation; slides are evidence

Strong presenters treat slides as visual evidence for a spoken argument. Weak presenters treat slides as the argument itself, which invites the audience to read ahead, disagree silently, and disengage. The fix is not charisma. It is architecture.

Three principles keep decks decision-ready:

First, one governing thought. Every deck answers one question: "What should we do?" Sub-questions support that answer; they do not multiply it. If you cannot state the governing thought in one sentence, you are not ready to present.

Second, action titles, not topic labels. A topic title names a subject ("Q2 Churn Analysis"). An action title states the takeaway ("Enterprise churn driven by onboarding gaps, not pricing"). Action titles let a skimmer understand the story without hearing your voice.

Third, explicit ask at the end. Deciders are not mind readers. Close with: "Today we need approval to delay EU launch ninety days and fund $480K compliance work. Do we approve?" Silence is not consent.

Delivery mechanics matter after structure. Speak slower than feels natural. Pause after key numbers so they land. Make eye contact with the decider, not the screen. If you lose the room, it is usually because you buried the ask, not because you forgot a joke.

The Pyramid Principle on screen

Barbara Minto's Pyramid Principle is a logic structure for communication: start with the answer, group supporting ideas, order evidence within each group. On slides, the pyramid has three visible levels.

Level 1: Governing thought (often slide 2 after a title slide). One sentence recommendation.

Level 2: Key line (typically three to four slides). These are the main reasons the recommendation wins. Each reason gets an action title.

Level 3: Evidence (charts, tables, quotes, benchmarks). Each evidence slide supports exactly one key-line slide.

The pyramid prevents the "data dump then surprise conclusion" pattern that erodes executive trust. It also mirrors BLUF from Lesson 1: answer first, proof second.

Topic title: "Q2 Churn Analysis"

Action title: "Enterprise churn driven by onboarding gaps, not pricing"

The action title tells the CFO where to challenge assumptions (onboarding investment) instead of wasting time on pricing discounts that do not address the driver.

A sample five-slide executive core outline you can adapt:

Slide 1 (title): Decision title + date + presenter
Slide 2 (governing thought): "Recommend [action] to [outcome] by [date]"
Slide 3 (key line 1): Action title + one chart or number
Slide 4 (key line 2): Action title + one chart or number
Slide 5 (key line 3 + risks): Action title + top risk and mitigation
Slide 6 (ask): Explicit approval sentence + next steps table

Appendix holds sensitivity tables, methodology, competitor profiles, and long backup. Never present appendix unless asked.

Audience analysis: same facts, different emphasis

Customization is not spin. It is relevant emphasis without changing truth. The CFO and the COO can watch the same five-slide core and care about different sentences on slide 3. Your layered deck should let you reorder emphasis in speaker notes, not fabricate alternate facts.

Before you build slides, write one sentence: "The decider for this meeting is [role], and they will say yes if [condition]." If you cannot name the decider, postpone the meeting. Presenting to a room without authority converts decisions into seminars.

Order customization example: For a CEO, slide order might be: recommendation, competitive window, tradeoff, risk. For a CFO, same slides but speaker notes lead with payback math on slide 3 before competitive window on slide 4. Facts unchanged; emphasis shifted.

From Unit 4, execution fails when decision rights are muddy. Presentations should name the owner who executes after approval, not only the executive who applauds.

Layered decks: 10-minute, 30-minute, and 60-minute paths

Build three depths from one story:

10-minute hallway version (3 slides): Governing thought, strongest single chart, explicit ask. Designed for "Can we approve X today?" conversations outside the conference room.

30-minute staff version (8-12 slides): Full key line plus risks and next steps. Designed for functional leaders who must align execution.

60-minute version (core + appendix): Appendix slides for methodology, sensitivities, and competitor detail. Presented only if questioned.

Never open with appendix. Protect decision time. Executives reward presenters who finish early with a clear ask more than presenters who "show thoroughness" with fifty slides.

Sample 30-minute presentation outline for "Delay EU launch ninety days":

Pre-read (memo, Lesson 1): BLUF + SCR one-pager sent 24 hours ahead

Live meeting agenda:
0-2 min: Restate governing thought (no slide reading)
2-8 min: Key line 1 - Compliance fine exposure ($2.1M) with single bar chart
8-14 min: Key line 2 - Support capacity conflict in Q3 (one line chart)
14-20 min: Key line 3 - U.S. enterprise momentum preserved (table)
20-25 min: Risks, rejected alternative (contractor compliance audit), owners
25-30 min: Q&A scoped to decision; explicit approval ask

Appendix (not presented unless asked):
A1: Regulatory citation summary
A2: Vendor implementation timeline
A3: Sensitivity on delay length (60 vs 90 vs 120 days)

The outline ties live minutes to decisions, not to slide count vanity.

Q&A, deflection, and credibility under pressure

Q&A (question and answer) is where presentations win or lose trust. Use a short protocol:

1. Pause. Repeat or paraphrase the question so the room shares it.
2. Answer the shortest path that respects the decision frame.
3. If unknown: "I do not know; I will follow up by Thursday with [specific deliverable]." Then do it.
4. If out of scope: "Strong question; separate from today's decision on [X]. Suggest we take [Y] offline with [owner]."

Deflect scope creep without arrogance. Deciders appreciate guards on meeting purpose. They resent presenters who improvise new commitments to seem helpful.

When challenged on numbers, show assumptions calmly. "That $2.1M figure assumes maximum regulatory penalty under Directive X; appendix A1 walks through legal interpretation." Lesson 3 will help you design charts that survive skeptical CFO eyes. Lesson 4 will help you state ranges instead of false precision.

End every decision meeting by stating what was decided, what was not, and who owns next steps. Ambiguous endings produce ambiguous execution.

Speaker notes, rehearsal, and the sixty-second rule

Slides carry headlines; speaker notes carry reasoning. For each core slide, draft sixty seconds of talk track: the claim, the number, the caveat, the link to the ask. If your note exceeds sixty seconds, the slide is overloaded. Split it or move detail to appendix.

Rehearse with a skeptical colleague playing the CFO role. Their job is to interrupt with "so what?" and "compared to what?" If you cannot answer without flipping to slide 17, your pyramid is broken.

The sixty-second rule for live delivery: the audience should hear the conclusion within the first minute after the title slide. Respect attention curves. Long warm-up stories signal you are not ready for a decision meeting.

Sample speaker notes for slide 3 (Northwind vendor consolidation):

"Slide 3 proves savings are material, not cosmetic. $740K annual run-rate savings after go-live, against $290K migration cost. Payback under five months once live. CFO question expected: revenue at risk during renewals. Answer: $420K pipeline under parallel run, mitigated by dedicated squad and frozen workflow changes. Do not open appendix unless asked for monthly cash phasing."

Notes like this keep Q&A inside the decision frame.

Integrating memo, deck, and data from prior lessons

Treat the pre-read memo (Lesson 1) as the authoritative fact base. The deck is a visual index into that memo, not a second document that might drift. Chart slides (Lesson 3) should reuse the same numbers and so what lines as the memo. Risk slides (Lesson 4) should reuse scenario names and triggers verbatim.

When documents disagree, executives trust neither. Assign one owner to reconcile memo, deck, and appendix before send. Version numbers in footers help: "Decision pack v1.2, July 10."

Crestline Health, a 2,100-employee regional health system, prepared a fifty-slide product strategy read for its board. Last quarter, the board checked phones and deferred a telehealth investment decision.

Part A: Failure diagnosis

Part B: Redesigned five-slide core + memo pre-read

Pre-read: One-page SCR memo (Lesson 1) recommending $6.2M telehealth platform over three years.

Slide 2 governing thought: "Approve $6.2M telehealth platform to reduce specialist access wait from 19 days to 7 days by FY27."

Slide 3 action title: "Wait-time reduction drives $4.1M annual contribution margin at 12% utilization" (single bar chart: current vs projected wait, described in prose: left bar 19 days, right bar 7 days, annotation on margin bridge).

Slide 4 action title: "In-house build delays launch eighteen months versus vendor path" (timeline graphic: vendor live month 9, build live month 27).

Slide 5 action title: "Top risk is clinician adoption; mitigated by champion program and paid workflow redesign" (table: risk, owner, milestone).

Slide 6 ask: "Request board approval of $6.2M capital plan and CEO authority to execute vendor contract by September 15."

Part C: Meeting flow and checks

Live meeting: 25 minutes. First 5 minutes silent read of memo (optional culture). Presenter speaks to slides 2-6 only. CFO deep dive on margin assumptions moved to appendix A2, invoked only when asked.

Outcome check: Decision recorded in minutes: approved $6.2M with adoption KPI review at month 6 ✓. Slide count presented live: 5 ✓. Ask explicit: yes ✓.

Part D: Managerial read

The redesign respects board time and fiduciary focus. Clinical outcomes appear, but through margin and access metrics the board can govern. Operator question: "What if adoption stalls at 6%?" Presenter should answer with downside scenario from Lesson 4, not new slides invented live.

Same five-slide core for Northwind Analytics vendor consolidation (Lesson 1). Facts identical; speaker notes differ.

CFO path (emphasis order in talk track):

• Open with three-year net benefit $1.93M and payback 4.7 months.
• Slide 3 highlights $740K annual savings and $290K migration cost.
• Tradeoff: six-week dual tooling during renewals; quantify revenue at risk $420K pipeline with mitigation squad.
• Ask: approve $290K project budget July 15.

COO path (emphasis order):

• Open with customer-visible risk target: escalations stay at 0.9%.
• Slide 4 highlights migration squad staffing and frozen workflow policy.
• Tradeoff: agent training hours (120 hours) scheduled in August low-volume weeks.
• Ask: approve squad formation and parallel-run playbook by July 20.

Managerial read: Customization lives in talk track and appendix pointers, not alternate numbers. If CFO and COO compare notes after the meeting, facts must match.

You are preparing a 30-minute presentation to the CEO on whether to launch a loyalty program costing $1.4M year one. Expected incremental gross profit: $2.0M year one if 18% of active users enroll. Enrollment uncertainty range: 12%-22%. Competitive risk: rival launched a similar program last month.

Tasks:

1. Write the governing thought (one sentence).
2. Draft a six-slide core outline with action titles only (no slide bodies).
3. Write a 10-minute three-slide subset (which slides stay).
4. Draft explicit closing ask.
5. Explain in prose why pre-read memo plus short live deck beats a 40-slide read-aloud.

Solution

1. Governing thought:

"Launch loyalty program September 1 with $1.4M investment to capture $2.0M incremental gross profit at 18% enrollment, accepting six-week engineering delay on checkout redesign."

2. Six-slide core outline:

• Slide 1: Title - Loyalty program decision - July 2026
• Slide 2: "Launch September 1 to offset rival retention lift and raise repeat purchase rate 4 pts"
• Slide 3: "$2.0M incremental gross profit at 18% enrollment; breakeven at 11% enrollment"
• Slide 4: "Rival program already shifting 3% of our high-value cohort; delay risks 2026 churn spike"
• Slide 5: "Checkout redesign slips six weeks; mitigated by phased feature flag rollout"
• Slide 6: "Top risk: enrollment below 12%; trigger downsized rewards tier per Lesson 4 playbook"

3. 10-minute subset:

Slides 2, 3, and 6 (governing thought, economics, risk/ask condensed on 6). Competitive slide 4 moves to speaker note backup if CEO asks.

4. Closing ask:

"Today I need approval for $1.4M year-one budget and September 1 launch date. Do we approve?"

5. Why memo plus short deck wins:

The memo (Lesson 1) lets the CEO absorb BLUF and tradeoffs asynchronously, so live time tests judgment rather than basic comprehension. A 40-slide read-aloud duplicates what a memo should do, encourages phone checking, and buries the ask where fatigue sets in. Short deck plus pre-read respects attention, speeds decisions, and forces you to know the one story that matters.

Check: Breakeven enrollment: $1.4M / $2.0M = 70% of target enrollment → 0.70 × 18% = 12.6% ≈ 11% after fixed/variable simplification stated in assumptions ✓.

A presenter ends with "Happy to take questions" but never states an ask. The COO loved the operations detail. The CFO loved the sensitivity table in appendix. No decision is made.

Tasks:

1. Rewrite the closing 60 seconds with explicit ask and decision recap format.
2. Identify which Unit 4 concept explains why ambiguous endings fail execution.

Solution

1. Closing rewrite:

"Today we sought approval for two warehouse automation projects totaling $3.1M to cut pick errors 40% by Q2. You aligned on ROI and risks. Decision needed now: approve $3.1M capital in FY26 budget and name Ops VP as program owner. If not approved today, we lose vendor install window and slip savings to Q4. Do we approve capital and owner assignment?"

2. Unit 4 link:

From Decision Rights and Organizational Coordination, execution fails when decision rights and owners are unclear. Ending without an explicit ask leaves teams without authorized scope, matching Why Good Strategies Fail in Execution: ambiguous governance produces drift, not delivery.

Check: Ask names budget amount, owner role, and time consequence ✓.

Key takeaways

• Presentations move a named decider to commitment; slides are evidence, not the story.
• Pyramid structure and action titles put conclusions where skimmers and CFOs will find them.
• Layer decks for 10-, 30-, and 60-minute depths; appendix is on demand, not default.
• Tailor emphasis in talk track to CEO, CFO, COO, or board incentives without changing facts.
• Close with explicit approval ask and recap of decision, owners, and deferred topics.

1. Audit your last deck: count topic titles versus action titles. Rewrite three headlines as conclusions.
2. Who is the actual decider in your next meeting? Write the one-sentence "they will say yes if..." test.
3. Continue to Lesson 3: Using Data Without Overwhelming the Audience.