The dashboard your store manager will actually open

The same dashboard that wins the boardroom presentation is usually the one the store manager closes within thirty seconds. They are different audiences solving different problems on different time horizons. A dashboard that does both is a dashboard that does neither well.

Three audiences, three jobs to be done

• Store manager — “what should I do in the next thirty minutes?” Needs a small number of live signals with clear thresholds and a response. Anything else is noise.
• Operations lead — “how is the chain trending this week?” Needs comparability, drift detection and outlier flagging. Cares less about live and more about reliable.
• Executive — “are we on plan?” Needs trend, exception and a small number of high-confidence numbers tied to commercial outcomes.

A dashboard built for the executive will overwhelm the store. A dashboard built for the store will frustrate the executive. The fix is role-based views — same data, different surfaces.

What the floor view looks like in practice

• Five live signals or fewer, each with a threshold and a response.
• A queue alert that goes to the role that can actually clear it, with a clear definition of “cleared”.
• Conversion-proxy as a moving comparison against the same hour last week — not against the chain average.
• Mobile-first — because the store manager is not behind a desk.
• No more than two clicks from any signal to the action.

How to know it is working

There are three signals that a dashboard is being used the way it was designed:

1. Daily active opens by role — not page views, opens by the people the view was designed for.
2. Time-to-action on alerts — a queue alert that is acknowledged in two minutes is real; one acknowledged in two hours is theatre.
3. Reduction in the questions the dashboard was supposed to answer — if the team still pulls the same Excel every Monday, the dashboard has not landed.

A short checklist before you ship

• Every chart answers exactly one question that has a known owner.
• Every signal has a threshold and a response.
• Every number has an accuracy figure attached to it.
• The mobile view is the design starting point, not the afterthought.