Stop Redesigning Broken Dashboards
A cleaner dashboard cannot save a number that was flawed from the start
When a chart is hard to understand, the first instinct is usually to change the chart.
Swap the pie chart for a bar graph.
Move things around.
Adjust the layout.
It feels productive, and at the end of the day, the page looks cleaner.
But changing a chart does not fix the math behind it.
This is one of the most common ways analytics work starts to go wrong.
The visual gets better. The metric stays broken. And the team moves on, confident in a number they never stopped to question.
Bad Metrics Do Not Announce Themselves
A broken metric does not always look broken. Most of them look completely normal on the surface.
The problem is in the definition, and you only notice the gaps when you look closely.
Take “active users.” It sounds simple. But what counts as active? Logging in once? Completing a specific action? Does the definition exclude bots, test accounts, or internal users?
If nobody has answered those questions clearly, the number means something different to every person looking at it.
Now take ‘churn rate.’ Most people think it means customers who canceled. But what about accounts that paused? Downgraded? Stopped paying but never fully closed?
If paused accounts are being counted as lost, churn looks worse than it actually is. The product gets blamed for a problem that may not exist in the way the data suggests.
These are not rare edge cases. They are the kinds of definition gaps that live inside common KPIs at real companies, often for years, with nobody raising a flag.
Good Looks Cannot Fix A Weak Number
This is where it gets risky.
When a number sits inside a well-designed dashboard with branded colors, clean headers, and a polished layout, it feels trustworthy. People trust it more because it looks more finished.
But if the math underneath is weak, the nice design can make things worse. It makes people trust a number that does not deserve it.
The gap between what a metric counts and what it is supposed to show is where quiet mistakes hide. A cleaner dashboard does not fix that.
Stop And Look At The Numbers First
A good analyst does not just build what they are asked for. They check the numbers before they ever touch the charts.
This means pausing to ask hard questions. They check if the rules have changed since the dashboard was first made. They check if the report is mixing things that should never be mixed.
Checking these details can feel very slow. It might even feel like you are creating problems instead of solving them. But these checks are the only way to keep the final report honest.
Without them, you just end up with a beautiful screen that tells a confident story about something that never really happened.
Design Last. Measure First.
The whole point of tracking data is to help people make better decisions. That only happens if the numbers measure exactly what they claim to measure.
Good design is meant to support good data, not replace it.
Before you start your next dashboard redesign, take a step back. Check your metrics. Make sure the logic behind the number is clear and that everyone agrees on it. Make sure the number is actually measuring what it claims to measure.
Once you trust the foundation, then you can start designing.



Designing a visual that facilitates a group decision by Execs across domains is actually really hard and sometimes, beautiful and/or too many visuals distracts from the math. For example, can anyone back into the numbers 🧮?