Project Retrospectives · Published August 14, 2026
Retrospective: A Dashboard Nobody Opened
The dashboard looked great and leadership applauded. Three months later its open rate was close to zero.
We built an operations dashboard for a retail client. The launch demo went well. A follow-up three months later showed fewer than ten visits a day, half of them our own tests.
Why nobody used it
The metrics were not decision inputs. The numbers looked good but did not imply an action, so store managers kept ordering on instinct.
Reaching it took a login and three menu levels, and the mobile experience was worse.
Data refreshed a day late, which is useless for daily ordering.
What version two changed
Metrics became action-oriented: instead of total sales, the dashboard shows SKUs that need replenishment and suggested quantities.
A summary card is pushed through the company chat every morning, linking straight to the detail.
Extraction runs hourly, making key metrics near real time.
A dashboard earns its place by driving decisions, not by showing data. If it cannot answer what to do next, nobody opens it.
← Previous post
Making Dashboards Actually Used: Three Design Principles
Next post →
A Quarterly Tech Sharing Day
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →