AgentSkillsCN

Executive Storytelling

以数据驱动的方式构建叙事,有效管理利益相关者,助力高层决策的影响力提升。

SKILL.md
--- frontmatter
name: "Executive Storytelling"
description: "Data-driven narrative construction, stakeholder management, and influencing senior leadership decisions"

Skill: Executive Storytelling

Data-driven narrative construction, stakeholder management, and meeting efficiency for influencing senior leadership decisions.

Metadata

FieldValue
Skill IDexecutive-storytelling
Version1.1.0
CategoryCommunication
DifficultyAdvanced
PrerequisitesNone
Related Skillsslide-design, coaching-techniques, frustration-recognition

Merged: Includes content from stakeholder-management and meeting-efficiency skills.


Overview

Executives make decisions in minutes, not hours. This skill transforms complex data and analysis into compelling narratives that drive action. The goal isn't to present information—it's to influence outcomes.

Core Principle

Data tells. Stories sell.

Executives don't need more data—they need clarity, confidence, and a clear path forward.


Module 1: The Executive Mindset

What Executives Care About

PriorityQuestions They Ask
Impact"What's the bottom line?" "How big is this?"
Risk"What could go wrong?" "What's the downside?"
Time"When will we see results?" "How long until ROI?"
Resources"What do you need?" "What's the investment?"
Decision"What do you want me to do?" "What's the ask?"

The Executive Attention Span

TimeWhat They Absorb
30 secondsYour main point (or they tune out)
2 minutesKey supporting evidence
5 minutesNuances and Q&A prep
15+ minutesOnly if deeply engaged

Implication: Lead with the conclusion, not the journey.


Module 2: The SCQA Framework

Barbara Minto's Pyramid Principle adapted for executive communication:

Structure

ElementPurposeExample
SituationEstablish shared context"Our AI adoption is below industry benchmarks."
ComplicationIntroduce the tension"Without intervention, we risk falling further behind."
QuestionThe problem to solve"How do we accelerate AI adoption?"
AnswerYour recommendation"Implement AIRS-based readiness assessment before deployment."

Example: AIRS Research Pitch

Situation: "Organizations are investing heavily in AI tools, but adoption rates remain inconsistent."

Complication: "We don't know which employees will adopt and which will resist—leading to failed rollouts and wasted investment."

Question: "How can we predict and optimize AI adoption before deployment?"

Answer: "AIRS-16, a validated psychometric instrument, predicts adoption intention with high accuracy. Price Value (β=.505) is the strongest driver—meaning ROI clarity is more important than trust or ease of use."


Module 3: The Pyramid Principle

Top-Down Communication

code
        [Main Point]
       /     |      \
  [Support] [Support] [Support]
   /  \      |   \      /  \
[Data][Data][Data][Data][Data][Data]

Rule: Always state the conclusion first, then provide supporting evidence.

The "So What?" Test

For every claim, ask: "So what? Why does this matter to the executive?"

Weak: "AIRS has 16 items measuring 8 constructs." ✅ Strong: "AIRS predicts adoption in 3 minutes—faster than any alternative."

Weak: "Price Value had β=.505 in our analysis." ✅ Strong: "ROI clarity matters twice as much as any other factor—if you can't show the value, adoption will fail."

Grouping and Ordering

MECE Principle (Mutually Exclusive, Collectively Exhaustive):

  • Groups should not overlap
  • Groups should cover everything

Ordering options:

  1. Importance - Most impactful first
  2. Time - Chronological sequence
  3. Structure - Parts of a whole
  4. Priority - Ranked by urgency

Module 4: Data Storytelling

The Three Acts

ActPurposeContent
SetupContext and stakesWhy this matters now
ConflictThe problem/challengeWhat's broken, what's at risk
ResolutionYour solutionWhat to do, expected outcomes

Narrative Patterns

The Hero's Journey (for transformation stories):

  • Current state (ordinary world)
  • Challenge arises (call to adventure)
  • Struggle and learning (trials)
  • Success achieved (return with elixir)

