Transform data into compelling executive narratives using the What/Why/Next framework from Gartner research
/plugin marketplace add cameronsjo/claude-marketplace/plugin install executive-data-storytelling@cameronsjoThis skill inherits all available tools. When active, it can use any tool Claude has access to.
QUICK_START.mdREADME.mdSKILL_SUMMARY.mdTEST_PROMPTS.mdresources/ceo-priorities-2024.mdresources/chart-selection-guide.mdresources/depersonalization-checklist.mdresources/narrative-template.mdresources/pre-presentation-checklist.mdscripts/analyze-presentation.pyscripts/narrative-validator.pyTransform data and metrics into compelling narratives that drive executive action and support using proven frameworks from Gartner research.
This skill provides a systematic framework for creating data-driven narratives that engage executive leadership teams (ELTs). Based on Gartner's "Use Data Storytelling to Engage the Executive Leadership Team" research (G00818015, September 2024), this skill teaches you to align metrics with executive priorities, craft compelling narratives using the What/Why/Next structure, and present insights in visually appealing, action-oriented formats.
High-performing ELTs use data and analytics for 84% of their decisions, yet executives often struggle with operational metrics instead of strategic storytelling. This skill bridges that gap by teaching proven techniques for translating technical data into executive-ready insights.
Trigger this skill when you need to:
Keywords: executive presentation, board memo, ELT update, data storytelling, executive dashboard, business case, quarterly review, stakeholder communication, C-suite presentation, leadership briefing, board deck, executive summary
Why Traditional Data Presentations Fail:
The Executive Context:
Step 1: Identify Metrics That Align With Executive Peers' Key Priorities
Understand what keeps your executive peers awake at night. Don't present metrics in isolation - connect them to broader strategic priorities.
CEO Business Priorities (2024 Gartner Research):
Strategic Alignment Questions:
Language Mirroring:
Step 2: Draft a Compelling Data-Based Narrative
Use the What/Why/Next structure adapted from Blake Snyder's "Save the Cat" storytelling method:
WHAT (Opening Image):
WHY (Catalyst):
NEXT (Break Into Two):
Narrative Flow Example:
WHAT: Our premium lead program increased qualified opportunities by 35% in Q2,
contributing $12M in pipeline toward our $50M growth target.
WHY: Premium leads receive personalized outreach within 4 hours (vs. 48 hours
for standard leads), resulting in 3x higher engagement rates. Sales teams
prioritized these leads, achieving 58% conversion vs. 19% baseline.
NEXT: Expand premium lead criteria to include mid-market accounts (currently
enterprise-only) to capture an additional $8M in Q3 pipeline. This requires
adding 2 SDRs and automating lead scoring. Investment: $120K. ROI: 67x.
Step 3: Create Concise, Visually Appealing Presentation
Slide Design Principles:
Visual Design Checklist:
Effective Chart Selection:
Anti-Patterns to Avoid:
Creating Analogies for Difficult Topics:
Complex technical concepts need translation for executive audiences.
Examples:
Formula: [Complex concept] is like [familiar thing] because [key similarity]
Emotional Resonance Check:
Before finalizing, ask:
Use this template to draft your executive narrative before creating slides:
## [Metric/Initiative Name]
### WHAT (Current State)
- Primary metric: [number] [unit] vs. [target/baseline]
- Connection to CEO priority: [Growth/Technology/Workforce/Financial]
- Current trajectory: [on track/ahead/behind]
- Context: [why this metric matters to ELT strategic goals]
### WHY (Root Cause Analysis)
- Primary driver: [data-backed explanation]
- Supporting evidence: [specific numbers, trends, comparisons]
- Contributing factors: [2-3 additional elements with data]
- Depersonalized challenges: [focus on problem, not blame]
### NEXT (Recommendations)
- Recommendation 1: [specific action] → [expected outcome] in [timeframe]
- Investment required: [resources, budget, headcount]
- Success metrics: [how we'll measure impact]
- Risk/trade-offs: [what we give up or risk]
- [Optional] Recommendation 2: [alternative approach]
- Comparison to Recommendation 1: [trade-offs]
### Decision Required
[Specific ask: approval, feedback, resources, priority decision]
Standard structure for ELT presentations:
Slide 1: Title & Executive Summary
- Initiative/topic name
- One-sentence summary of key insight
- Decision required or action requested
Slide 2: Current State (WHAT)
- Primary metric(s) with visual
- Alignment with strategic priority
- Current status vs. target
Slide 3: Root Cause (WHY)
- Data-driven explanation
- Supporting evidence chart
- Key insights from analysis
Slide 4: Recommendations (NEXT)
- Option 1 with outcomes
- [Optional] Option 2 with trade-offs
- Clear comparison if multiple options
Slide 5: Next Steps & Timeline
- Specific actions with owners
- Timeline with milestones
- Success metrics and tracking plan
[Appendix: Supporting data, detailed analysis, FAQs]
Use this to map your metrics to executive priorities:
## Priority Alignment Matrix
### Your Metric/Initiative: [Name]
| Executive | Primary Priority | How This Connects | Language to Use |
|-----------|------------------|-------------------|-----------------|
| CEO | [Growth/Tech/etc]| [Specific link] | [Exact phrases] |
| CFO | [Financial/etc] | [ROI, efficiency] | [Budget terms] |
| COO | [Ops/Workforce] | [Process impact] | [Ops metrics] |
| CRO | [Revenue/Growth] | [Pipeline, sales] | [Revenue terms] |
| CTO/CIO | [Technology] | [Tech impact] | [Tech strategy] |
| CHRO | [Workforce] | [People impact] | [Talent terms] |
### Stakeholder Analysis
- **Who is affected**: [List executives/departments]
- **Who must approve**: [Decision makers]
- **Who must support**: [Implementation partners]
- **Potential objections**: [Concerns by stakeholder]
Context: Chief Commercial Officer (CCO) presenting Q2 results to ELT
WHAT (Opening Image): "Our premium lead program increased qualified opportunities by 35% in Q2, adding $12M to pipeline and putting us 24% ahead of our $50M quarterly growth target."
Connection to CEO Priority: Growth (59% priority) - directly impacts revenue pipeline
WHY (Catalyst): "Premium leads receive personalized outreach within 4 hours versus 48 hours for standard leads, resulting in 3x higher engagement rates (58% vs. 19%). Sales teams prioritized these leads based on clear scoring criteria, and the shorter response time prevented leads from exploring competitor solutions."
Data Points:
NEXT (Break Into Two): "Recommendation: Expand premium lead criteria to include mid-market accounts, currently limited to enterprise. This will capture an estimated $8M additional pipeline in Q3.
Investment: $120K (2 SDRs + lead scoring automation) ROI: 67x return Timeline: 6 weeks to implement Risk: Requires sales team training on mid-market qualification
Alternative: Maintain current enterprise-only focus and increase marketing spend to generate more volume. Lower ROI (12x) but faster implementation (2 weeks)."
Emotional Tone: Inspired - shows unexpected success and path to exceed targets
Slide Structure:
Context: CIO presenting innovation initiative results to ELT
WHAT (Opening Image): "Design thinking labs generated 47 employee-submitted ideas in Q1, resulting in 3 prototypes now in pilot phase. These innovations target $2.3M in operational cost savings, supporting our financial efficiency goals."
Connection to CEO Priority: Technology (29%) + Financial (22%) - innovation driving efficiency
WHY (Catalyst): "The lab structure removed hierarchical approval barriers that previously delayed ideas by 6-8 months. Cross-functional teams (engineering, operations, customer success) identified pain points that individual departments missed. The rapid prototyping process (2-week sprints) validated ideas 10x faster than traditional development."
Data Points:
NEXT (Break Into Two): "Recommendation: Expand labs from 1 to 3 locations (Austin, Bentonville, Seattle) to include regional operational teams. Expected outcome: 150+ ideas annually, 10-12 pilots, $8M-12M in savings/efficiency gains.
Investment: $450K annually (lab space, facilitators, prototyping tools) ROI: 18x-27x return on projected savings Timeline: Q3 launch for Austin and Bentonville, Q4 for Seattle Success Metrics: Ideas submitted, pilot conversion rate, realized savings
Risk: Requires executive sponsorship to maintain cross-functional participation. Without active CXO support, attendance drops and idea quality suffers."
Emotional Tone: Reassured - early results validate investment, expansion is logical next step
Slide Structure:
Context: CISO presenting post-incident analysis to board
WHAT (Opening Image): "On May 15, we detected and contained a credential stuffing attack within 47 minutes. Zero customer data was compromised. Our incident response time was 83% faster than industry average (4.5 hours)."
Connection to CEO Priority: Technology (risk management) + Financial (avoiding breach costs)
WHY (Catalyst): "The attack exploited recycled passwords from a third-party breach (not our systems). Our automated threat detection identified 12,000 failed login attempts within 2 minutes and triggered account lockdowns. The security team's pre-defined playbook enabled rapid containment without executive escalation during off-hours.
However, the attack exposed a gap: 23% of customer accounts still use weak passwords despite our password policy updates in March. These accounts remain vulnerable to similar attacks."
Data Points:
NEXT (Break Into Two): "Recommendation: Implement mandatory multi-factor authentication (MFA) for all customer accounts by end of Q3.
Impact: 99.9% reduction in credential-based attack risk Investment: $85K (MFA provider, implementation, customer communication) Timeline: 12 weeks (phased rollout) Customer Experience: Minor friction (30-second setup), significant security benefit Risk: 5-8% of customers may contact support during rollout
Alternative: Make MFA optional with incentives (discounts, premium features). Lower implementation cost ($30K) but only 40-50% adoption based on industry data, leaving half our customers vulnerable."
Emotional Tone: Reassured (rapid response) + Concerned (remaining vulnerability) + Confident (clear solution)
Slide Structure:
Context: CHRO presenting retention initiative to ELT
WHAT (Opening Image): "Engineering turnover decreased from 24% to 11% following our retention program launch in Q4 2023. This prevented an estimated $4.8M in replacement costs and preserved critical product knowledge for our AI roadmap."
Connection to CEO Priority: Workforce (25%) + Technology (29%) - retaining AI/ML talent
WHY (Catalyst): "Exit interviews revealed that 67% of departing engineers cited limited career growth and skills development as primary factors. The retention program addressed this with:
The combination increased internal promotion rate from 8% to 22% and created clear growth paths that competing offers couldn't match."
Data Points:
NEXT (Break Into Two): "Recommendation: Expand retention program to product management and data science teams (combined 145 employees), where turnover remains elevated at 19%.
Investment: $580K annually ($435K learning budgets + $145K program administration) Expected Outcome: Reduce turnover to 10-12%, avoid $2.1M in replacement costs Timeline: Launch in Q4 2024 ROI: 3.6x in year one, higher in subsequent years as knowledge retention compounds
Alternative: Target only "flight risk" employees (top 20% identified via stay interviews). Lower cost ($190K) but doesn't address systemic career growth issues, likely resulting in continued turnover of mid-tier talent."
Emotional Tone: Inspired - unexpected success in competitive talent market
Slide Structure:
One of the most difficult aspects of executive storytelling is presenting failures or challenges without sounding defensive or making excuses. Executives respect transparency and data-driven analysis of what went wrong.
Focus on the problem, not the people:
❌ Personalized (Defensive):
✅ Depersonalized (Analytical):
1. Use Passive Voice Strategically
While active voice is generally preferred, passive voice can depersonalize failures:
2. Focus on Systems and Processes
Identify systemic issues rather than individual or team failures:
3. Use Data to Explain Causality
Let numbers tell the story:
4. Externalize Where Appropriate
When external factors genuinely contributed, state them clearly:
5. Acknowledge Lessons Learned
Show growth and adaptation:
When presenting failures or setbacks:
## [Failed Initiative/Missed Target]
### Current State (Data-First)
- Target: [what was expected]
- Actual: [what was achieved]
- Gap: [quantified shortfall]
### Root Cause Analysis (Depersonalized)
- Primary factor: [systemic issue with data]
- Contributing factors: [2-3 additional elements]
- External dependencies: [vendor, market, regulatory issues if applicable]
### Lessons Learned (Forward-Looking)
- Process changes implemented: [specific improvements]
- New controls/safeguards: [what prevents recurrence]
- Updated assumptions: [what we now know]
### Path Forward (Action-Oriented)
- Revised approach: [what changes]
- New timeline: [realistic projection]
- Success criteria: [how we'll measure]
❌ Defensive Version: "We launched the mobile app but didn't get the adoption we hoped for. The team worked really hard, but we probably should have done more marketing. We're going to try to fix it with a redesign."
✅ Depersonalized Version: "Mobile app adoption reached 8,400 downloads vs. 25,000 target in first 30 days. Post-launch analysis identified three primary factors:
Process improvements implemented:
Revised plan targets 18,000 downloads by end of Q3 with optimized app store presence and streamlined onboarding."
The Pyramid Principle:
Structure information from conclusion to supporting details:
Slide Title (Conclusion/Insight)
↓
Key Point (3-5 words)
↓
Supporting Data (chart or bullets)
↓
Recommendation (if applicable)
Example:
Premium Leads Increase Pipeline 35%
↓
Q2 qualified opportunities: +$12M vs. target
↓
[Chart showing lead conversion: Premium 58% vs. Standard 19%]
↓
Expand to mid-market accounts: +$8M Q3 opportunity
Line Charts (Trends Over Time):
Bar Charts (Comparisons):
Pie Charts (Parts of Whole):
Tables (Detailed Data):
Strategic Color Use:
Color Guidelines:
Font Selection:
Readability Rules:
Recommended Deck Flow:
Total Main Deck: 7-12 slides maximum for 30-minute meeting
Appendix: Unlimited supporting slides, referenced as needed
Best Practices:
Problem: Using department-specific acronyms and terminology that other executives don't understand.
Example: ❌ "Our MAU increased 23% QoQ, driving MQL-to-SQL conversion up 15 bps, resulting in improved LTV:CAC ratio from 3.2 to 4.1."
Solution: Define acronyms on first use or eliminate them entirely. Use plain language.
✅ "Monthly active users increased 23% this quarter. More users engaged with content, leading 15% more prospects to request sales conversations. This improved our customer acquisition economics: we now earn $4.10 for every $1 spent on acquisition, up from $3.20."
Prevention Strategy:
Problem: Starting with background and building to conclusion, exhausting executive patience before reaching the point.
Example: ❌ Slide 1: Market overview ❌ Slide 2: Historical trends ❌ Slide 3: Methodology ❌ Slide 4: Data collection ❌ Slide 5: Analysis results ❌ Slide 6: Finally, the insight and recommendation
Solution: Lead with the insight, support with data, provide details in appendix.
✅ Slide 1: "Premium leads increase pipeline 35% - recommend expanding to mid-market" ✅ Slide 2: Supporting data and analysis ✅ Slide 3: Implementation plan ✅ Appendix: Methodology, detailed data, historical context
Prevention Strategy:
Problem: Presenting data without explaining why it matters or what should be done.
Example: ❌ "Website traffic increased 47% quarter-over-quarter." (Executive thinks: "Is that good? Why did it happen? What do you want me to do?")
Solution: Always connect data to strategic implications and recommendations.
✅ "Website traffic increased 47% quarter-over-quarter, driven by our content marketing investment. This traffic generated 1,200 qualified leads, contributing $3.2M to pipeline and putting us ahead of our $12M quarterly growth target. Recommend doubling content investment in Q3 to sustain momentum, requiring $85K additional budget."
Prevention Strategy:
Problem: Slides with 8-12 bullet points of dense text.
Example: ❌ Slide with 10 bullets, each containing 2-3 lines of text, tiny font, impossible to read
Solution: Apply the 3-5 bullet rule ruthlessly. Convert dense text to visuals.
✅ Slide with:
Prevention Strategy:
Problem: Presenting departmental wins that don't connect to CEO or ELT strategic priorities.
Example: ❌ Engineering leader presents: "We reduced technical debt by 35% and improved code coverage to 87%" (Executive thinks: "Why should I care? How does this help us grow or improve margins?")
Solution: Always connect departmental metrics to strategic priorities.
✅ "We reduced technical debt by 35%, enabling the team to ship features 40% faster. This acceleration directly supports our product roadmap, allowing us to launch the enterprise tier in Q3 (2 months ahead of schedule) and capture an additional $4.5M in revenue this year."
Prevention Strategy:
Problem: Ending with unclear next steps or asking executives to figure out what to do.
Example: ❌ "We should explore options to improve customer retention." ❌ "More resources would help accelerate delivery." ❌ "Leadership should consider investing in this area."
Solution: Provide specific, actionable recommendations with clear outcomes.
✅ "Implement automated customer health scoring to identify at-risk accounts 30 days earlier. Investment: $45K (software + implementation). Expected outcome: Reduce churn from 8% to 5%, retaining $1.8M in annual recurring revenue. Timeline: 8 weeks to launch. Decision needed: Budget approval and assignment of CS ops lead."
Prevention Strategy:
Problem: Making excuses or deflecting blame when presenting challenges or failures.
Example: ❌ "We didn't hit targets because the market changed and we didn't have enough resources and the requirements kept changing."
Solution: Use depersonalization techniques and focus on data-driven analysis.
✅ "Q2 revenue reached $8.2M vs. $10M target. Analysis identified three factors: (1) Enterprise sales cycle extended from 90 to 120 days due to increased budget scrutiny, (2) Product gaps in compliance features delayed 40% of deals, (3) Competitive pricing pressure reduced average deal size 18%. Mitigation plan: Accelerate compliance roadmap (launch Q3), introduce flexible payment terms for extended cycles, revise Q3 targets to reflect market reality."
Prevention Strategy:
Problem: Presenting data without sources, using inconsistent time periods, or mixing incompatible metrics.
Example: ❌ Slide 1: Q2 revenue (fiscal calendar) ❌ Slide 2: June customer growth (monthly) ❌ Slide 3: YTD pipeline (Jan-Jul, 7 months) ❌ No indication of data sources or calculation methods
Solution: Use consistent time periods, clearly label data sources, define calculation methods.
✅ All slides use fiscal Q2 (Apr-Jun 2024) ✅ Footnotes indicate: "Source: Salesforce, as of Jul 1, 2024" ✅ Appendix defines: "Pipeline = Qualified opportunities in Stage 3+, weighted by probability"
Prevention Strategy:
The most effective executive narratives don't just present data - they evoke emotion that influences decision-making.
Surprise: Highlight unexpected results that challenge assumptions
"Despite reducing marketing spend 20%, lead generation increased 34%. Analysis revealed that our highest-ROI channels (webinars, partner referrals) were previously under-funded."
Use when: Results contradict conventional wisdom or initial expectations
Inspiration: Paint a vision of what's possible
"This breakthrough in automated underwriting positions us to dominate the SMB lending market within 18 months. No competitor can match our 4-minute approval time, and early adopters show 3x higher retention."
Use when: Presenting transformative opportunities or early wins that signal larger potential
Reassurance: Demonstrate control and stability during uncertainty
"While Q2 revenue was flat, underlying metrics remain healthy: customer retention at 94% (vs. 91% industry average), pipeline up 28% QoQ, and product NPS increased from 42 to 58. The revenue pause reflects timing of large deals shifting to Q3, not demand issues."
Use when: Navigating challenges, maintaining confidence during short-term setbacks
Concern: Highlight risks that require immediate attention (use sparingly)
"Customer acquisition cost increased 67% in six months while competitor CAC remained flat. At current trajectory, our unit economics become unprofitable in Q4. This requires immediate action."
Use when: Urgent issues need executive prioritization or resource allocation
Technique: Consciously choose emotional tone for each section of narrative. Mix emotions within presentation to maintain engagement (e.g., concern about current state, inspiration about opportunity).
Don't wait for the formal presentation to introduce your narrative.
Pre-Meeting Strategy:
Benefits:
1:1 Script Template:
"I'm presenting [initiative] to ELT next week. The core recommendation is [summary]. I wanted to get your perspective first:
Your feedback will help me address potential objections proactively."
Build confidence with comprehensive supporting detail while keeping main deck concise.
What Goes in Appendix:
Main Deck vs. Appendix Decision:
Ask: "Does the executive need this to make the decision?"
Appendix Organization:
Main Deck: Slides 1-10
Appendix:
A. Methodology (Slides 11-13)
B. Detailed Financial Analysis (Slides 14-17)
C. Competitive Benchmark (Slides 18-20)
D. Implementation Plan (Slides 21-24)
E. Risk Assessment (Slides 25-27)
F. FAQ (Slides 28-30)
Navigation Strategy:
Make it crystal clear what you need from the executive audience.
Decision Types:
Framework Application:
Include explicit "Decision Required" section on final slide:
## Decision Required
**Type**: Approval
**Ask**: Approve $450K investment to expand design thinking labs to 3 locations
**Options**:
- Option 1 (Recommended): Full expansion to Austin, Bentonville, Seattle - $450K, 18x-27x ROI
- Option 2: Pilot one additional location first - $180K, validate model before full expansion
- Option 3: Maintain current state - $0, forgo estimated $8M-12M in efficiency gains
**Timeline**: Decision needed by Aug 15 to launch in Q3
**Next Steps**:
- If approved: Kickoff meetings week of Aug 19
- If Option 2: Pilot selection decision required
- If Option 3: Redirect team to other initiatives
Benefits:
Ensure every piece of data connects to executive priorities through layered implications.
Cascade Structure:
Data Point
↓ So what?
Operational Implication
↓ So what?
Business Implication
↓ So what?
Strategic Implication (connects to CEO priority)
Example:
"Website page load time decreased from 4.2s to 1.8s"
↓ So what?
"Bounce rate dropped from 58% to 32%"
↓ So what?
"More visitors engage with content and product pages"
↓ So what?
"Conversion rate increased 23%, generating 840 additional leads per month"
↓ So what?
"This contributes $2.1M to quarterly pipeline, accelerating our path to $50M growth target (CEO Priority: Growth)"
Application: For every metric you present, trace the cascade from technical detail to strategic impact. Present the strategic implication first, support with the cascade if questioned.
Frame your recommendations in competitive context to create urgency.
Positioning Strategies:
1. First-Mover Advantage: "Our AI-powered customer service reduces resolution time by 60%. No competitor has deployed this capability at scale. Launching in Q3 positions us 6-9 months ahead of competitive response, capturing early adopter segment."
2. Defensive Play: "Competitor X announced mobile-first redesign last month. Our current mobile experience lags behind (App Store rating: 3.2 vs. their 4.6). Without investment in mobile, we risk losing 35% of our user base (mobile-first millennials) over next 12 months."
3. Leapfrog Strategy: "While competitors focus on incremental improvements to legacy systems, we have opportunity to leapfrog with cloud-native architecture. This enables capabilities they can't match without complete platform rebuild (estimated 2-3 years for them)."
4. Market Expansion: "Our enterprise solution succeeded in financial services (35% market penetration). Healthcare vertical shows similar characteristics and $400M TAM, but only 2 competitors present. Early entry captures market leadership before segment matures."
Framework:
## Competitive Context
### Current Position
- Our capability: [metric]
- Competitor average: [metric]
- Market leader: [metric]
### Opportunity/Threat
- What competitors are doing: [brief description]
- Timeline: [when competitive action happens]
- Impact if we act: [positive outcome]
- Impact if we don't act: [risk/loss]
### Recommendation
- [Action to take]
- [Competitive advantage gained]
- [Window of opportunity timeline]
For high-uncertainty situations, present multiple scenarios with probabilities and responses.
Scenario Structure:
## Market Expansion: Three Scenarios
### Optimistic Scenario (30% probability)
- Economy remains strong, enterprise budgets increase
- Expected outcome: $18M revenue, 35% growth
- Our response: Aggressive hiring, expand to 3 regions
### Base Case (50% probability)
- Moderate growth, stable budgets
- Expected outcome: $14M revenue, 20% growth
- Our response: Disciplined hiring, 2 regions
### Pessimistic Scenario (20% probability)
- Economic downturn, budget freezes
- Expected outcome: $9M revenue, flat growth
- Our response: Freeze hiring, focus on retention
### Recommendation
- Invest for Base Case (most likely)
- Maintain flexibility to scale up or down based on Q3 signals
- Decision point: End of Q3 to adjust Q4 strategy
Use When:
Benefits:
This skill includes templates, checklists, and tools in the resources/ folder:
The scripts/ folder includes Python utilities:
When presenting API strategy to executives:
Example: "Our monolithic API limits feature velocity (What). Each new feature requires testing the entire system, taking 3 weeks (Why). Microservices architecture enables independent deployment, reducing time-to-market from 3 weeks to 3 days (Next). This accelerates our product roadmap, supporting Growth priority."
When presenting security findings to board:
Example: "Penetration testing identified 12 vulnerabilities (What). 8 are low-risk, addressed in normal sprint cycle. 4 require immediate attention: [list]. These gaps exist because legacy authentication system lacks modern controls (Why - depersonalized). Recommendation: Implement zero-trust architecture by Q4, eliminating 95% of identified risks. Investment: $340K. Breach avoidance value: $8M-15M based on industry data (Next)."
When explaining feature flag strategy:
Example: "Feature flags enable us to deploy code to production without immediately exposing to all users (What). This reduces deployment risk 90% and enables A/B testing to optimize features before full launch (Why). Recommendation: Implement feature flag system in Q3. This accelerates our release cycle from monthly to weekly, supporting 4x faster product iteration (Next - connects to Growth priority)."
Content Check:
Design Check:
Appendix Check:
Stakeholder Check:
Step 1: IDENTIFY METRICS → Align with CEO priorities
↓
Step 2: DRAFT NARRATIVE → Use What/Why/Next structure
↓
Step 3: CREATE PRESENTATION → Apply visual design principles
↓
PRE-WIRE STAKEHOLDERS → Build support before formal meeting
↓
PRESENT WITH CONFIDENCE → Lead with insight, support with data
↓
DRIVE EXECUTIVE ACTION → Secure decision and commitment
Possible Causes:
Solutions:
Possible Causes:
Solutions:
Possible Causes:
Solutions:
Possible Causes:
Solutions:
Possible Causes:
Solutions:
Possible Causes:
Solutions:
Possible Causes:
Solutions:
Before presenting to executives, test your narrative with these exercises:
Summarize your entire presentation in 60 seconds as if you encountered the CEO in an elevator.
Components to hit:
If you can't do this clearly, your narrative isn't focused enough.
Read your slides aloud to someone outside your department (spouse, friend, colleague from different function).
Questions to ask:
Revise based on feedback.
For each key metric or recommendation in your presentation:
Ask:
If you can't answer these clearly, executives won't see the strategic relevance.
Have a colleague ask you 10 challenging questions about your presentation.
Test:
If you struggle, build more comprehensive appendix.
Show only your final slide to someone unfamiliar with your presentation.
Questions they should answer:
If they can't answer these, your ask isn't clear enough.
After each executive presentation:
Study great executive communications:
Iterate and improve - executive storytelling is a skill that improves with practice and feedback.
This skill is based on Gartner research "Use Data Storytelling to Engage the Executive Leadership Team" (G00818015, September 2024). The framework combines proven techniques from storytelling, visual design, and executive communication to help you transform data into compelling narratives that drive action and support.
Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.