cadence-voice-presenting-data

name	cadence-voice:presenting-data
description	Use when presenting data findings as a narrative or building a data-driven argument
license	MIT
metadata	{"author":"cameronsjo","version":"1.0"}

Data Storytelling

Transform data and metrics into compelling narratives that drive executive action and support using proven frameworks from Gartner research.

Overview

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.

When to Use This Skill

Trigger this skill when you need to:

• Create executive presentations for board meetings, ELT updates, or C-suite reviews
• Draft board memos or stakeholder communications requiring data-driven narratives
• Prepare quarterly business reviews or department performance updates
• Build business cases for investment decisions or strategic initiatives
• Design executive dashboards that tell stories, not just display metrics
• Transform technical analysis into executive-friendly insights
• Respond to executive requests for data explanations or recommendations
• Handle crisis communications requiring data-backed action plans
• Present project results to senior leadership or steering committees
• Justify resource allocation or budget requests with data

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

Core Principles

The Strategic Context

Why Traditional Data Presentations Fail:

1. Jargon overload: Using department-specific terminology (MAU, CSAT, TTM, MQL) that ELT members outside your domain don't understand
2. Operational focus: Presenting tactical metrics instead of strategic implications
3. Missing the "so what": Showing what happened without explaining why it matters
4. No clear action: Providing data without recommendations or next steps
5. Poor visual design: Overwhelming slides that exceed adult attention spans (67 seconds)
6. Misaligned priorities: Focusing on departmental wins instead of CEO/ELT strategic priorities

The Executive Context:

• CEOs spend 72% of their time in meetings - your presentation competes for limited attention
• High-performing ELTs use data for 84% of decisions - they want insights, not raw data
• Executives think in strategic terms: growth, technology, workforce, financial performance
• They need to make decisions quickly with confidence in the supporting data

The Three-Step Framework

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):

• Growth (59%): Revenue expansion, market share, customer acquisition, new markets
• Technology (29%): Digital transformation, AI/ML adoption, modernization, innovation
• Workforce (25%): Talent retention, skills development, culture, productivity
• Financial (22%): Cost optimization, profitability, ROI, operational efficiency

Strategic Alignment Questions:

• Who will be affected by this data? Which executives have a stake?
• Who do you need support from to act on these insights?
• What strategic initiative does this metric support or threaten?
• How does this connect to quarterly or annual goals?

Language Mirroring:

• Use the exact acronyms and terminology your CEO and peers use
• If the CEO talks about "customer lifetime value," don't say "LTV optimization"
• If the CFO discusses "operating margin," mirror that language exactly
• Study recent ELT communications to understand their vocabulary

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):

• State the current state clearly and concisely
• Are we on track for targets? Ahead? Behind?
• Align the metric directly with CEO/ELT priorities identified in Step 1
• Use concrete numbers, not vague descriptions
• Set the stage for the story you're about to tell

WHY (Catalyst):

• Explain why you achieved or failed to achieve results
• Be data-driven and specific - no fluffy excuses
• Depersonalize failures: Focus on the problem, not "we" or "our team"
  • ❌ "We struggled to deliver features on time"
  • ✅ "Feature delivery was impacted by increased technical debt requiring 40% more QA cycles"
• Show causal relationships with supporting data
• Be honest about failures - executives respect transparency

NEXT (Break Into Two):

• State what should be done next with clear recommendations
• Predict what the outcomes will be if action is taken
• Provide specific timeframes and success metrics
• If unclear, provide 2-3 options with trade-offs for executive decision-making
• Advanced: Embed emotional tone to influence response:
  • Surprised: "Unexpectedly, customer churn decreased 40% after price increase"
  • Inspired: "This opens a path to dominate the SMB segment within 18 months"
  • Reassured: "Despite Q2 challenges, we remain on track for annual targets"

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:

1. One Slide, One Idea: Each slide should convey a single concept or insight
2. 3-5 Bullets Maximum: Adults have a 67-second attention span - respect it
3. Simple Visuals: Use charts, graphs, and relevant images sparingly
4. Clear Hierarchy: Title → Key insight → Supporting data → Recommendation
5. Consistent Formatting: Match or improve upon CEO/peer presentation style

Visual Design Checklist:

• Does each slide have a clear title that states the insight?
• Are there 3-5 bullets or less per slide?
• Do visuals support the narrative rather than decorate?
• Is text large enough to read from the back of the room?
• Have you removed unnecessary logos, borders, and decoration?
• Does the slide tell a story without you speaking?
• Would this slide pass the "glance test" (understand in 5 seconds)?

Effective Chart Selection:

