storytelling-with-data
Apply storytelling principles to create, review, and improve data visualisations and data-driven communications. Use when creating charts, dashboards, infographics, presentations, pitch decks, or reports that communicate data, or when structuring narrative arcs, hooks, aha moments, or persuasive stories.
What this skill does
# 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. ## When to Use This Skill - **Creating**: Building new visualisations, dashboards, infographics, presentations, pitch decks, or data-driven pages - **Reviewing**: Critiquing existing data communications for clarity and impact - **Improving**: Performing "makeovers" on charts, dashboards, or layouts to make them more effective - **Advising**: Helping choose the right chart type, structure a narrative, declutter, craft a hook, or position a message - **Storytelling**: Structuring any narrative: data stories, pitches, brand positioning, conference talks, stakeholder briefings > **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: 1. **WHO** is your audience? What do they care about? What's their relationship to you? What will motivate them? 2. **WHAT** do you need them to know or do? Define the single action or takeaway. 3. **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):** 1. Remove chart borders 2. Remove or lighten gridlines 3. Remove data markers (unless specific points need emphasis) 4. Clean up axis labels (round numbers, remove unnecessary precision) 5. Label data directly (eliminate legends where possible) 6. 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. **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 | | #### The Data Storytelling Arc (Brent Dykes) - Default for Data Presentations 1.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.