"We Need a Dashboard" — No, You Need an Alert

Whenever an operational bottleneck hits a growing company, the executive response is almost a reflex: 'We need a dashboard for this.'

It sounds great in a meeting. Visibility! Data-driven decisions! Transparency! So an analyst spends a week wiring up Metabase or Looker. They build a beautiful array of charts showing 14 different metrics. It gets shared in the company all-hands.

And then, exactly two weeks later, nobody looks at it ever again.

Why? Because human beings don't want to constantly monitor data to figure out if they should do their job. Looking at a dashboard requires cognitive load. You have to open the link, parse the charts, compare the current state to the expected state, and then decide if an action is required. That’s friction.

You don't need a dashboard. What you actually need is an alert.

Dashboards are for exploration; alerts are for execution. Instead of building a chart that shows 'Clients stuck in onboarding for more than 7 days,' build a Slack integration that pings the account manager directly at 9:00 AM on Tuesday saying: 'Client X has been stuck in onboarding for 8 days. Click here to follow up.'

A good operational system doesn't ask you to go find the problem. It brings the problem to you, complete with a button to fix it. If you want to speed up your team, stop giving them more data to analyze. Start giving them clear instructions generated by the data.