The Discovery (for research findings):

  • What we believed
  • What we found
  • What this changes

The Comparison (for recommendations):

  • Option A: status quo
  • Option B: alternative
  • Why B wins

Data Visualization Principles

PrincipleApplication
One point per chartDon't overload visuals
Title is the takeaway"Revenue grew 40%" not "Revenue 2020-2025"
Remove clutterNo 3D, no gridlines, minimal legend
Highlight the insightColor/size to draw eye to key data

Numbers That Stick

TechniqueExample
Anchoring"That's 50% more than last year"
Humanizing"Each hour saved equals 2,000 employees × $50/hr = $100K/year"
Comparison"The cost of a coffee per employee per day"
Rounding"$2.3M" not "$2,347,891.23"

Module 5: The Ask

Clarity of Request

Every executive presentation needs a clear ask:

Ask TypeExample
Decision"Approve the $500K investment"
Input"Share your concerns so we can address them"
Resource"Allocate 3 FTEs for 6 months"
Alignment"Confirm this direction before we proceed"
Escalation"Remove the blocker with [stakeholder]"

The One-Page Summary

SectionContentLines
HeadlineMain recommendation1
ContextWhy now, what's at stake2-3
Key findings3 bullets maximum3-4
RecommendationSpecific action2-3
AskWhat you need from them1-2
Next stepsImmediate actions2-3

Module 6: Objection Handling

Anticipate and Preempt

Objection TypePreemption Strategy
CostLead with ROI, payback period
RiskAcknowledge, present mitigations
TimingShow urgency cost of delay
ComplexitySimplify, offer phased approach
SkepticismCite precedent, pilot results

The Acknowledge-Bridge-Response Pattern

  1. Acknowledge: "That's a fair concern..."
  2. Bridge: "What we've found is..."
  3. Response: "...which is why we recommend..."

Backup Slides

Keep supporting detail in backup slides:

  • Detailed methodology
  • Full data tables
  • Alternative scenarios
  • Risk registers
  • Implementation timelines

Templates

30-Second Elevator Pitch

code
We need to [action] because [problem].
Our approach is [solution].
This will deliver [outcome] within [timeframe].
I need [ask] to proceed.

5-Minute Executive Brief

code
1. [0:30] The headline and ask
2. [1:00] Context and stakes
3. [2:00] Evidence (3 key points)
4. [1:00] Recommendation details
5. [0:30] Specific ask and next steps

Slide Structure (McKinsey Style)

code
┌─────────────────────────────────────────┐
│ HEADLINE: The main takeaway as a sentence│
├─────────────────────────────────────────┤
│                                         │
│         [Visual Evidence]               │
│                                         │
│         Chart, diagram, or key data     │
│                                         │
├─────────────────────────────────────────┤
│ Source: [data source]                   │
└─────────────────────────────────────────┘

Quick Reference

Storytelling Checklist

  • Lead with conclusion (not buildup)
  • Clear "so what?" for every point
  • Specific, measurable claims
  • One ask, clearly stated
  • Anticipated objections addressed
  • Backup detail available
  • Under time limit

Common Mistakes

MistakeFix
Burying the leadStart with recommendation
Too much detailRuthlessly cut
No clear askSpecify the decision needed
Data dumpSelect 3 most compelling points
JargonPlain language, define terms
Missing "so what?"Connect data to business impact

Activation Patterns

TriggerResponse
"executive presentation", "senior leadership"Full skill activation
"elevator pitch", "30 seconds"30-Second template
"SCQA", "pyramid principle"Module 2-3 frameworks
"objection handling", "pushback"Module 6
"data storytelling", "present findings"Module 4
"stakeholder", "influence", "politics"Stakeholder Management
"meeting", "agenda", "facilitation"Meeting Efficiency

Stakeholder Management

The Power-Interest Grid

Low InterestHigh Interest
High PowerKeep SatisfiedManage Closely
Low PowerMonitorKeep Informed

Stakeholder Profile Template

