| name | executive-communication-narrative-mapping |
| description | A framework for structuring product presentations and updates to executives to avoid being "in the weeds" or "too high level." Use it when preparing for formal product reviews, seeking buy-in for non-sexy investments (like technical debt), or escalating high-stakes trade-off decisions. |
Executive Communication Narrative Mapping
To communicate effectively upward, you must view your work as a story and identify exactly which "chapter" your audience is ready to read. Executives often feel "out of touch" because PMs start the story too late (in the weeds) or too early (re-explaining basic strategy), leading to misalignment and wasted time.
The "Chapters of the Story" Framework
When presenting to leadership, categorize your information into these stages:
- Chapter 1 (The Foundation): The company strategy and how your work maps to it.
- Chapters 2-4 (The Logic): The specific metrics you are trying to improve and the core assumptions guiding your solution.
- Chapter 5 (The Pivot): The specific trade-offs or problems you are currently facing.
- Chapter 6 (The Execution): The granular implementation details, specific UI changes, or technical specs.
The "Optimal Starting Point" Rule
Do not start at Chapter 1 if the audience already knows it, but never start at Chapter 6.
- The Goal: Find the last point in your story that would be completely obvious to the person you are talking to. Start exactly one sentence after that.
- The Trap: Most non-executives start at Chapter 6. They skip the strategy, metrics, and assumptions, and go straight to the "big reveal." This causes executives to ask questions "in a different language" because they lack the context of the previous five chapters.
De-Risking the Meeting
High-stakes meetings should never have a "Big Reveal" or a "Success/Fail" moment. Use these three tactics to ensure a positive outcome:
1. The Pre-Meeting (The "No Surprises" Rule)
Meet with key individuals (e.g., the CFO or a specific VP) 1-on-1 before the big presentation.
- Goal: Surface their major concerns privately.
- Outcome: You can weave the answers to their concerns into your main presentation before they even have to ask.
2. Executive Personas Roleplay
During prep, have your team or manager "impersonate" the specific executives who will be in the room.
- The CFO Persona: Will ask about cost, efficiency, and ROI.
- The CEO Persona: Will ask about "Why this now?" and long-term vision.
- The Head of Product Persona: Will ask about data context, user research, and edge cases.
3. The Data "Confidence Test"
Executives often ask 2-3 early, specific data questions as a "stress test." If you don't know the answers, it casts doubt on the entire strategy.
- Preparation: Identify the "Universe of Questions" that could be asked from your document. Have the raw data ready for the "boring" context (e.g., current conversion rates, specific segment sizes) to build immediate credibility.
Examples
Example 1: Presenting a New Feature
- Context: A PM is presenting a new automated marketing tool for creators.
- Input: The PM has the final UI mocks and a list of features.
- Application: Instead of starting with the mocks (Chapter 6), the PM starts with Chapter 2: "Our assumption is that creators aren't professional marketers and need automation to grow." They then link this to Chapter 1: "This supports our strategy of creator retention."
- Output: The executive team stays aligned on the intent of the feature rather than nitpicking the button colors.
Example 2: Escalating a Resource Trade-off
- Context: A team is behind on a goal because they chose to fix a major performance bug.
- Input: A missed OKR and a technical report.
- Application: The PM escalates by explaining the "Chapter 5" trade-off: "We prioritized stability over the new feature because we identified a risk to the gains we've already built."
- Output: The CPO can help "change the circumstances" or help communicate the trade-off to the rest of the company, preventing the executive team from feeling blindsided by a missed metric.
Common Pitfalls
- Starting at the "English Alphabet": Spending the first 20 minutes re-explaining the company mission or things everyone already knows. You will run out of time before reaching the new information.
- Treating "Executives" as a Monolith: Ignoring that the CFO and CEO have different styles. Tailor the content to the specific individuals in the room.
- Confusing "Handling it" with "Leadership": Thinking that being a leader means suffering through a bad situation in silence. Effective leaders escalate early so executives can help change the circumstances.
- Under-preparing for Contextual Questions: Being an expert on the new feature but failing to know the current metrics of the business. This signals that you lack the context to make a strategic decision.
