All articles
Oct 14, 2026

Nobody Needs Another Dashboard

Nobody Needs Another Dashboard

I was in a board meeting once — won't say which company — and the CMO pulled up a dashboard with 47 metrics on it.

Forty-seven.

The CMO walked through it, slide by slide, metric by metric. Traffic's up 12%. Engagement's flat. The funnel visualization looked like a modern art installation. Everyone nodded.

Nobody learned anything.

After the meeting, the CEO pulled me aside and asked, "So... are we doing okay?"

That's the state of analytics in most companies. Mountains of data. Dashboards that cost six figures to build. And the CEO still has to ask a human being whether things are going well.

I told him the truth: pipeline was fine, but enterprise deals were stalling in legal review, and two big renewals were at risk because onboarding was understaffed. I knew that from four numbers, not forty-seven. The CMO's dashboard got cut to nine metrics. Two quarters later, the company was running a weekly 30-minute pipeline review — no slides, just what moved and why. Because someone finally said what was true.

Most analytics is theater. It's the appearance of knowing without the substance. And it's everywhere.

---

Here's the distinction that matters: reporting is not knowing.

Reporting is: "Here are the numbers." It's backward-looking, comprehensive, and safe. Nobody gets fired for presenting a thorough report.

Knowing is: "Here's what's happening, here's why, and here's what we do next." It's forward-looking, selective, and risky. It requires judgment. It requires someone to say "this metric matters and those forty-six don't."

Most teams are world-class at reporting and terrible at knowing. All numbers, no knowledge.

---

I watched a company die with great metrics once.

Traffic was up 40% year over year. Social engagement was through the roof. Their NPS was 62 — genuinely good. The marketing team was winning every internal award. The board decks were beautiful.

Meanwhile, pipeline had collapsed 30% in two quarters, and nobody caught it because the pipeline numbers were buried on tab four, underneath the traffic charts everyone was celebrating. By the time someone looked, the sales team had already started quitting. The "engagement" was people reading free content. The NPS was from users who loved the product and would never pay for it.

Traffic up. Pipeline dead. Nobody noticed because the metric that mattered wasn't the one anyone was looking at.

Vanity metrics aren't just useless — they're camouflage. They give everyone a story to tell while the real story goes untold. A rising chart is a sedative. It makes the room feel calm right up until the layoffs.

---

So what does signal actually look like?

Signal is the one number — or the small set of numbers — that tells you whether the machine is working. Not vanity metrics. Not "engagement." The number that, if it moves, means something real changed in the business.

For most B2B companies, it's pipeline velocity. Let me make that concrete.

Say you're a SaaS company with a $2M pipeline target per quarter. You've got 200 opportunities open. Here's what signal looks like:

  • **Stage conversion rates.** Of 200 opps, 80 in discovery, 60 in demo, 35 in proposal, 25 in negotiation. If discovery-to-demo converts at 40% but demo-to-proposal at 15%, your problem isn't lead volume — it's the demo. More leads won't fix a broken demo. They just feed more deals into the place where they die.
  • **Stage duration.** Deals sit in proposal an average of 21 days. Last quarter it was 12. Maybe it's procurement season. Maybe your champion left. You don't know yet — but you know where to look, because the number moved.
  • **Week-over-week movement.** You don't need the full funnel every week. You need four numbers: how many deals entered, how many advanced, how many died, and the total value of what moved. If entered is steady, advanced is dropping, and died is rising, you have a conversion problem. If entered is dropping, you have a top-of-funnel problem. The diagnosis is different. The fix is different.

That's the signal. Everything else — traffic, engagement, email open rates — is context. Useful context, sometimes. But context.

For a content business, it might be the ratio of new to returning audience. For a product-led company, it might be time-to-value for new signups.

The point isn't which metric. The point is that you should be able to name yours in one sentence. If you can't — if you need a dashboard with 47 tiles to explain whether you're winning — you don't have signal. You have noise with good design.

---

Why do teams drown in metrics? Four reasons.

Nobody wants to choose. Picking the metric that matters means deprioritizing the ones that don't. That means telling someone their dashboard tab isn't important. That means having an opinion. Most organizations would rather measure everything badly than measure the right thing well.

Tools made it too easy. Modern analytics platforms will track anything, so teams track everything. The marginal cost of another metric is zero, so there's no discipline. Data hoarding.

Reporting became the job. Somewhere along the way, "analytics" became synonymous with "building dashboards" instead of "producing insight." The analyst who builds the beautiful 47-metric dashboard gets praised. The analyst who says "here are the three numbers that matter and here's what they're telling us" gets asked where the other 44 are.

Nobody owns the question. There's always someone who owns the dashboard — the analyst, the ops person, the vendor. But who owns the answer? Who's accountable for saying "here's what's happening and here's what we do"? When nobody owns the question, analytics defaults to whatever's easiest to produce: a report. Assign the question to a person with a name, not a team with a backlog.

---

I built something called Signal because I kept watching this happen. It's not a pitch — it's why I care. I wanted a way to cut through the theater and get to what's actually true.

But you don't need my tool. You need the discipline.

Here's the exercise. Block 30 minutes. Get the people who touch revenue in the room — sales, marketing, whoever owns the number. No slides.

Minutes 0–10: Name your three. Each person writes down the three numbers they'd track if they could only track three. No discussion yet. Just write.

Minutes 10–20: Defend them. Go around the room. For each number: what decision does it drive? If nobody can name one, it goes on the kill list. Be ruthless. "It's interesting" is not a decision.

Minutes 20–30: The subtraction. Take the kill list and ask: what do we stop measuring, stop reporting, stop discussing? Assign an owner to kill each one. Not "deprioritize." Kill. Every metric you track that doesn't drive a decision is noise making the real signal harder to hear.

What you're left with is the beginning of signal. It won't be perfect. You'll adjust. But you'll have done the thing most companies never do: chosen.

---

The companies that know what's happening don't have better dashboards. They have better judgment about what to look at.

They've done the hard work of deciding what matters. They've had the uncomfortable conversations about what doesn't. They've accepted that knowing requires choosing, and choosing requires someone willing to be wrong.

Dashboards don't produce clarity. People do.

Stop building dashboards. Start knowing.

A note from the author

Thanks for reading. If this sparked something — a question, a disagreement, a project idea — I want to hear it.

The fastest way to reach me is steve@stevepeeleii.com, or say hello through the contact page.

— Steve Peele II