3 things that make your dashboards seem bad, but actually make them good
While studying law, I learned about plain English—a writing style that's clear and easy for everyone to understand, not just lawyers. I’ve done my best to use that style in this article!
If you’re reading this blog, you probably love dashboards, but not every dashboard looks like a winner at first glance. In fact, some of the features that might make them seem "bad" can actually be the key to long-term success. Here's why some dashboards that might scare off developers or operations teams can actually be game-changers:
Dashboards that are hard to get started
Certain dashboards might seem intimidating because they require extra work to set up. Many dev/ops teams shy away from dashboards that need complex integrations or hard tasks to get going. However, this challenge can actually be a sign that you're working towards a more powerful tool.
Why it's good:
When you play the long game and invest time into building the dashboard, you're creating something that will ultimately streamline your team’s processes. For example, integrating analytics into your sales reps’ workflow might seem tricky, but once done, it addresses real problems users face. A date comparison dashboard is a great example—it is quite hard to configure (at least in CRM Analytics), but it provides valuable insights - period over period comparison - that users need in their everyday work.
In short, features that are complex to build, may be much more useful than simple features.
2. Boring dashboards
Dashboards that show simple metrics can seem boring and uninspiring. They don’t have the bells and whistles of “fun” dashboards with fancy visuals or interactive elements. However, these basic dashboards often hit the mark better than you think.
Why it's good:
Simple dashboards focus on core metrics, making them more user-friendly and practical. Their no-frills design can have a much higher hit rate — meaning users usually are not data crunchers and they just need simple guidance how to make their work better. A “fun” dashboard with too much going on may lose its appeal quickly, while a basic, mobile-friendly dashboard serves its purpose day in and day out, especially for people on the go.
Have a look at your dashboards:
How many filters are there?
Do users understand the metrics?
Is it clear what to do with the insights?
Does your data tell the story?
3. Dashboards that already exist elsewhere
Sometimes teams hesitate to create a new dashboard because similar ones already exist in other platforms, like Salesforce reports or PowerBI. It might feel redundant to build another one, but this assumption can be misleading.
Why it's good:
If users aren’t engaging with existing dashboards, there’s usually a reason behind it—perhaps the UI is clunky, too many clicks are needed, they are not pre-filtered, or the data refresh is slow. In such cases, creating a new dashboard with better UX or incorporating CRM Analytics features like actions, can be a unique selling point. Don’t shy away from building a fresh dashboard—look at what’s broken in the existing ones and focus on fixing those pain points.
Dashboards that seem difficult, boring, or redundant at first can actually be the most effective ones in the long run. Instead of focusing on flashiness or ease of use right away, play the long game. By building dashboards that address real user problems, provide simple but valuable insights, and improve, you create something that delivers consistent value over time.
