Interview Prep · Data Analysts

Why Every Data Analyst Should Practise Explaining Their Dashboard Aloud

SECTION 01Why aloud, not silent

Reading silently is fast. Speaking is slow. That slowness is the point.

When you read a dashboard silently, your brain fills the gaps. When you speak, the gaps become audible. You'll hear yourself say things like:

• "This shows… uh… the churn is going up…" — vague claim.
• "The metric here is… defined somewhere…" — you don't own the metric.
• "This is from last quarter." — no baseline, no context.

Every stumble is a data point. Fix the stumble, and the dashboard gets stronger — before any interviewer sees it.

SECTION 02The 3 levels of explanation

Level 1 — Read it

You describe what the dashboard shows. "This shows revenue by region over the last 90 days." Anyone could do this. If this is all you can do, you're not ready.

Level 2 — Explain it

You describe what the dashboard means. "The Q3 dip is driven by three enterprise accounts that renewed late; here's the fix we recommended." This shows analysis.

"This dashboard shows weekly sales by region over
the last 90 days."

"Weekly sales by region over the last 90 days.
Q3 dipped 8% — but that's three enterprise
accounts renewing late, not a market issue.
Those three are 61% of the dip. Without them,
Q3 is flat at +1%."

Level 3 — Defend it

You defend it under follow-up. "Yes, the definition of 'active user' changed in August — we measured both definitions for a month and the trend held, so I'd stand behind it." This shows judgement.

Interviewer: "Wait — didn't the definition of
'active user' change in August?"

"Yes. We changed the definition in August from
'session in last 30 days' to 'any meaningful
action in last 30 days'. I measured both
definitions side-by-side for a month — the
trend held within 2%. I'd still stand behind
the conclusion, but if you want, I can flag
the data in the dashboard as a tooltip."

SECTION 03The 5-step routine

Run this routine once per dashboard, out loud, ideally to a friend or a camera. It takes 8-10 minutes.

Step 1 — Problem (30 s)
"What decision does this dashboard help someone make?
 Who is the decision-maker?"

Step 2 — Decision (20 s)
"Which specific decision, and how often?
 Weekly pricing review? Monthly churn triage?"

Step 3 — Walkthrough (90 s)
"Top to bottom, left to right. Each chart,
 what it answers, what it doesn't answer.
 Point out one thing that looks weird and
 explain it in one sentence."

Step 4 — Impact (30 s)
"One number: what changed because of this
 dashboard's existence? Time saved, cost cut,
 decision made faster?"

Step 5 — Next (20 s)
"What would I change about this dashboard
 if I had another sprint? What's the weakest
 signal here?"

Total: 3 minutes 10 seconds
Target: 2-3 minutes in an interview.

If you're over 4 minutes, you're reading
instead of explaining.

If you're under 90 seconds, you're skipping
the walkthrough — which is the part
interviewers actually evaluate.

Practice three times per dashboard:
  Pass 1: just read it (baseline).
  Pass 2: explain it without pausing.
  Pass 3: record it, listen back, score it.

SECTION 04Common stumbles

When you say it aloud, these phrases come out. Each one signals a weakness the interviewer would have found anyway.

SECTION 05A self-scoring rubric

Record yourself explaining the dashboard. Play it back once. Score each line 0-2. A total of 8+/10 means you're interview-ready.

Scoring rubric (max 10):

☐ Problem statement named (0-2)
☐ One decision named (0-2)
☐ Each chart explained (0-2)
☐ One number of impact (0-2)
☐ One "what I'd change" line (0-2)

Bonus: handles one follow-up cleanly (+1)

Score guide:
  9-10 — interview-ready, can defend live
  6-8  — solid, needs one more pass
  3-5  — reading, not explaining
  0-2  — you don't know your dashboard yet

SECTION 06Interview Q&A

SECTION 07Test yourself

SECTION 08Frequently asked questions

SECTION 09Related reads