Data Quiz
An activity that makes your team data-driven.
It is a multiple-choice quiz you build from your own product analytics and run with your whole design team. You end up with a dashboard the team keeps. They come back to it again and again, so the reflection stays alive instead of fading after one meeting. Here is how to run it.
The premise
Being data-driven has nothing to do with staring at dashboards.
Most designers nod at data and move on. The quiz forces the issue. You turn the dashboard into questions and let the team find out, live in the room, where their gut and the truth part ways. Nobody has to get defensive about the gap. The gap is the whole point.
How to run it
Invite the full design team. UX, UI, service, research. Same room, same questions, same time. That shared moment is what makes the gaps safe to talk about.
Example. Nine designers block one hour. Every laptop stays closed except yours.
Open your product analytics and turn five or six findings into multiple-choice questions. Keep them concrete and specific. Four options each, one right answer.
Example. Which screen do users drop off on first? When did we launch the new onboarding? Where do most taps land on the home tab?
Everyone votes before the answer shows. Reveal the real number. Give three minutes per question: where did our gut match, where did we miss, and why.
Example. The room bets everyone loves the new filter. Analytics says 2% ever touch it. That gap is the conversation.
Skip the final score. Save the questions as a live dashboard the team can reopen any week. The activity wraps in an hour. The artifact and the habit stick around.
Example. The same dashboard shows up in the next three design critiques, and nobody had to ask for it.
Why it matters
Designers lean on user interviews as their source of truth. Leaning too hard on a few voices misses the bigger shape. The quiz trains you to look for the pattern.
OKRs, KPIs, behavioural data and qualitative research each do different work. The quiz makes the gaps between them visible, and nobody has to get defensive about it.
Forget the score and the winner. What you keep is a team with a shared dashboard, a shared vocabulary, and honest agreement about what they did not know.