Storytelling with Data (SWD) Skill
Apply the 6-lesson SWD framework from Cole Nussbaumer Knaflic for visual and design decisions, combined with narrative storytelling frameworks (Dykes, Duarte, Miller, Dicks, Cron, Heath) for structuring compelling stories that drive action.
Format-agnostic by design: This skill covers what to communicate and how to design it. Pair it with format-specific skills that handle output mechanics (e.g. pptx skill for slide decks, a web framework for dashboards).
The SWD 6-Lesson Framework
Every data communication task should be evaluated against these 6 lessons, applied in order:
Lesson 1: Understand the Context
Before touching any tool, answer three questions:
- WHO is your audience? What do they care about? What's their relationship to you? What will motivate them?
- WHAT do you need them to know or do? Define the single action or takeaway.
- HOW will you communicate? Live presentation? Email? Dashboard? This changes everything about design.
Key techniques:
- The 3-Minute Story: Can you explain your entire message in 3 minutes? If not, you haven't distilled it enough.
- The Big Idea: One sentence that articulates your unique point of view, what's at stake, and what you want the audience to do. Format: [situation] + [complication] → [recommended action].
- Storyboard first: Sketch your flow on sticky notes or paper before opening any tool. Rearrange freely.
- Exploratory ≠ Explanatory: The audience sees only the explanatory output - the curated insight, not the full analysis journey. Never dump exploratory analysis on your audience.
When reviewing existing work, ask:
- Is there a clear "so what?" on every chart, panel, or section?
- Could the audience state the key message after a 3-second glance?
- Is there a specific call to action?
Lesson 2: Choose an Appropriate Visual Display
Match the visual to the message. You can handle the vast majority of business communications with just a few chart types.
Read references/chart-selection.md for the detailed chart selection guide.
Quick decision framework:
- Comparison across categories → Horizontal bar chart (default workhorse)
- Trend over time → Line chart (continuous) or vertical bar chart (discrete periods)
- Part-to-whole → Stacked bar or waterfall (NOT pie charts)
- Two data points comparison → Slopegraph
- Single important number → Simple text (the number itself, large, with context)
- Detailed lookup → Table or heatmap
Charts to AVOID:
- Pie and doughnut charts (hard to compare areas/angles accurately)
- 3D anything (adds clutter, distorts data, makes reading values harder)
- Dual y-axes (confuse the audience about scale relationships)
- Spaghetti graphs (too many overlapping lines - filter or use small multiples instead)
Lesson 3: Eliminate Clutter
Clutter is any visual element that takes up space without adding understanding. Every element increases cognitive load - the mental effort to process information.
Identify and remove:
- Chart borders and unnecessary outlines
- Gridlines (reduce to light or remove entirely)
- Data markers on every point (only mark what matters)
- Redundant labels (if the axis says it, the data label doesn't need to)
- Bold/italic/colour on everything (when everything is emphasised, nothing is)
- Legends (can you label directly instead?)
- Rotated text (hard to read - restructure the chart instead)
- Decorative elements that don't encode data
Apply Gestalt Principles to structure what remains:
- Proximity: Group related items close together; separate unrelated ones
- Similarity: Use consistent colours/shapes for items in the same category
- Enclosure: Subtle backgrounds can group related content
- Closure: Remove unnecessary borders - the eye fills in gaps
- Continuity: Align elements so the eye flows naturally
- Connection: Lines connecting points imply sequence or relationship
Decluttering process (step by step):
- Remove chart borders
- Remove or lighten gridlines
- Remove data markers (unless specific points need emphasis)
- Clean up axis labels (round numbers, remove unnecessary precision)
- Label data directly (eliminate legends where possible)
- Use consistent, strategic colour
Lesson 4: Focus Your Audience's Attention
Use preattentive attributes - visual properties the brain processes before conscious thought - to guide the eye to what matters:
- Colour: The most powerful tool. Use a single accent colour to highlight the key data; push everything else to grey. Never use colour decoratively.
- Size: Larger elements draw attention first. Make the key number or data point bigger.
- Position: Items at the top-left get seen first (in left-to-right reading cultures). Place the most important information there.
- Bold/weight: Use sparingly on text to create hierarchy. Bold the key phrase, not the whole paragraph.
The Grey + One Colour rule: Default everything to grey, then use ONE strategic accent colour to highlight the story. This is the single most impactful SWD technique.
Read references/colour-and-emphasis.md for the emphasis hierarchy and grey-plus-accent strategy. This skill owns the message and emphasis strategy; for the visual rendering and colour system (validated palettes, mark specs) defer to the dataviz skill.
Memory matters:
- Iconic memory (~0.5 seconds): Preattentive attributes are processed here - that's why colour and size pop instantly
- Short-term memory (~4 items): Don't overload a single view with too many competing elements
- Long-term memory: Connect to what the audience already knows - use familiar chart types and conventions
Lesson 5: Think Like a Designer
Design serves the message. Apply these principles:
- Form follows function: Every element earns its place by serving comprehension
- Affordances: Make interactive elements look clickable; make important text look important
- Accessibility: Would this work in greyscale? For colour-blind audiences? Without a narrator explaining it?
- Aesthetics build trust: Clean, well-aligned visuals signal competence and credibility
Practical design rules:
- Use consistent alignment (create an invisible grid)
- Left-align text (easier to read than centred for body content)
- Use white space generously - it's not wasted space, it's breathing room
- Limit fonts to 1-2 families; use size and weight for hierarchy
- Action titles > descriptive titles: "Revenue grew 23% in Q3" beats "Q3 Revenue"
- Every chart, section, or panel should have a clear, declarative title that states the "so what"
- Add context with text annotations directly on the visualisation
Lesson 6: Tell a Story
Without narrative, data visualisations are just pretty pictures. Multiple frameworks exist for structuring compelling stories. Choose based on your scenario.
Read references/narrative-frameworks.md for detailed framework guidance and references/hooks-and-moments.md for hook and aha moment techniques.
Framework Selection
| Scenario |
Primary Framework |
Supporting |
| Data insight presentation |
Dykes Data Storytelling Arc |
Heath SUCCESs |
| Persuasive keynote or pitch |
Duarte Sparkline |
Miller SB7, Dicks |
| Product/brand positioning |
Miller StoryBrand SB7 |
Duarte, Heath |
| Conference talk / personal story |
Dicks Five-Second Moment |
Duarte, Cron |
| Message stickiness review |
Heath SUCCESs checklist |
|
Storytelling techniques (applicable across all frameworks):
- Horizontal logic: Read just the section/slide titles in sequence. They should tell a complete story on their own.
- Vertical logic: Each individual section, panel, or slide should make sense on its own with title + content.
- Repetition: Repeat your key message at least 3 times in different ways.
- Progressive reveal: Don't show everything at once. Build up piece by piece.
- Match the medium: Live presentations = sparse visuals (you are the narrator). Read-alone formats need more text and annotation.
- Hooks within 60 seconds: Use anomaly, stakes, contrast, question, vulnerability, or in-medias-res hooks (see
references/hooks-and-moments.md).
- Use "but" and "therefore" to connect story elements: "and" kills momentum (Dicks).
Applying SWD: Task-Specific Workflows
Creating New Data Communications
This workflow applies regardless of output format (slide deck, dashboard, infographic, static site, report).
- Context interview - Ask the user: Who's the audience? What's the one thing they should take away? How will this be delivered?
- Choose narrative framework - Data insight: Dykes Arc. Persuasive pitch: Duarte Sparkline. Product positioning: Miller SB7. (See
references/narrative-frameworks.md)
- Storyboard - Draft section/panel titles as a narrative arc. For Dykes: Setting > Hook > Rising Points > Aha Moment > Solution. For Duarte: What Is > What Could Be (alternating) > New Bliss.
- Craft the Hook - Must land within 60 seconds. Choose from: anomaly, stakes, contrast, question, vulnerability, or in-medias-res. (See
references/hooks-and-moments.md)
- Chart selection - For each data point, pick the simplest effective chart (see
references/chart-selection.md)
- Build - Apply Lessons 3-5 while creating each section or view
- Verify the Aha Moment - Does it surprise? Shift understanding? Have an explicit "so what"? Is it at the climax, not the beginning?
- Review - Check horizontal logic (titles alone tell the story), vertical logic (each unit stands alone), and run the SUCCESs checklist
Format-Specific Considerations
| Format |
Key adaptations |
| Slide deck |
Sparse visuals (presenter narrates), one idea per slide, progressive build/reveal |
| Dashboard |
Self-explanatory (no presenter), overview panels first with drill-down detail, interactive filters to reduce clutter |
| Infographic |
Single linear flow top-to-bottom, strong visual hierarchy to guide the eye, must stand alone without explanation |
| Static site / playground |
Progressive disclosure (summary up top, detail below or on click), responsive layout considerations, can use animation/interaction for reveal |
| Written report |
More annotation and explanation than visual formats, charts support the narrative text rather than replace it |
Creating a Persuasive Pitch or Keynote
- Define The Big Idea (Duarte): One sentence = situation + complication leading to recommended action
- Map the audience as hero (Miller SB7): What do they want? What problem do they face (external, internal, philosophical)? How are you the guide?
- Structure with Sparkline contrast: Alternate "what is" vs "what could be" throughout
- Plant a S.T.A.R. Moment (Duarte): Something They'll Always Remember: a dramatic, tangible demonstration of the idea
- Craft sound bites: Small, repeatable phrases for headlines and sharing
- End with New Bliss: Paint the picture of the world with the idea adopted + clear call to action
- Apply SWD Lessons 2-5 for any data slides within the pitch
Structuring a Personal or Conference Story
- Find the five-second moment (Dicks): What single moment of transformation is this story about?
- Start at the end: Know where you're going, then build backward
- Begin in the opposite: Open in the emotional/situational opposite of where the story ends
- Apply the Dinner Test: Would you tell it this way to a friend over dinner?
- Load engagement devices: Stakes (hopes/fears before moving forward), Surprise (build it, don't spoil it), Suspense (make them wonder what's next)
- Slow down at the moment: Use the Hourglass (Dicks): add detail and a beat right before the climax
Positioning a Product or Brand
- Complete the SB7 BrandScript (Miller): Character > Problem > Guide > Plan > CTA > Failure > Success
- Define the villain: Must be a root source (not a feeling), relatable, singular, and real
- Articulate three problem levels: External (tangible), Internal (emotional), Philosophical (why it's wrong)
- Establish Guide credentials: Empathy ("I understand") + Authority ("I've solved this before")
- Show the transformation: Clear before/after: who does the customer become?
- Run SUCCESs check (Heath): Is the message Simple, Unexpected, Concrete, Credible, Emotional, Story-driven?
Reviewing / Critiquing Existing Work
Run through the SWD Review Checklist in references/review-checklist.md. For each chart, panel, section, or slide, evaluate against all 6 lessons and provide specific, actionable feedback. Additionally evaluate the narrative structure:
- Does the presentation have a clear Hook within the first 60 seconds?
- Is there a genuine Aha Moment (surprise + shift + "so what")?
- Is the insight at the climax, not the beginning?
- Does the narrative follow a coherent arc (not just a collection of charts)?
- Would it pass the Dinner Test: is it told the way a human would tell it?
- Does the closing provide clear, actionable next steps?
Chart / Visualisation Makeover
- Identify the core message (what should the audience think/do?)
- Choose a better chart type if needed (Lesson 2)
- Strip all clutter (Lesson 3)
- Apply grey + accent colour strategy (Lesson 4)
- Add a declarative action title (Lesson 5)
- Add text annotations to guide interpretation (Lesson 5)
- Show before/after to demonstrate the improvement
Reference Files
| File |
When to read |
references/narrative-frameworks.md |
When structuring any narrative: data stories, pitches, keynotes, brand positioning. Contains Dykes (Data Storytelling Arc), Duarte (Sparkline), Miller (SB7), Dicks (Five-Second Moment), Cron (Brain Science), Heath (SUCCESs). Framework selection table is in Lesson 6. |
references/hooks-and-moments.md |
When crafting a hook or aha moment. Contains 6 hook types, the Insight Test, placement principles, and engagement devices. |
references/chart-selection.md |
When choosing a chart type or advising on visual selection |
references/review-checklist.md |
When reviewing or critiquing existing data communications |
references/colour-and-emphasis.md |
When making colour choices or applying emphasis strategies |
1---2name: storytelling-with-data3description: Apply storytelling principles to create, review, and improve data visualisations and data-driven communications. Use when the message or story of a data communication (chart, dashboard, infographic, data-driven deck or report) needs structuring or review, or when structuring narrative arcs, hooks, or aha moments in data-driven communications.4---5
6# Storytelling with Data (SWD) Skill
7
8Apply the 6-lesson SWD framework from Cole Nussbaumer Knaflic for visual and design decisions, combined with narrative storytelling frameworks (Dykes, Duarte, Miller, Dicks, Cron, Heath) for structuring compelling stories that drive action.
9
10> **Format-agnostic by design**: This skill covers _what_ to communicate and _how_ to design it. Pair it with format-specific skills that handle output mechanics (e.g. pptx skill for slide decks, a web framework for dashboards).
11
12---
13
14## The SWD 6-Lesson Framework
15
16Every data communication task should be evaluated against these 6 lessons, applied in order:
17
18### Lesson 1: Understand the Context
19
20Before touching any tool, answer three questions:
21
221. **WHO** is your audience? What do they care about? What's their relationship to you? What will motivate them?
232. **WHAT** do you need them to know or do? Define the single action or takeaway.
243. **HOW** will you communicate? Live presentation? Email? Dashboard? This changes everything about design.
25
26**Key techniques:**
27
28- **The 3-Minute Story**: Can you explain your entire message in 3 minutes? If not, you haven't distilled it enough.
29- **The Big Idea**: One sentence that articulates your unique point of view, what's at stake, and what you want the audience to do. Format: [situation] + [complication] → [recommended action].
30- **Storyboard first**: Sketch your flow on sticky notes or paper before opening any tool. Rearrange freely.
31- **Exploratory ≠ Explanatory**: The audience sees only the _explanatory_ output - the curated insight, not the full analysis journey. Never dump exploratory analysis on your audience.
32
33**When reviewing existing work, ask:**
34
35- Is there a clear "so what?" on every chart, panel, or section?
36- Could the audience state the key message after a 3-second glance?
37- Is there a specific call to action?
38
39### Lesson 2: Choose an Appropriate Visual Display
40
41Match the visual to the message. You can handle the vast majority of business communications with just a few chart types.
42
43**Read `references/chart-selection.md` for the detailed chart selection guide.**
44
45Quick decision framework:
46
47- **Comparison across categories** → Horizontal bar chart (default workhorse)
48- **Trend over time** → Line chart (continuous) or vertical bar chart (discrete periods)
49- **Part-to-whole** → Stacked bar or waterfall (NOT pie charts)
50- **Two data points comparison** → Slopegraph
51- **Single important number** → Simple text (the number itself, large, with context)
52- **Detailed lookup** → Table or heatmap
53
54**Charts to AVOID:**
55
56- Pie and doughnut charts (hard to compare areas/angles accurately)
57- 3D anything (adds clutter, distorts data, makes reading values harder)
58- Dual y-axes (confuse the audience about scale relationships)
59- Spaghetti graphs (too many overlapping lines - filter or use small multiples instead)
60
61### Lesson 3: Eliminate Clutter
62
63Clutter is any visual element that takes up space without adding understanding. Every element increases **cognitive load** - the mental effort to process information.
64
65**Identify and remove:**
66
67- Chart borders and unnecessary outlines
68- Gridlines (reduce to light or remove entirely)
69- Data markers on every point (only mark what matters)
70- Redundant labels (if the axis says it, the data label doesn't need to)
71- Bold/italic/colour on everything (when everything is emphasised, nothing is)
72- Legends (can you label directly instead?)
73- Rotated text (hard to read - restructure the chart instead)
74- Decorative elements that don't encode data
75
76**Apply Gestalt Principles to structure what remains:**
77
78- **Proximity**: Group related items close together; separate unrelated ones
79- **Similarity**: Use consistent colours/shapes for items in the same category
80- **Enclosure**: Subtle backgrounds can group related content
81- **Closure**: Remove unnecessary borders - the eye fills in gaps
82- **Continuity**: Align elements so the eye flows naturally
83- **Connection**: Lines connecting points imply sequence or relationship
84
85**Decluttering process (step by step):**
86
871. Remove chart borders
882. Remove or lighten gridlines
893. Remove data markers (unless specific points need emphasis)
904. Clean up axis labels (round numbers, remove unnecessary precision)
915. Label data directly (eliminate legends where possible)
926. Use consistent, strategic colour
93
94### Lesson 4: Focus Your Audience's Attention
95
96Use **preattentive attributes** - visual properties the brain processes before conscious thought - to guide the eye to what matters:
97
98- **Colour**: The most powerful tool. Use a single accent colour to highlight the key data; push everything else to grey. Never use colour decoratively.
99- **Size**: Larger elements draw attention first. Make the key number or data point bigger.
100- **Position**: Items at the top-left get seen first (in left-to-right reading cultures). Place the most important information there.
101- **Bold/weight**: Use sparingly on text to create hierarchy. Bold the key phrase, not the whole paragraph.
102
103**The Grey + One Colour rule**: Default everything to grey, then use ONE strategic accent colour to highlight the story. This is the single most impactful SWD technique.
104
105**Read `references/colour-and-emphasis.md` for the emphasis hierarchy and grey-plus-accent strategy.** This skill owns the message and emphasis strategy; for the visual rendering and colour system (validated palettes, mark specs) defer to the dataviz skill.
106
107**Memory matters:**
108
109- **Iconic memory** (~0.5 seconds): Preattentive attributes are processed here - that's why colour and size pop instantly
110- **Short-term memory** (~4 items): Don't overload a single view with too many competing elements
111- **Long-term memory**: Connect to what the audience already knows - use familiar chart types and conventions
112
113### Lesson 5: Think Like a Designer
114
115Design serves the message. Apply these principles:
116
117- **Form follows function**: Every element earns its place by serving comprehension
118- **Affordances**: Make interactive elements look clickable; make important text look important
119- **Accessibility**: Would this work in greyscale? For colour-blind audiences? Without a narrator explaining it?
120- **Aesthetics build trust**: Clean, well-aligned visuals signal competence and credibility
121
122**Practical design rules:**
123
124- Use consistent alignment (create an invisible grid)
125- Left-align text (easier to read than centred for body content)
126- Use white space generously - it's not wasted space, it's breathing room
127- Limit fonts to 1-2 families; use size and weight for hierarchy
128- Action titles > descriptive titles: "Revenue grew 23% in Q3" beats "Q3 Revenue"
129- Every chart, section, or panel should have a clear, declarative title that states the "so what"
130- Add context with text annotations directly on the visualisation
131
132### Lesson 6: Tell a Story
133
134Without narrative, data visualisations are just pretty pictures. Multiple frameworks exist for structuring compelling stories. Choose based on your scenario.
135
136**Read `references/narrative-frameworks.md` for detailed framework guidance** and **`references/hooks-and-moments.md` for hook and aha moment techniques**.
137
138#### Framework Selection
139
140| Scenario | Primary Framework | Supporting |
141|---|---|---|
142| Data insight presentation | Dykes Data Storytelling Arc | Heath SUCCESs |
143| Persuasive keynote or pitch | Duarte Sparkline | Miller SB7, Dicks |
144| Product/brand positioning | Miller StoryBrand SB7 | Duarte, Heath |
145| Conference talk / personal story | Dicks Five-Second Moment | Duarte, Cron |
146| Message stickiness review | Heath SUCCESs checklist | |
147
148#### Storytelling techniques (applicable across all frameworks):
149
150- **Horizontal logic**: Read just the section/slide titles in sequence. They should tell a complete story on their own.
151- **Vertical logic**: Each individual section, panel, or slide should make sense on its own with title + content.
152- **Repetition**: Repeat your key message at least 3 times in different ways.
153- **Progressive reveal**: Don't show everything at once. Build up piece by piece.
154- **Match the medium**: Live presentations = sparse visuals (you are the narrator). Read-alone formats need more text and annotation.
155- **Hooks within 60 seconds**: Use anomaly, stakes, contrast, question, vulnerability, or in-medias-res hooks (see `references/hooks-and-moments.md`).
156- Use **"but" and "therefore"** to connect story elements: "and" kills momentum (Dicks).
157
158---
159
160## Applying SWD: Task-Specific Workflows
161
162### Creating New Data Communications
163
164This workflow applies regardless of output format (slide deck, dashboard, infographic, static site, report).
165
1661. **Context interview** - Ask the user: Who's the audience? What's the one thing they should take away? How will this be delivered?
1672. **Choose narrative framework** - Data insight: Dykes Arc. Persuasive pitch: Duarte Sparkline. Product positioning: Miller SB7. (See `references/narrative-frameworks.md`)
1683. **Storyboard** - Draft section/panel titles as a narrative arc. For Dykes: Setting > Hook > Rising Points > Aha Moment > Solution. For Duarte: What Is > What Could Be (alternating) > New Bliss.
1694. **Craft the Hook** - Must land within 60 seconds. Choose from: anomaly, stakes, contrast, question, vulnerability, or in-medias-res. (See `references/hooks-and-moments.md`)
1705. **Chart selection** - For each data point, pick the simplest effective chart (see `references/chart-selection.md`)
1716. **Build** - Apply Lessons 3-5 while creating each section or view
1727. **Verify the Aha Moment** - Does it surprise? Shift understanding? Have an explicit "so what"? Is it at the climax, not the beginning?
1738. **Review** - Check horizontal logic (titles alone tell the story), vertical logic (each unit stands alone), and run the SUCCESs checklist
174
175### Format-Specific Considerations
176
177| Format | Key adaptations |
178| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
179| **Slide deck** | Sparse visuals (presenter narrates), one idea per slide, progressive build/reveal |
180| **Dashboard** | Self-explanatory (no presenter), overview panels first with drill-down detail, interactive filters to reduce clutter |
181| **Infographic** | Single linear flow top-to-bottom, strong visual hierarchy to guide the eye, must stand alone without explanation |
182| **Static site / playground** | Progressive disclosure (summary up top, detail below or on click), responsive layout considerations, can use animation/interaction for reveal |
183| **Written report** | More annotation and explanation than visual formats, charts support the narrative text rather than replace it |
184
185### Creating a Persuasive Pitch or Keynote
186
1871. **Define The Big Idea** (Duarte): One sentence = situation + complication leading to recommended action
1882. **Map the audience as hero** (Miller SB7): What do they want? What problem do they face (external, internal, philosophical)? How are you the guide?
1893. **Structure with Sparkline contrast**: Alternate "what is" vs "what could be" throughout
1904. **Plant a S.T.A.R. Moment** (Duarte): Something They'll Always Remember: a dramatic, tangible demonstration of the idea
1915. **Craft sound bites**: Small, repeatable phrases for headlines and sharing
1926. **End with New Bliss**: Paint the picture of the world with the idea adopted + clear call to action
1937. **Apply SWD Lessons 2-5** for any data slides within the pitch
194
195### Structuring a Personal or Conference Story
196
1971. **Find the five-second moment** (Dicks): What single moment of transformation is this story about?
1982. **Start at the end**: Know where you're going, then build backward
1993. **Begin in the opposite**: Open in the emotional/situational opposite of where the story ends
2004. **Apply the Dinner Test**: Would you tell it this way to a friend over dinner?
2015. **Load engagement devices**: Stakes (hopes/fears before moving forward), Surprise (build it, don't spoil it), Suspense (make them wonder what's next)
2026. **Slow down at the moment**: Use the Hourglass (Dicks): add detail and a beat right before the climax
203
204### Positioning a Product or Brand
205
2061. **Complete the SB7 BrandScript** (Miller): Character > Problem > Guide > Plan > CTA > Failure > Success
2072. **Define the villain**: Must be a root source (not a feeling), relatable, singular, and real
2083. **Articulate three problem levels**: External (tangible), Internal (emotional), Philosophical (why it's wrong)
2094. **Establish Guide credentials**: Empathy ("I understand") + Authority ("I've solved this before")
2105. **Show the transformation**: Clear before/after: who does the customer become?
2116. **Run SUCCESs check** (Heath): Is the message Simple, Unexpected, Concrete, Credible, Emotional, Story-driven?
212
213### Reviewing / Critiquing Existing Work
214
215Run through the **SWD Review Checklist** in `references/review-checklist.md`. For each chart, panel, section, or slide, evaluate against all 6 lessons and provide specific, actionable feedback. Additionally evaluate the narrative structure:
216
217- Does the presentation have a clear Hook within the first 60 seconds?
218- Is there a genuine Aha Moment (surprise + shift + "so what")?
219- Is the insight at the climax, not the beginning?
220- Does the narrative follow a coherent arc (not just a collection of charts)?
221- Would it pass the Dinner Test: is it told the way a human would tell it?
222- Does the closing provide clear, actionable next steps?
223
224### Chart / Visualisation Makeover
225
2261. Identify the core message (what should the audience think/do?)
2272. Choose a better chart type if needed (Lesson 2)
2283. Strip all clutter (Lesson 3)
2294. Apply grey + accent colour strategy (Lesson 4)
2305. Add a declarative action title (Lesson 5)
2316. Add text annotations to guide interpretation (Lesson 5)
2327. Show before/after to demonstrate the improvement
233
234---
235
236## Reference Files
237
238| File | When to read |
239|------|-------------|
240| `references/narrative-frameworks.md` | When structuring any narrative: data stories, pitches, keynotes, brand positioning. Contains Dykes (Data Storytelling Arc), Duarte (Sparkline), Miller (SB7), Dicks (Five-Second Moment), Cron (Brain Science), Heath (SUCCESs). Framework selection table is in Lesson 6. |
241| `references/hooks-and-moments.md` | When crafting a hook or aha moment. Contains 6 hook types, the Insight Test, placement principles, and engagement devices. |
242| `references/chart-selection.md` | When choosing a chart type or advising on visual selection |
243| `references/review-checklist.md` | When reviewing or critiquing existing data communications |
244| `references/colour-and-emphasis.md` | When making colour choices or applying emphasis strategies |