Product Thinking · Published July 11, 2026
Dashboards: Define the Metric Before Showing the Number
The same 'customer count' can mean three different things to sales, finance and operations.
We built a sales dashboard and three departments each reported wrong numbers. Sales counted signed customers, finance counted collected payments, operations counted registrations. All three were right, with different definitions.
Define metrics down to the field
Name, definition, time range and exclusion rules, all four. 'New customers' must state whether trials count and whether the date is signing or payment.
Store definitions in a metric dictionary inside the product, viewable from the page, instead of relying on verbal explanation.
Three dashboard habits
One screen answers one question. Too many metrics and nobody knows where to look.
Numbers must drill down. Being able to open the detail behind an anomaly beats ten more charts.
State the refresh time. A two-hour delay and real-time updates lead to completely different decisions.
A dashboard is not about beautiful charts. It is about everyone reading the same number the same way.
← Previous post
Message Queues Are Not a Cure-All
Next post →
Retrospective: The Cascade Behind One Change
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 →