Data

Building Analytics That Actually Drive Decisions

Why most dashboards fail and what to build instead

8 min read

I've built dozens of dashboards. Most of them collected dust. The ones that worked shared a few common traits that had nothing to do with the technology.

The Dashboard Graveyard

At CrewLAB, I built our first analytics suite in Looker Studio. Beautiful charts. Real-time data. Every metric you could want. Usage after the first week? Near zero.

The problem wasn't the data. It was that nobody had a clear action to take when the numbers moved.

Actionable Over Comprehensive

The dashboards that worked followed one rule: every metric had a clear "if this, then that" attached to it.

  • If activation rate drops below 40%, trigger the onboarding review
  • If CAC exceeds $50, pause the underperforming ad sets
  • If weekly active teams decline 10%+, schedule customer interviews

Build for the Decision, Not the Data

Start with the decision someone needs to make. Work backward to the data that informs it. Then build the simplest possible view that surfaces that data at the right time.

The best analytics aren't dashboards at all. They're alerts, automated reports, and embedded metrics that show up in the tools people already use.

David Kerns

David Kerns

Operator, builder, creative. Sharing thoughts on the intersection of operations, product, and making things that matter.

More about David

Enjoyed this post?

Subscribe to get new posts delivered to your inbox. No spam.