Topic 4 · Storytelling  ›  Week 8

Storytelling — Make the Data Mean Something

You can now build almost any chart. This week is about the harder half: why anyone should care. Charts show numbers; a story tells people what the numbers mean and what to do about them.

By the end of this week you can…

  • Name the three elements of data visual storytelling and why all three are needed.
  • Storyboard a presentation before opening any slide software.
  • Structure a data story with a clear beginning, middle and end.
  • Choose a narrative order — chronological, or conclusion-first — and know when each works.
  • Test your own story with horizontal logic, vertical logic, reverse storyboarding and a fresh perspective.
● Lab Test this week — 20%

The Lab Test is held in Week 8 and covers Chapters 1–2 and Google Sheets (Weeks 1–7). It's a practical test: you'll work with data and build charts. Format, timing and what to bring are explained in class. Passing mark is 50%.

8.1  What data visual storytelling is

Data visual storytelling is the art of using a narrative, visuals and data to communicate insight and influence an audience. It turns complex information into a simple, clear story. Instead of just showing numbers and charts, you build a narrative that helps people understand what the data means — making it meaningful, relatable and actionable.

Three elements — you need all three
DATA accurate, analysed NARRATIVE meaning & call to action VISUALS patterns made instantly clear a story

Data is the evidence — it must be accurate and properly analysed. Narrative explains what it means, with a beginning, middle and end. Visuals make the pattern clear without forcing anyone to decode a spreadsheet.

● Why bother

Combining the three turns a dry collection of numbers into something that resonates, is remembered, and drives a decision. A chart alone is information. A story is information people act on.

8.2  Storyboarding — plan before you build

A storyboard is a visual plan of your story. It's the first step in making a clear, effective presentation — and it happens on paper, not in slide software.

✗ What most students do

Open Google Slides, start making slide 1, keep adding until it feels like enough. Result: a disorganised deck with no real point, and a main message buried on slide 14.

✓ What to do instead

Sketch a simple outline first — one box per idea. Focus on structure and flow. Establish your main point early, so the audience knows immediately why they should care.

A storyboard is just boxes in order
Problemthe gap Contextwho & when Evidencechart 1 Evidencechart 2 Solutionwhat works Actionnext step …or move the main idea to the front, so nobody waits to hear it

If your main idea only appears in the final box, consider starting with it — so the audience grasps the key message early and knows why it matters to them.

8.3  The beginning — set the context

Open by introducing the situation. Five questions give you everything you need:

ElementThe question to answer
SettingWhen and where does the story take place?
Main characterWho is taking action? (link them to your audience)
ImbalanceWhat has changed, or created the problem?
BalanceWhat outcome do we want?
SolutionHow will the change happen?
● The problem statement carries the whole story

Problems and conflict create interest and keep an audience engaged. If the problem isn't clear, the story won't hold attention. Frame it around the audience's problem so they feel connected to the solution — and open by showing the gap between the situation now and what could be.

● Example — Department of Science project

Setting: the national Department of Science, 2025.
Main character: the Department's research team.
Imbalance: research findings aren't reaching the public — the reports are too technical to understand.
Balance: the public and policymakers can clearly understand and use the research.
Solution: use storyboarding and data storytelling to present findings simply and engagingly.

8.4  The middle — show what could be

Having set the scene, convince the audience why action is needed. This is where your charts live. Keep the focus on the audience: why it matters to them, and what role they can play.

This is where your Week 5–7 work goes. Every chart in the middle should be answering one of the points above. If a chart doesn't advance the argument, it belongs in the appendix — or nowhere.

8.5  The end — call to action

Every story needs an ending, and a data story ends with a call to action. Be clear about what you want the audience to do with what you've shared. A strong ending loops back to the beginning: remind them of the problem, show why action is urgent, and finish with the next step.

● Session 1 recap

Data + narrative + visuals = a story. Storyboard on paper first, main point early. Beginning sets the context and the problem; the middle proves it with data and offers a solution; the end asks for action.

8.6  Narrative structure — order changes meaning

Narrative structure is how a story is organised: which events are included, and in what order. Change the order and you change how the story is understood.

