More Data, Less Value

How our obsession with dashboards and real-time reporting may be costing us more than it's giving us — and what to do about it.

The Process Debt Podcast

When we were kids, the news came at predictable times. Evening, then again at 10, then in the morning as a physical newspaper on the doorstep. And then CNN arrived — 24 hours of news, every day. Suddenly, to fill all that airtime, the definition of "newsworthy" had to stretch. What was once signal became noise. What was once journalism started to look a lot more like entertainment.

We think the same thing has happened inside our organizations — and we're calling it the dashboard problem.

From financial statements to real-time feeds

Before spreadsheets and databases, business reporting was boring by necessity. You had financial statements. They were static. They came out once a month, maybe once a quarter. Nobody was checking them hourly because there was nothing to check.

Then came dynamic data tools, real-time integrations, and the ability to watch your deal flow tick second by second. The tools got better. The data got richer. And somewhere along the way, we started confusing more for better.

"More might be better. More might be worse. But better is always better."

The truth is, most of the reporting dashboards living inside organizations today aren't serving the people doing the work — they're serving management's need for a sense of control. And maintaining them comes at a real cost: data entry overhead, administrative lift, and the quiet drain of people spending time updating reports instead of taking care of clients.

The CYA dashboard

Here's a pattern we see constantly in implementation work: a team migrates to a new platform and almost immediately, the first major requirement isn't functionality — it's reporting. Leadership wants full visibility into how everything is working before anyone has actually learned how the tool works.

The result is what we call the CYA dashboard: a report built not because it drives better decisions, but because it provides cover. Someone fills it out. Nobody quite knows why. The tool becomes a compliance exercise, and the organization gets an administrative burden without the operational benefit it was hoping for.

The two common culprits: Sales funnel tracking and service delivery hours are the two areas where we most often see this pattern. Both require disciplined, structured data capture habits. Everyone wants the macro trends — but the lift required to produce accurate data is enormous, and frequently underestimated.

When reporting becomes political

There's another cost that's harder to measure: reporting culture makes work more political. When the story around the data matters more than the data itself, you stop making decisions and start making narratives.

The same dataset, presented differently to two different stakeholders, can tell two completely opposite stories. At that point, the report isn't illuminating anything — it's just a weapon in an internal argument. The customer disappears from the conversation entirely.

The weight-loss scale analogy

Think about trying to lose ten pounds. The basic math is simple: eat less, move more. But you can also weigh yourself six times a day, log every calorie down to the gram, and obsess over your wrist monitor. If you do, you'll notice that the scale never stops moving — because every breath you take releases a tiny amount of water vapor. At sufficient precision, the number is always changing.

What are you actually learning from that? Probably not much. What you're getting is a dopamine hit — the same dopamine hit that keeps people refreshing their dashboards all morning.

The real drivers are the activities: what you eat, how much you move. Those are the inputs. The scale is just the lagging indicator. Obsessing over lagging indicators doesn't change them — it just keeps you busy.

So when does real-time reporting actually matter?

It's not that dashboards are always useless. If you're running an Indy 500 pit strategy or monitoring a rocket in flight, second-by-second data is genuinely valuable. The velocity of the situation demands it.

But very few business situations have that kind of velocity. If you're running an 18-month implementation project, you probably don't need to check your progress report daily. If your website isn't on fire, you probably don't need to look at your traffic dashboard hourly.

"Unless your website is down or there is some major problem, you can probably just look at it twice a day."

The question worth asking isn't can we report on this — we almost always can. The question is: what decision will this information actually change, and how often does that decision need to be made?

A few things worth revisiting

If any of this sounds familiar, here are three prompts worth sitting with:

Is this report serving the work, or just management's comfort? If the people doing the work don't benefit from the report, that's worth examining. Administrative overhead that only serves upward visibility has a real cost.

How often does this data actually need to change hands? Not every metric needs a live feed. Some things are well-served by a monthly sit-down in a room with a printout — and that cadence forces better conversation.

Is the habit ongoing, or is it an experiment? Many reporting processes started as experiments and calcified into permanent rituals. There's value in periodically asking whether the ROI still pencils out — or whether the meeting, the dashboard, and the hour of data entry each week are quietly costing more than they're returning.

In a world of abundant data, curation is the skill. And sometimes the most valuable thing you can do with a dashboard is decide you don't need it as often as you thought.