There is a particular satisfaction in a good dashboard. The numbers update, the charts move, the colors tell you at a glance whether things are green or red, and sitting in front of it you feel informed, on top of the operation, in command of what is happening across the portfolio. That feeling is real, and it is one of the reasons dashboards proliferate: every team wants one, every meeting opens with one, and every new system arrives promising another.

The uncomfortable question is whether that feeling of being informed corresponds to actually being more effective, and often it does not. A dashboard can deliver a strong sense of insight and control while the things that actually determine outcomes, diagnosing why a number moved, deciding what to do about it, and doing it, go unaddressed. Watching the numbers is not the same as understanding them, and understanding them is not the same as acting. The dashboard is very good at producing the feeling of the first while quietly substituting for the other two, and an organization can accumulate more and more of them while getting worse, not better, at the work they were supposed to support.

Reviewing the KPIs is not the same as managing

The core problem has a precise name, and it is worth stating plainly because it hides inside a phrase every leadership team uses. In meetings, "we reviewed the KPIs" is treated as though it means the situation is being managed. But as one analysis of why dashboards fail puts it, reviewing the dashboard often just means "we felt informed," and feeling informed is not the same as changing outcomes. This is the illusion of control: mistaking observation for influence, the act of looking at the numbers for the act of affecting them.

The mechanism underneath it is a documented gap between knowing and doing. Dashboards, the same analysis notes, tend to stop at awareness: once people understand what happened, they feel prematurely complete and stop before deciding what to do. Understanding satisfies the brain's need for closure, so the meeting reviews the numbers, everyone leaves feeling that something has been accomplished, and nothing has, because no decision was made, no owner assigned, no action taken. The dashboard delivered the sensation of management without any of its substance.

A useful test cuts straight through it: after a dashboard review, does the meeting end with a specific decision, a single owner, and a deadline? If it ends with a shared sense of being caught up, the dashboard produced comfort, not commitment, and comfort is the more dangerous output because it feels productive.

Why more dashboards make this worse, not better

If one dashboard can substitute the feeling of insight for the work of it, more dashboards compound the problem rather than solving it, and they do so through a few mechanisms.

The first is that attention is finite and dashboards are not. Working memory holds only a handful of things at once, research puts the effective range at five to nine items on a screen, and past that, more metrics do not mean more understanding, they mean more noise competing for the same fixed attention. When you try to look at everything, you end up seeing nothing, because nothing is prioritized and the signal that matters is buried among the fifty that do not. The proliferation of dashboards is, in effect, a steady dilution of attention across an expanding surface of numbers, and diluted attention is worse at spotting the one thing that actually needs a decision.

The second is tool sprawl. Each new system arrives with its own dashboard, its own login, its own slightly different version of the truth, and teams end up spending as much time toggling between them and reconciling which number is right as they do acting on any of them. The dashboards multiply, and the fraction of time spent on genuine diagnosis and decision shrinks, because the overhead of navigating the dashboards has itself become work.

The third is the most subtle: more dashboards deepen the illusion. The more comprehensively you can watch the operation, the more strongly you feel you are managing it, and the wider the gap can grow between that feeling and the reality of whether anything is being decided and done. A leadership team with ten dashboards can feel ten times as informed while being no more effective, and possibly less, because the time that went into building and reviewing the dashboards came out of the time available to think and act. This is related to, but distinct from, the problem of reports accumulating faster than anyone can read them, examined in the reports nobody reads are about to multiply: that is about volume overwhelming attention, while this is about the dashboard actively manufacturing a false sense that watching is managing.

What a dashboard can and can't do

It helps to be precise about where the line falls, because the dashboard is genuinely good at some things and the problem is asking it to do the things it cannot.

A dashboard is excellent at monitoring: showing you the current state, alerting you that something has changed, telling you that a number is now red that was green. That is real and valuable, and for genuinely operational, act-now situations, unit availability during leasing, a payment that needs authorizing, a threshold breached, fast monitoring is exactly the right tool.

What a dashboard cannot do is the part that actually creates value, and asking it to is the error. It cannot tell you why a number moved, which requires diagnosis, digging beneath the metric into the specific, often messy, causes. It cannot tell you what to do about it, which requires judgment that weighs context the dashboard does not contain. And it certainly cannot do the thing, which requires a decision and an owner and follow-through. The dashboard shows you that occupancy dropped. It does not tell you that the drop is concentrated in one property, driven by a specific problem, requiring a specific response, and it will never make that response happen. Treating the dashboard as if it delivers understanding and action, when it only delivers awareness, is how the illusion takes hold.

The failure, in short, is not a bad dashboard. It is a good dashboard asked to be a substitute for thinking.

The honest part

Several qualifications keep this from becoming an argument against dashboards, which would be foolish.

Dashboards are genuinely valuable for what they are for. Fast, well-designed monitoring of the metrics that require quick action is a real capability, and an operation flying blind because it rejected dashboards would be far worse off than one that uses them well. The argument is against dashboard proliferation and against mistaking monitoring for management, not against the tool. A small number of well-chosen dashboards, tied to decisions, is an asset.