A report presents facts directly. A narrative reveals them gradually — and that step-by-step reveal creates curiosity, keeps an audience engaged, and makes the meaning clearer. Without structure, data and words carry very little meaning; each section should make its purpose obvious so listeners can focus on the part that matters to them.

8.7  Two ways to order it

Chronological

Walk through the work as it happened:

identify a problem → gather data → analyse → reach a conclusion → recommend an action

Natural for a written report, where the reader can see how you got there.

Conclusion first

Lead with the answer, then justify it:

state what you want them to know or do → present the key points that support it → explain why it matters to them

Stronger for a presentation — it's clear from the first minute why the story matters.

8.8  The power of repetition

Repetition helps people remember. The structure is simple, and it works:

  1. Tell them what you'll say — in the introduction.
  2. Say it — in the main content.
  3. Remind them what you said — in the conclusion.
● Example — science learning programme

Introduction: “Today we'll look at why students are losing interest in science, and how a new hands-on programme can help.”
Main content: show the data on falling scores, explain the new programme, share results from other schools.
Conclusion: “To sum up: students are struggling, the programme works, and we should adopt it to make science exciting again.”

● Repetition ≠ duplication

Repeating the message helps the audience. Repeating the evidence does not — never show the same numbers as both a table and a chart. It will feel unnecessary to you because you already know the content; for the audience, hearing the message three times is what makes it stick.

8.9  Four tactics to check your story works

① Horizontal logic

Ideas flow from one to the next like links in a chain — read only the slide titles and the argument should still make sense.

Example: problem (students losing interest) → evidence (low scores) → solution (hands-on programme).

② Vertical logic

Everything on a single slide reinforces itself: content supports the title, words support the image, and the other way round.

Example: if the title says “students are bored with science,” the slide shows the survey results that prove it.

③ Reverse storyboarding

Start from your conclusion and work backwards, checking that everything genuinely supports it. The result should read like an outline of your story.

Example: conclusion = “we must adopt the new programme” → confirm the data, examples and story all lead there.

④ Fresh perspective

Ask someone unfamiliar with the project to review it. If they can tell you the key message, your flow works. If they can't, it doesn't.

Example: let a friend outside your group read your slides before you present.

Use one tactic, combine several, or invent your own flow. What matters is only this: can the audience clearly understand the message?

8.10  Using this in your assessments

This chapter is not theory you'll forget after the test — it's the backbone of both Week 14 tasks.

WhereHow to apply it
Group project reportChronological order fits the report structure: Introduction (problem & gap) → Methodology → Results (evidence) → Conclusion (recommendation). The Introduction section is your story's beginning.
PresentationTry conclusion first — open with your headline insight, then let the dashboard prove it. Use the tell/say/remind structure across your 15 minutes.
BothRun reverse storyboarding before you submit, and get a fresh perspective from someone outside your group.
● Try it · Storyboard your own project

On paper, draw six boxes. Fill them in for your group project: problem, context, evidence 1, evidence 2, solution, call to action. Then ask a member of another group to read only your box titles. Can they tell you your main message? If not, reorder the boxes before you build a single slide.

Key terms & definitions

Data visual storytelling
Using narrative, visuals and data together to communicate insight and influence an audience.
Storyboard
A visual plan of a story — one box per idea — made before any slides are built.
Imbalance
The change or problem that creates tension at the start of the story.
Balance
The outcome you want — where the story is heading.
Call to action
The explicit next step you want the audience to take, given at the end.
Narrative structure
Which events are included in a story and in what order; changing the order changes the meaning.
Horizontal logic
Each main point flows into the next, so the titles alone tell the story.
Vertical logic
Everything on one slide reinforces the slide's title and the other content on it.
Reverse storyboarding
Starting from the conclusion and checking backwards that all content supports it.

✅ Quick self-check

1. The three elements of data visual storytelling are…

2. When should you start building slides?

3. “Imbalance” in a data story means…

4. Reading only your slide titles should still tell the story. That's…

5. For a 15-minute presentation, the usually stronger order is…

Week 9 →