• Trends over time: Line charts
• Comparisons: Bar charts (horizontal for long labels)
• Parts of a whole: Pie charts (only if 2-4 segments)
• Relationships: Scatter plots with trend lines
• Geographic data: Heat maps or choropleth maps
• Hierarchies: Tree maps or sunburst charts

Anti-Patterns to Avoid:

• ❌ Dense paragraphs of text
• ❌ More than 5 bullet points
• ❌ Multiple ideas on one slide
• ❌ Complex 3D charts or excessive decoration
• ❌ Tiny fonts or cluttered visuals
• ❌ Data without context or comparison
• ❌ Missing units or timeframes on metrics

Creating Analogies for Difficult Topics:

Complex technical concepts need translation for executive audiences.

Examples:

• Technical debt → "Like a credit card: borrowing speed today means paying interest tomorrow"
• API rate limits → "Like a highway with lanes: too many cars (requests) cause congestion"
• Machine learning model → "Like a spam filter: it learns patterns from examples"
• Kubernetes scaling → "Like hiring seasonal workers: add capacity when needed, reduce when demand drops"

Formula: [Complex concept] is like [familiar thing] because [key similarity]

Emotional Resonance Check:

Before finalizing, ask:

• Does this content incite a visceral emotion? (surprise, inspiration, concern, reassurance)
• Would this make an executive lean forward or check their phone?
• Does the narrative build to a compelling call to action?
• Have you connected data to human impact? (customers, employees, market position)

Framework Application Guide

Template 1: What/Why/Next Narrative Structure

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]

Template 2: Executive Presentation Outline

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]

Template 3: Priority Alignment Framework

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]

Use Case Examples

Example 1: Sales Enablement - Premium Leads Program

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:

• 4-hour response time vs. 48-hour baseline
• 3x higher engagement (58% vs. 19%)
• 35% increase in qualified opportunities
• $12M pipeline contribution

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:

1. Title: "Premium Leads Drive 35% Opportunity Growth"
2. What: Pipeline chart showing $12M contribution vs. target
3. Why: Side-by-side comparison of premium vs. standard lead conversion
4. Next: Investment/ROI table with recommendation
5. Timeline: 6-week implementation plan

Example 2: Technology Innovation - Design Thinking Labs

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:

• 47 employee ideas submitted
• 3 prototypes in pilot (6% conversion rate)
• $2.3M projected savings
• 2-week sprint cycle vs. 6-8 month traditional timeline

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:

1. Title: "Design Labs Unlock $2.3M in Employee-Driven Innovation"
2. What: Funnel chart (47 ideas → 3 pilots → projected savings)
3. Why: Timeline comparison (traditional vs. lab process)
4. Next: Expansion map with investment and ROI
5. Risk Mitigation: Executive sponsorship model and commitment asks

Example 3: Crisis Communication - Security Incident

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:

• 47-minute detection and containment
• 83% faster than industry average
• 0 customer records compromised
• 23% of accounts using weak passwords

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:

1. Title: "Security Incident Contained in 47 Minutes - Zero Customer Impact"
2. What: Timeline infographic of detection → containment
3. Why: Attack vector diagram + weak password vulnerability data
4. Next: MFA recommendation with adoption curve projection
5. Implementation: Phased rollout plan with customer communication strategy

Example 4: Workforce - Talent Retention Program

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:

• Individualized career development plans (100% of engineers)
• $3K annual learning budget per engineer
• Internal mobility program (lateral moves without manager approval)

The combination increased internal promotion rate from 8% to 22% and created clear growth paths that competing offers couldn't match."

Data Points:

• 24% → 11% turnover reduction
• $4.8M cost avoidance
• 67% cited career growth in exit interviews
• 8% → 22% internal promotion rate

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:

1. Title: "Retention Program Cuts Engineering Turnover in Half"
2. What: Turnover trend line + cost avoidance calculation
3. Why: Exit interview insights + program components
4. Next: Expansion plan with investment and ROI
5. Risk Mitigation: Market comparison showing our competitive positioning

References

Each reference expands on the framework above. Pull in the one that matches what you are doing:

• Advanced Techniques: Read when you need to influence the room beyond a clean narrative (emotional tone, pre-wiring stakeholders, the appendix strategy, the "Decision Required" framework, the "So What" cascade, and competitive or scenario positioning).
• Depersonalization Strategies: Read when presenting a failure, missed target, or setback and the narrative needs to stay analytical instead of defensive.
• Visual Design Best Practices: Read when building the slides themselves (layout, chart selection, color, typography, deck structure).
• Pitfalls and Troubleshooting: Read when a draft feels off or a presentation fell flat (eight authoring pitfalls with fixes, plus live-room symptoms like disengagement, data pushback, or no clear decision).
• Testing and Best Practices: Read before presenting (rehearsal exercises, the ten commandments, the pre-flight checklist) and after (the debrief loop).