FieldPurpose
Name/RoleWho they are
Power LevelDecision authority
Current PositionSupport, oppose, neutral
Desired PositionWhere you need them
Key ConcernsWhat they worry about
MotivatorsWhat they care about
Communication PreferenceHow to reach them
StrategyHow to move them

Influence Without Authority

StrategyWhen to UseTactics
ReciprocityBuilding long-term alliesDo favors first, bank goodwill
CoalitionFacing resistanceBuild supporter network
EvidenceSkeptical stakeholdersData, pilots, proof points
AuthorityBorrowed credibilityExecutive sponsor, expert endorsement
Social proofRisk-averse stakeholdersIndustry examples, peer adoption

The Stakeholder Ladder

Move stakeholders progressively:

code
Opponent → Skeptic → Neutral → Supporter → Champion

Resistance Patterns

Resistance TypeRoot CauseCounter
Fear of unknownUncertaintyEducation, pilots
Loss of powerTerritory threatInvolvement, shared credit
Resource concernBudget/timeClear scope, trade-offs
Not invented herePrideCo-creation, acknowledgment

Stakeholder Communication Frequency

Stakeholder TypeFrequencyMedium
Executive sponsorWeekly1:1, brief updates
Manage closely2x/weekMeetings, direct calls
Keep satisfiedBi-weeklyEmail summaries
Keep informedMonthlyNewsletters, dashboards

RACI Matrix

RoleDefinition
ResponsibleDoes the work
AccountableOwns the decision (one per task)
ConsultedInput before decision
InformedTold after decision

Meeting Efficiency

Meeting or Not?

NeedMeeting Required?Alternative
Decide somethingMaybeAsync decision doc if simple
Share informationRarelyEmail, video, document
BrainstormOftenAsync + sync hybrid
Build relationshipsYesNo substitute for presence
Status updatesNoDashboards, async standup

Meeting Types

TypePurposeDurationRequired Elements
DecisionMake a call30-60 minOptions, criteria, decider
CreativeGenerate ideas60-90 minPrompt, diverge/converge
TacticalCoordinate action15-30 minBlockers, handoffs
StrategicSet direction60-120 minContext, options, trade-offs
1:1Develop people30-60 minTheir agenda first

Agenda Template

markdown
## Meeting: [Purpose Statement]
**Duration**: [X min] | **Attendees**: [Required], [Optional]

### Pre-Work
- [ ] Review [document]

### Agenda
1. [Topic 1] - [Owner] - [Time] min
2. [Topic 2] - [Owner] - [Time] min

### Decisions Made
1. 

### Action Items
| Action | Owner | Due |
|--------|-------|-----|

Facilitation Techniques

ProblemIntervention
One person dominates"Let's hear from others"
Nobody speaksDirect: "Sarah, your thoughts?"
Tangent emerges"Interesting—let's park that"
Going in circles"Let me summarize where we are"
Conflict emerges"What do we actually agree on?"

Decision-Making Methods

MethodWhen to Use
ConsentRoutine decisions ("Any objections?")
ConsensusHigh-stakes, need buy-in
ConsultativeNeed input, one decider
DelegationTrust exists

Async Alternatives

Meeting TypeAsync Alternative
Daily standupSlack standup post
Weekly statusDashboard + async digest
All-handsRecorded video + AMA thread
Document reviewComments in doc

Meeting Anti-Patterns

Anti-PatternFix
No agendaRequire agenda for all meetings
Too many attendees7 ± 2 rule
Status meetingsMake async
No decisionsClear decision process
No notesAssign note-taker

Skill created: 2026-02-10 | Category: Communication | Status: Active Merged: stakeholder-management, meeting-efficiency


Synapses

  • [.github/skills/slide-design/SKILL.md] (High, Uses, Bidirectional) - "Executive presentation design"
  • [.github/skills/coaching-techniques/SKILL.md] (Medium, Complements, Bidirectional) - "Leadership communication overlap"
  • [.github/skills/project-management/SKILL.md] (Medium, Integrates, Forward) - "Stakeholder communication in projects"