Product Sense · medium

A stakeholder asks for a dashboard showing everything. How do you respond?

Asked in BI Developer interviews.

Short answer

Push back with questions, not a wall of charts: what decision does this drive, who acts on it, how often, and what would make them act differently? Then design to that decision. Everything dashboards get built once and never opened — a dashboard is a decision tool, not a data dump.

How to answer it

"Everything" is a request for reassurance, not a spec. The job is to find the decision underneath it and build for that.

Ask, in roughly this order:

• What decision will this help you make, and how often? Weekly hiring plan and quarterly budget are different dashboards.
• Who looks at it, and what do they do after? A person who acts needs different information from a person who reports upward.
• What would make you change course? That answer is the metric.
• What do you look at today, and what is missing from it? Usually the real request is one specific gap.

Then propose something smaller and concrete. "A one-screen view of the four numbers that drive the weekly decision, each with target and trend, and a second page with the breakdowns you would look at when one of them is off." Offer to add a section when a real question needs it, rather than guessing at all possible questions now.

Say why you are pushing back, in their interest: dashboards with forty charts are built once and opened rarely, because there is nothing on them to act on. A dashboard that gets used is one where a number going red tells someone what to do.

Worked line: "The ask was 'everything about sales'. The decision was where to send the two new reps next quarter. The dashboard became pipeline by region with win rate and cycle time, and it is opened every Monday."

• What they are checking: whether you can question the request without refusing it, and whether you design to a decision.
• Common mistake: building everything. It ships late, loads slowly, and nobody can find the one number they needed.

Related questions

• Estimate the number of ride requests in a city per day.
• How would you measure the health of a subscription business?
• How do you design a KPI dashboard for an executive who has 30 seconds?
• What makes a chart misleading, and how do you avoid it?
• Design an experiment to test a new recommendation algorithm.
• What is the difference between WHERE and HAVING?

Practice this for real

• Check your resume against a BI Developer job description — free, no account needed.
• Every data interview question, by role and topic
• Scored AI mock interviews — two free, no card