There is also a legitimate role for exploratory, comprehensive data views, and this is not a demand that every screen be ruthlessly minimal. Analysts doing genuine investigation need access to depth and breadth, and a rich analytical environment serves that. The problem is specifically the executive or operational dashboard that is supposed to drive attention and action, becoming bloated and mistaken for management. Different surfaces have different jobs, and the caution here is aimed at the decision-driving one.

And the underlying instinct, wanting visibility into the operation, is correct and healthy. A leader should want to see what is happening. The failure is not the desire for visibility, it is stopping at visibility, treating the seeing as the managing. The fix is not to see less but to insist that seeing leads to deciding and doing, rather than terminating in a comfortable sense of being informed.

The discipline that turns watching into managing

The practical shift is to hold every dashboard to a single standard: does looking at this change what we do? A dashboard that informs but never alters a decision is producing the feeling of management without the substance, and the cure is to connect the watching to acting deliberately, because it does not happen on its own.

Concretely, that means ending dashboard reviews with a decision rather than a feeling. If a review of the numbers does not conclude with what we are going to do about this, who owns it, and by when, then the review was theater, however informed everyone felt. It means resisting the proliferation, keeping the decision-driving dashboards few and focused on the handful of things that genuinely warrant standing attention, and letting the rest be pulled on demand rather than watched continuously. And it means being honest about the difference between the dashboard's job and yours: the dashboard's job is to tell you something changed, and your job is the diagnosis, the judgment, and the action, none of which the dashboard will do for you no matter how good it looks.

The single question that exposes the whole trap: think about the time your team spends looking at dashboards, and ask how often that looking actually changes a decision versus how often it just leaves everyone feeling caught up. If the honest ratio is mostly the second, you do not have an insight problem that another dashboard will fix. You have a knowing-versus-doing problem, and more dashboards will make it worse, because the thing you are short of was never visibility. It was the decision and the action that visibility is supposed to serve, and those have to come from you.

FAQs

Q1. Don't dashboards help us make better decisions?
They can, but only when looking at them actually changes what you do. The common failure is that a dashboard produces the feeling of being informed without leading to any decision, a pattern sometimes called the illusion of control, where observation is mistaken for influence. A dashboard that informs but never alters a decision is delivering comfort rather than management, however sophisticated it looks.

Q2. What is the illusion of control in this context?
It is mistaking watching the numbers for affecting them. In practice it shows up as "we reviewed the KPIs" standing in for "the situation is being managed," when the review actually just produced a shared sense of being caught up. Feeling informed satisfies the brain's need for closure, so people stop at awareness and never reach the harder steps of diagnosing the cause and deciding what to do.

Q3. Why does having more dashboards make things worse?
Because attention is finite while dashboards are not. Working memory handles only a handful of items, so past a small number, more metrics add noise rather than understanding, and the signal that matters gets buried. Tool sprawl adds reconciliation overhead as teams toggle between systems, and the sheer comprehensiveness deepens the false sense that watching everything equals managing it, widening the gap between feeling effective and being effective.

Q4. What is a dashboard actually good at?
Monitoring: showing current state and alerting you that something changed. For genuinely act-now situations, such as unit availability during leasing or a threshold being breached, fast monitoring is exactly the right tool. What it cannot do is tell you why a number moved, which needs diagnosis, decide what to do, which needs judgment, or take the action, which needs an owner and follow-through. The error is asking it to do those three.

Q5. How do I know if my dashboard reviews are productive?
Check how they end. If a review concludes with a specific decision, a single owner, and a deadline, it drove management. If it ends with everyone feeling caught up and informed, it produced comfort, not commitment. The test is whether looking at the numbers changed what you do, or merely left you with the sensation of having done something.

Q6. Isn't this just an argument against using dashboards?
No. Dashboards are genuinely valuable for fast monitoring of metrics that need quick action, and an operation that rejected them would be worse off. The argument is against proliferation and against mistaking monitoring for management. A few well-chosen dashboards tied to decisions are an asset. The caution is aimed specifically at the decision-driving dashboard becoming bloated and treated as a substitute for thinking.

Q7. What about analysts who need comprehensive data?
That is a legitimate and different use. Genuine investigation needs depth and breadth, and a rich analytical environment serves it well. The problem addressed here is specifically the executive or operational dashboard meant to drive attention and action becoming overloaded and mistaken for management. Different surfaces have different jobs, and comprehensive exploration is not what this caution is about.

Q8. What should we actually do differently?
End dashboard reviews with a decision, an owner, and a deadline rather than a feeling of being informed. Keep the decision-driving dashboards few and focused on the handful of things that warrant standing attention, and pull the rest on demand. And stay honest about the division of labor: the dashboard tells you something changed, while diagnosis, judgment, and action are yours to supply, because visibility only creates value when it leads to a decision.