Communicating Strategy to Execs

How Executives Process Information

Executives think about information differently than engineers do. They're switching between 15 different topics in a single day. They don't have time to dig into your architecture diagrams. Your job is to make the decision as easy as possible by organizing your message around how they think: What's the problem? What do you recommend? What does it cost? What happens if we do nothing?

The Pyramid Principle

Barbara Minto's Pyramid Principle is probably the most effective framework for talking to executives. Start with the answer, your recommendation. Then provide the key supporting arguments (three at most). Under each argument, lay out the evidence. This structure means the executive can stop reading at any level and still get the point.

Example structure:

• Recommendation: Invest 2 engineering sprints in migrating the checkout service to the new platform.
• Argument 1: Current checkout reliability sits at 99.2%, costing an estimated $180K/month in failed transactions.
• Argument 2: The migration will push reliability to 99.95%, recovering roughly $150K/month.
• Argument 3: Delaying raises the stakes further since the current platform loses vendor support in Q3.

Metric-First Communication

Every slide should open with a number. Not "We plan to improve system performance" but "P99 latency will drop from 1.2s to 200ms, directly impacting our 23% cart abandonment rate." Executives trust numbers because numbers let them compare across departments. If you show up without metrics, your initiative will lose priority to the sales team that came prepared with a pipeline forecast.

Handling "Just Make It Faster"

When an executive says "just make it faster" or "why can't we do both," don't launch into a full explanation of every constraint. Instead, put options on the table:

• Option A (Fast): Ship a partial solution in 2 weeks that addresses the top complaint. Risk: you take on technical debt and have to revisit in Q3.
• Option B (Right): Full solution in 6 weeks. Addresses the root cause with no rework needed. Cost: the mobile feature slips by one sprint.
• Option C (Cheap): Invest 3 days in a mitigation that reduces impact by 60%. Buys time to do Option B next quarter.

Let the executive pick. This respects their authority while making sure they understand what they're trading off. Document both the decision and the trade-off they accepted. That protects the engineering team if consequences show up later.

The Five-Slide Format

1. The Problem: One metric that shows the pain. One sentence of context.
2. The Impact: What happens if we do nothing. Revenue at risk, incident trends, competitive disadvantage.
3. The Recommendation: What you want to do. One paragraph, maximum.
4. The Trade-offs: Options A/B/C with cost, timeline, and risk for each.
5. The Ask: What decision you need, from whom, and by when.

Everything else goes in the appendix. If they want to go deeper, they'll ask. Most of the time, they won't.