Presenting to Senior Leadership

Core Idea

Engineers default to evidence-before-answer when presenting to senior leadership. Senior leaders need conclusion-first structure. The fix is a seven-part narrative rooted in the Pyramid Principle.

Engineers frequently present excellent work that fails to land with senior leadership. Larson attributes this to a format mismatch: engineering communication defaults to chronological narrative, while senior leaders need conclusion-first structure and clear decision support.

The Seven-Part Structure

1. Situation — Current factual state. Brief, neutral, no opinion.

   • Example: “Our mobile app has 2M daily active users. Infrastructure handles 50K concurrent requests at peak.”

2. Complication — What has changed to make the situation problematic.

   • Example: “p99 latency has increased 40% over 90 days. Infrastructure costs are projected to triple.”

3. Question — The specific question this presentation will answer.

   • Example: “Should we refactor our data layer now, or optimise incrementally while we hire?”

4. Answer — The recommendation, stated upfront.

   • Example: “We recommend a targeted refactor of the top three database queries over Q2.”

5. Evidence — Data and analysis supporting the answer. Technical detail lives here — after the answer.

   • Example: “Profiling shows three queries account for 78% of DB load. Fixing them requires 6 engineer-weeks.”

6. Risks — What could go wrong and what mitigations exist.

   • Example: “Primary risk: the refactor may surface latent data model issues. Mitigation: spike one query first.”

7. Ask — The specific decision or action needed from this group.

   • Example: “We need 6 engineer-weeks approved in Q2 and product to defer Feature X by two weeks.”

Why Conclusion-First Works

• Matches how senior leaders process information: They evaluate fit with org priorities before considering details
• Demonstrates strategic thinking: Presenting answer first signals you can prioritise, not just enumerate
• Creates decision points: Transforms an informational update into an actionable meeting
• Reduces cognitive load: Leaders who know less can engage at the right level without drowning in evidence

Common Failure Mode

Presenting evidence before the answer forces leaders to hold all evidence in memory before knowing what it supports — increasing cognitive load and making it easy to lose the thread before the recommendation arrives.

When to Use It

• Presenting a proposal, recommendation, or trade-off decision to leadership
• Requesting budget, headcount, or approval to change direction
• Status updates where a decision or action is expected

Related Concepts

• Larson-2019-An-Elegant-Puzzle
• Strategy-vs-Vision
• Good-Strategy-Structure
• Close-Out-Solve-or-Delegate
• Team-Snippets-and-Directional-Metrics

Sources

• Larson, Will (2019). An Elegant Puzzle: Systems of Engineering Management. Stripe Press. ISBN: 978-1-7322651-8-9.

  • Chapter 4.3: Seven-part framework for presenting to senior leadership

• Minto, Barbara (2002). The Pyramid Principle: Logic in Writing and Thinking (3rd ed.). Prentice Hall. ISBN: 978-0-273-65919-3.

  • Original SCQA framework; foundational source Larson’s structure builds upon

• Duarte, Nancy (2010). Resonate: Present Visual Stories that Transform Audiences. John Wiley & Sons. ISBN: 978-0-470-63201-8.

  • Conclusion-first narrative structure for persuasive presentations

• Heath, Chip and Dan Heath (2007). Made to Stick: Why Some Ideas Survive and Others Die. Random House. ISBN: 978-1-4000-6428-1.

  • SUCCES framework: top-line framing improves retention and decision quality

• Alley, Michael (2003). The Craft of Scientific Presentations: Critical Steps to Succeed and Critical Errors to Avoid. Springer. ISBN: 978-0-387-95557-3.

  • Assertion-evidence structure explaining why leading with conclusions improves comprehension

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.