1 / 31

Designing data stories for small screens

A workshop on making stories survive real mobile reading conditions.

Areena Arora

Who am I?

Editorial coder. Data journalist. Often stuck between reporting, code, design, and the tiny angry rectangle where readers actually meet our work.

  • Interactive storytelling
  • Data journalism
  • Information design
  • Mobile-first public interest work

Let’s get to know each other.

NameWhat do you do?
ScreenWhat device do you usually design on?
PainOne mobile data story problem you keep seeing.

What this workshop is about

Diagnose
Redesign
Critique

We are not designing for a calm rectangle.

One hand. Low light. Notifications. Bad network.

A metro rail, a baby, a coffee, a bag, a plate of lunch — something else is always happening.

How do you usually start?

Desktop board→Mobile shrink

Most workflows start in generous space: large canvases, multiple panels, a mouse, stable attention. Then the phone becomes the afterthought. But mobile is more than just a smaller layout.

Can the reader still understand the story under interruption?

Desktop

Landscape

Many things can be visible at once. Meaning is assembled spatially.

Mobile

Sequence

One thing enters, then the next. Meaning is choreographed over time.

Attention economics

On mobile, try to include a striking number, a stark contrast, a bold claim with a dramatic consequence or a sharp visual feature at the start of the project. First insight isn’t the same as the headline.

Five kinds of friction

  • Entry
  • Memory
  • Interaction
  • Grip
  • Escape

Peripheral vision is a desktop luxury.

On a large screen, the reader can sense the legend, headline, note and sidebar while reading the chart. On a phone, those relationships break into separate moments.

Memory tax

Once the reader scrolls away, you are relying on them to remember the color code, axis, caveat, filter state or annotation.

Legend left behind
Blue meant… what again?

Every remembered relationship is a tax.

Legend rule

Label the thing. Don’t make me decode the key.

Mobile screenshot of a Reuters drone explainer with direct labels embedded in the visual.

Public dashboards

Filter first, insight later.

This pattern feels reasonable to the team that knows the data. But a public reader arrives with low context and low patience.

Dashboard redesign order

Outliers→Suggested paths→Filters

First show why the data matters. Then invite self-exploration.

Fixing dashboards

  • Cut columns to the story path.
  • Turn rows into cards on mobile.
  • Sort by largest increase, decline, highest value, your state.
  • Put search after summary, not instead of summary.

Maps are greedy.

If scrolling becomes zooming, the story stops progressing.

Map trap
Pinch. Zoom. Stuck.

The map took over the thumb path.

How to fix maps

  • Use a static map before tap-to-explore.
  • Keep map height modest unless it is the scene.
  • Add an escape lane or clear continue cue.
  • Replace maps with rankings when the task is comparison.

Scrollytelling

Mobile scroll is natural. But each step must fit with the visual state inside the same moment of attention.

  • Text step too long.
  • Graphic changes too early.
  • Annotation stays too long.
  • Step assumes old memory.
Phone screenshot of a The Hindu scrollytelling explainer with text and a recovery trajectory diagram.

Charting efficiently

  • Directly label line ends.
  • Label stacked segments if there are only two or three.
  • Reintroduce color meaning in scrolly steps.
  • Use exact values in text when exactness matters.
Chart vocabulary table comparing desktop and mobile chart choices, why they work on mobile, and things to watch for.
Chart vocabulary table covering distribution, relationship, flow or process, lookup or details, and many comparisons or exploration for mobile.

Sketching

  • Write five insights in order before drawing.
  • Pick the chart type after the insight sequence.
  • Use interaction stingily.
  • Define the default view.
  • Keep the color system explainable.

Reviewing prototypes

Put a thumb on it.

  • Where does the thumb naturally land?
  • What is hidden?
  • What two insights does another group learn?
  • Does that match what you intended?

Mobile survival checklist

  • Compress images.
  • Avoid unnecessary client-side libraries.
  • Provide fallbacks for heavy visuals.
  • Test on slow mobile data. Try the elevator test.