Presenting-to-Senior-Leadership

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

The fix is a seven-part narrative structure rooted in Barbara Minto’s Pyramid Principle — designed so that leaders get the answer before the evidence, not after it.

The Seven-Part Structure

1. Situation — The current factual state. Brief, neutral, no opinion. Establishes shared context.

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

2. Complication — What has changed or emerged to make the situation problematic. The tension demanding action.

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

3. Question — The specific question this presentation will answer. Making it explicit keeps the presentation focused.

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

4. Answer — The recommendation, stated upfront. Leaders should not wait until the end for the conclusion.

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

5. Evidence — The data and analysis supporting the answer. Technical detail lives here — but it follows 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. Proactively naming risks builds trust.

   • 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. Never leave without one.

   • 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

The most common mistake: presenting evidence before the answer. Engineers are trained to show their work — to build up from data to conclusion. This is appropriate in academic and technical peer review contexts. In executive presentations, it forces leaders to hold all the evidence in memory before they know what it is supporting, 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

Standard narrative chronology is fine for retrospectives, postmortems, or peer technical reviews where evidence-first is the shared norm.

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 (Situation, Complication, Question, Answer) framework; foundational source Larson’s structure builds upon
  • Developed at McKinsey & Company in the 1970s as a consulting communication standard

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

  • Audience-centred presentation design; 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 explaining why top-line framing (the “core message”) 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 in scientific presentations; explains why leading with conclusions rather than methods 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.