executive-communication-framework-reference
Executive Communication Framework
The complete manual for presenting with , not
What’s In This Guide
- Framework Steps 1–7: Deep dive with Will Larson quotes, examples, common mistakes, and authority language patterns
- Authority vs Permission: Self-assessment, career impact, real-world transformations
- Ready-to-Use Templates: Executive brief template, decision request emails, status updates
- Quick Reference Cards: Timing cheat sheet, power phrases, pre-meeting checklist
Total presentation time: ~5 minutes structured + discussion/Q&A
Based on “An Elegant Puzzle: Systems of Engineering Management” by Will Larson, Section 3.13
Tie to Business Value
$ cat principle.txt
“Answer ‘why should anyone care?’ — not technically, but in terms of revenue, risk, or strategic positioning.”
The Core Principle
“Typically you’ll be presenting on an area that you’re intimately familiar with, and it’s probably very obvious to you why the work matters. This will be much less obvious to folks who don’t think about the area as often. Start by explaining why your work matters to the company.”
— Will Larson, An Elegant Puzzle
How to Apply This
Lead with business impact in your opening sentence:
- Revenue: “This saves $X annually” or “This enables $Y in new revenue”
- Risk: “This eliminates compliance risk threatening our audit”
- Strategy: “This positions us for acquisition” or “This enables 2x scale”
❌ Don’t Lead With:
- Technical problems (“Our database is slow”)
- Process issues (“We’re having vendor problems”)
- Internal pain (“The team is frustrated”)
Common Mistakes
Technical Framing
“We need to migrate from MySQL to PostgreSQL”
Business Framing
“I recommend migrating our database to reduce query times by 60% and eliminate $50K in scaling costs“
Problem-First
“Our current system has performance issues”
Opportunity-First
“This upgrade delivers 40% faster response times and improves customer satisfaction“
Authority Language Patterns
Use These Patterns:
Historical Narrative
$ git log –oneline narrative.md
“2–4 sentences on how we got here. Not a history lesson — just enough context so the recommendation makes sense.”
The Core Principle
“Another aspect of framing the topic is providing a narrative of where things are, how you got here, and where you’re going now. This should be a sentence or two along the lines of, ‘Last year we had trouble closing several important customers due to concerns about our scalability. We identified our databases as our constraints to scaling, and since then our focus has been moving to a new sharding model that enables horizontal scaling, which is going well, and we expect to finish in Q3.'”
— Will Larson, An Elegant Puzzle
The Formula
Past → Present → Future trajectory:
| Step | What to Include | Example |
|---|---|---|
| 1. What happened | 1 sentence | “Our user base grew 300% last year” |
| 2. Current state | 1 sentence | “Response times degraded from 200ms to 2 seconds” |
| 3. What’s at stake | 1 sentence | “Contract renewal deadline forces a decision in 60 days” |
Examples
Poor Narrative
“We’ve had various issues with performance over the years and different teams have tried different solutions but nothing has really worked consistently…”
⚠️ Too vague, no timeline, no stakes
Good Narrative
“Our user base grew 300% last year, pushing our infrastructure beyond capacity. Response times degraded from 200ms to 2 seconds, causing customer complaints. Contract renewal deadline forces a decision in 60 days.”
✓ Clear timeline, quantified impact, urgent deadline
What NOT to Include
Avoid These:
- Detailed technical history
- Blame or finger-pointing
- Multiple competing storylines
- Ancient history (>18 months ago unless critical)
Authority Framing
Position yourself as someone who understands the situation rather than someone :
Authority Signals:
Explicit Ask
$ echo $REQUEST
“State exactly what you need. Budget amount. Headcount. A decision by Friday. Specific asks get specific answers.”
The Core Principle
“If you don’t go into a meeting with leadership with a clear goal, your meeting will either go nowhere or go poorly. Start the meeting by explicitly framing your goal!”
— Will Larson, An Elegant Puzzle
The Authority Shift
Permission-Seeking
- “Will you support me in exploring this?”
- “Can I get approval to look into options?”
- “Would you be open to considering alternatives?”
❌ Vague, uncertain, asking for permission to think
Specific Resource Requests
- “I need $200K budget approval and 2 FTE headcount”
- “I need your decision by Friday and input on team coordination”
- “I need legal review of contract terms and IT procurement approval”
✅ Specific, actionable, demonstrates planning
Types of Asks
| Ask Type | What to Specify | Example |
|---|---|---|
| Budget | Dollar amount + timeline | “$150K approval by March 15” |
| Resources | FTE count, contractor hours, licenses | “2 senior engineers for 6 months” |
| Decisions | Yes/no by specific date, priorities | “Vendor selection decision by Friday” |
| Input | Domain expertise from stakeholders | “Legal review of compliance requirements” |
| Access | Data, systems, stakeholder meetings | “Access to Q1 financial data for analysis” |
| Authority | Decision-making power, team leadership | “Authority to approve vendor contracts <$50K" |
Multiple Ask Strategy
Prioritize Your Asks
- Primary ask: The thing you absolutely need
- Secondary asks: Nice-to-have or follow-up items
Common Mistakes
Vague Support
“I need your backing on this”
What does “backing” mean? Money? Headcount? A nice email?
Specific Resource
“I need $50K budget approval and legal review”
Crystal clear what’s needed
Authority Language
Power Phrases:
Data-Driven Diagnosis
$ analyze –metrics –evidence
“The evidence behind your recommendation. Key metrics, not all metrics. Address the obvious counterargument before someone raises it.”
The Core Principle
“You should be deep enough in your data that you can use it to answer unexpected questions. This means spending time exploring the data, and the most common way to do that is to run a thorough goal setting exercise.”
— Will Larson, An Elegant Puzzle
What to Include
Key Supporting Metrics:
- Financial impact (costs, savings, ROI)
- Performance data (before/after comparisons)
- Risk quantification (probability × impact)
- Timeline constraints (deadlines, dependencies)
Address Obvious Objections
| Expected Objection | Proactive Response |
|---|---|
| “This seems expensive” | Show ROI calculation with payback timeline |
| “This seems risky” | Present risk mitigation plan with contingencies |
| “This takes too long” | Demonstrate urgency/cost of delay |
Data Presentation Strategy
Lead with the strongest data points:
- Most compelling financial metric
- Clearest performance/risk indicator
- Time-sensitive constraint
- Supporting evidence
⚠️ Avoid Data Dumps
- Don’t show every metric you analyzed
- Focus on decision-relevant data
- Use ranges when precision isn’t needed
- Round numbers for readability ($147,832 → $150K)
Examples
Poor Diagnosis
“I analyzed seventeen different metrics across five categories and found various issues in multiple areas that could potentially be improved through several different approaches…”
❌ Overwhelming, unfocused, signals uncertainty
Good Diagnosis
“Current vendor costs $200K annually with 40% SLA failures. Alternative vendor quotes $150K with 99% uptime guarantee. Migration cost is $75K one-time, paying for itself in 6 months. Contract renewal deadline in 90 days forces immediate decision.”
✅ Focused, quantified, actionable
Authority Positioning
Own Your Analysis:
Decision-Making Principles
$ cat decision-framework.yml
“Share your mental model. This shows your thinking, not just your conclusion.”
The Core Principle
“One of your aims is to provide a mental model of how you view the topic, allowing folks to get familiar with how you make decisions. Showing you are ‘in the data’ is part of this, and the other aspect is defining the guiding principles you’re using to approach decisions.”
— Will Larson, An Elegant Puzzle
Why This Matters
Executives want to understand your framework because:
- They need to trust your judgment on future decisions
- It helps them evaluate trade-offs and priorities
- It demonstrates strategic thinking beyond this specific issue
- It shows you’re not just reactive problem-solving
How to Structure Principles
Template: “I prioritized [X] over [Y] because [business reasoning]”
Example Frameworks:
- “Risk mitigation first, cost optimization second, because compliance failure threatens the business”
- “Customer impact above internal efficiency, because retention drives growth”
- “Proven solutions over cutting-edge, because stability enables scale”
- “Team development alongside delivery, because sustainable growth requires capability”
Common Principle Categories
| Trade-off Type | Question to Answer | Example Principle |
|---|---|---|
| Risk vs. Opportunity | When prioritize safety vs. growth? | “Compliance first, feature velocity second” |
| Short-term vs. Long-term | How balance immediate vs. future? | “Platform investment over quick patches” |
| Cost vs. Quality | Where invest for premium outcomes? | “99.9% uptime justifies premium vendor costs” |
| Build vs. Buy | When develop vs. purchase? | “Buy commodity, build differentiation” |
| Centralized vs. Distributed | How balance control vs. autonomy? | “Centralize security, distribute features” |
Authority Demonstration
Defensive Explanations
- “I know this seems expensive, but…”
- “Some people might not like this approach, however…”
❌ Apologetic, defensive
Confident Framework Application
- “I prioritized long-term scalability over short-term cost savings because…”
- “My framework emphasizes proven solutions, which is why I selected…”
✅ Confident, principled
Common Mistakes
❌ Avoid These:
- Too many principles: Stick to 3-5 core guidelines
- Obvious principles: “I prioritize success over failure” (duh)
- Technical principles: “I chose REST over GraphQL because…” (wrong level)
- Personal principles: “I like working with this vendor” (not business-focused)
Timeline & Next Steps
$ gantt –milestones –dependencies
“Concrete milestones. Vague timelines signal vague thinking.”
The Core Principle
“Apply your principles to the diagnosis to generate the next steps. It should be clear to folks reading along how your actions derive from your principles and the data. If it’s not, then either rework your principles or your actions!”
— Will Larson, An Elegant Puzzle
Timeline Specificity
Vague (signals uncertainty)
- “We’ll start soon”
- “This should take a few months”
- “Sometime in Q2”
Specific (signals planning)
- “Phase 1 starts March 15”
- “Initial deployment by April 30”
- “Full rollout completed June 15”
Implementation Structure
Phase-based approach:
| Phase | Timeframe | Focus | Example Activities |
|---|---|---|---|
| Immediate | 0-30 days | Planning & Setup | Budget approval, vendor selection, team allocation |
| Short-term | 1-3 months | Core Implementation | Development, testing, initial deployment |
| Medium-term | 3-6 months | Full Deployment | Rollout, optimization, training |
| Long-term | 6+ months | Measurement & Iteration | Performance monitoring, improvements, scaling |
What to Include
Key Milestones with Dates:
- Decision points and deadlines
- Resource allocation timing
- Risk checkpoints and go/no-go decisions
- Success measurement periods
Dependencies and Constraints:
- External vendor timelines
- Budget cycle requirements
- Team availability windows
- Regulatory or compliance deadlines
Authority Ownership
Hoping Someone Else Figures It Out
- “Someone should probably coordinate this”
- “We’ll need to figure out the timeline”
- “The team can work out the details”
❌ Passive, unclear ownership
Taking Ownership of Execution
- “I will coordinate vendor selection by March 1”
- “My team will deliver the migration plan by March 15”
- “I’m accountable for staying within the $200K budget”
✅ Clear ownership, accountable
Risk Mitigation Planning
Include Contingency Timelines:
- “If vendor A is unavailable, vendor B adds 30 days to timeline”
- “Budget approval delay moves start date from March 1 to April 1”
- “Critical dependency: legal review must complete by February 15”
Return to Explicit Ask
$ confirm –commitment –next-steps
“Close the loop. Restate what you need. Check for agreement. Don’t let the room drift into ‘interesting discussion’ territory.”
The Core Principle
“The final step is to return to your explicit ask and ensure you get the information or guidance you need.”
— Will Larson, An Elegant Puzzle
Why This Step Matters
⚠️ Without Explicit Closure:
- Meetings end with “interesting discussion” but no decisions
- Your ask gets lost in side conversations
- Stakeholders think they provided input but didn’t commit resources
- Follow-up becomes “let’s schedule another meeting”
How to Execute the Close
Restate Your Primary Ask:
- “To confirm: I need $200K budget approval and legal review”
- “What I’m asking for is headcount authorization for 2 FTE”
- “The decision I need is vendor selection by Friday”
Check for Explicit Agreement:
- “Do I have budget approval to proceed?”
- “Can you commit to the March 15 timeline?”
- “What questions do you have about this recommendation?”
Different Types of Closes
| Close Type | Example Phrases |
|---|---|
| Budget/Resource Approval |
• “Do I have approval for the $X investment?” • “Can you authorize the headcount request?” • “When can I expect the budget decision?” |
| Input/Expertise Request |
• “What technical considerations am I missing?” • “How does this integrate with your team’s priorities?” • “What implementation risks should I address?” |
| Decision/Timeline Commitment |
• “Can you decide by [date]?” • “Will you support this timeline?” • “What would change your mind on this recommendation?” |
Authority Language for Closing
Weak Endings
- “So… what do you think?”
- “Does this make sense to everyone?”
- “I guess that’s everything I wanted to cover”
❌ Uncertain, seeking validation
Confident Conclusion
- “I’m ready to execute this plan. What questions do you have?”
- “This approach solves the problem. Do I have your support to proceed?”
- “Based on this analysis, I recommend immediate approval. What concerns do you have?”
✅ Confident, invitation for questions
Managing the “Interesting Discussion” Trap
When Conversations Drift to Theoretical Discussion:
- “That’s an interesting point for future consideration. For this decision, what I need is…”
- “Let me capture that for follow-up. On the immediate ask…”
- “Good discussion. To move forward, the decision I need is…”
Follow-Up Commitment
Get Specific Next Steps:
- “I’ll send you the detailed proposal by [date]”
- “You’ll have the budget decision by [date]”
- “We’ll reconvene on [date] with vendor quotes”
Authority Positioning
You’re Not Begging for Approval:
- Position as coordination, not permission-seeking
- Demonstrate readiness to execute
- Show confidence in the recommendation
- Take ownership of next steps
Authority vs Permission: The Mindset Shift
The Problem: The Permission Trap
Most technical leaders fall into the “permission trap” without realizing it. You present thorough analysis, but your language signals instead of .
Self-Assessment
❌ Permission Language (Signals Uncertainty)
- “Will you support me in doing X?”
- “Do you think we should consider Y?”
- “Can I get approval to explore Z?”
- “I wanted to discuss some options…”
- “Would you be open to looking at alternatives?”
- “What do you think about…”
- “I’m wondering if we should…”
✅ Authority Language (Signals Expertise)
- “I recommend we implement X. Here’s why.”
- “Based on my analysis, Y is the optimal approach.”
- “I need Z resources to execute this plan.”
- “I recommend we transition to Option A by Q2.”
- “My analysis shows Alternative B delivers the best ROI.”
- “The data supports…”
- “I’m ready to execute…”
What Executives Hear
| When You Say… | Executives Hear… |
|---|---|
| “Will you support me in exploring this?” | “I’m not sure this is the right answer.” |
| “I recommend we implement this solution.” | “This person has done the analysis and knows what to do.” |
Career Impact
❌ Permission Seekers Get:
- Requests for “more analysis”
- Delayed decision-making
- Reduced executive confidence
- Fewer high-stakes projects
✅ Authority Demonstrators Get:
- “What do you need to make this happen?”
- Faster approvals and resource allocation
- Increased executive trust
- Leadership opportunities
Real-World Example
❌ Before (Permission-Seeking)
“Hi everyone, I wanted to discuss some issues we’ve been having with our current system. There have been several problems over the past few months, and I’m wondering if we should consider looking at alternatives. I’ve done some preliminary research and found a few options that might work better. Would you be willing to support me in exploring this further? I think it could save us money, but I wanted to get your thoughts first.”
Problems with this approach:
- Buries the recommendation in problems
- Asks for permission to think about solutions
- Uses uncertain language (“I think,” “might,” “wondering”)
- No specific ask or timeline
- Makes executives do the work of determining next steps
✅ After (Authority-Based)
“I recommend we migrate from System A to System B by Q3. This eliminates our current performance issues, saves $75K annually, and improves our compliance posture. Our current system has degraded 40% over six months due to scale limits. Migration requires $200K investment with 18-month ROI. What questions do you have about this recommendation?”
Why this works better:
- Leads with clear recommendation and business value
- Provides concise context and urgency
- Makes specific resource request
- Owns the timeline and implementation
- Positions as expert coordinating execution
The Mindset Shift
❌ Old Mindset: “I need permission to be heard”
- Asking for approval to think about problems
- Apologizing for bringing up issues
- Seeking consensus before making recommendations
- Deferring to others’ judgment over your analysis
✅ New Mindset: “I’m the expert providing recommendations”
- Making business recommendations based on analysis
- Owning your expertise and judgment
- Requesting resources to execute solutions
- Coordinating stakeholders around your plan
Ready-to-Use Templates
Executive Brief Template (2-Page Max)
# [Topic]: Executive Recommendation **Date:** [Date] **To:** [Stakeholder Names and Titles] **From:** [Your Name and Title] **Subject:** [Clear Action-Oriented Subject] --- ## 1. Business Value & Recommendation I recommend [specific action] to [achieve business outcome]. This [saves/enables/eliminates] $[amount] [timeframe] while [additional strategic benefit]. ## 2. How We Got Here [Current situation - 1 sentence]. [How we arrived here - 1 sentence]. [What's at stake if no action - 1 sentence]. ## 3. What I Need From You **Primary ask:** [Specific resource, decision, or input with timeline] **Secondary asks:** [Additional support that would improve outcomes] ## 4. Supporting Analysis **Key Metric 1:** [Data point with source and business relevance] **Key Metric 2:** [Data point with source and business relevance] **ROI Analysis:** [Investment required, payback timeline, total value] **Risk Mitigation:** [Primary concern and how you've addressed it] ## 5. Decision Framework My approach prioritizes: 1. [Principle 1 with business reasoning] 2. [Principle 2 with trade-off explanation] 3. [Principle 3 with strategic alignment] ## 6. Implementation Plan **Phase 1** ([dates]): [Key activities and milestones] **Phase 2** ([dates]): [Key activities and milestones] **Completion** ([date]): [Final deliverables and success criteria] ## 7. Next Steps [Restate primary ask]. [Specific commitment or decision needed]. What questions do you have about this recommendation? --- *Detailed analysis, alternative evaluations, and technical specifications available in supporting documentation upon request.*
Quick Email Templates
Decision Request Email
Subject: [Specific Decision] Needed by [Date] - [Brief Business Impact] [Executive Name], I recommend [specific action] to [business outcome]. This [quantified impact] with [timeline]. Context: [2-3 sentences on situation and urgency] I need: [Specific decision/approval] by [date] to [maintain timeline/capture opportunity]. Supporting analysis attached. Questions? [Your name]
Status Update with Authority
Subject: [Project Name] Status - [Key Milestone] Achieved, [Next Decision] Needed [Executive Name], Status: [Project] is [on track/ahead/behind] with [key achievement]. Next decision needed: [Specific ask] by [date] for [business reason]. Key metrics: - [Metric 1]: [Status vs. target] - [Metric 2]: [Status vs. target] - Timeline: [Current phase] completing [date], [next phase] starting [date] Risks: [Primary concern] mitigated by [action taken/planned]. Questions or input needed on [specific area]? [Your name]
Quick Reference Cards
Framework Timing Cheat Sheet
| Step | Time Limit | Core Question |
|---|---|---|
| 1. Business Value | 30 seconds | Why should anyone care? |
| 2. Historical Narrative | 30 seconds | How did we get here? |
| 3. Explicit Ask | 30 seconds | What exactly do you need? |
| 4. Data-Driven Diagnosis | 2 minutes | What’s the evidence? |
| 5. Decision Principles | 1 minute | What’s your framework? |
| 6. Timeline & Next Steps | 30 seconds | When and how? |
| 7. Return to Ask | 30 seconds | Did we get commitment? |
| Total Structured Time | ~5 minutes + Q&A | |
Authority Language Power Phrases
✅ USE THESE:
- “I recommend…”
- “Based on my analysis…”
- “I need…”
- “This delivers…”
- “My assessment shows…”
- “The data supports…”
- “I’m ready to execute…”
❌ AVOID THESE:
- “I wanted to discuss…”
- “What do you think about…”
- “Can we maybe…”
- “I think maybe…”
- “Would you be willing…”
- “We might…”
- “I’m wondering if…”
Pre-Meeting Checklist
| Phase | Checklist Items |
|---|---|
| Before Meeting |
☐ 2-page brief prepared following framework ☐ Supporting data and appendix ready ☐ Stakeholder-specific adaptations considered ☐ Likely objections identified with responses ☐ Specific asks clearly defined with amounts/timelines |
| During Meeting |
☐ Lead with business value in opening 30 seconds ☐ Stay within time allocations for each step ☐ Be ready for detours but return to framework ☐ Make specific asks and get explicit commitments ☐ Document agreements and next steps |
| After Meeting |
☐ Follow up with agreed timeline and deliverables ☐ Send meeting summary with commitments documented ☐ Execute next steps and report progress ☐ Apply lessons learned to future presentations |
Business Value Framing Quick Reference
| Impact Type | Template |
|---|---|
| Revenue Impact |
“This enables $[amount] in new revenue by [capability]” “This saves $[amount] annually by [eliminating cost]” |
| Risk Mitigation |
“This eliminates [risk] that threatens $[impact]” “This prevents potential $[cost] in [penalties/losses]” |
| Strategic Positioning |
“This positions us for [opportunity] by enabling [capability]” “This enables expansion into [market] worth $[size]” |
Primary Source: “An Elegant Puzzle: Systems of Engineering Management” by Will Larson
Section 3.13: “Presenting to senior leadership”
One Comment