The Hidden Cost of Measuring the Wrong Things

There is an old management saying: “What gets measured gets managed.”

I think that’s only half right.

What gets measured gets attention. And what gets attention eventually changes behavior.

That can be incredibly powerful. It can also be incredibly dangerous. If you measure the wrong thing, your organization can become very good at producing a result that doesn’t actually matter.

The Number Can Be Right and the Organization Can Still Be Wrong

Imagine a nonprofit that measures how many people it serves. Last year, 5,000. This year, 7,000. Next year, 10,000.

The graph looks great. The board is happy. The annual report has a big number on the front.

But there’s another question: What happened to those 10,000 people?

That’s much harder to measure. And because it’s harder, organizations often fall back on the numbers that are easiest to collect: meals served, bags distributed, people attending, calls answered, volunteer hours, applications processed, dollars raised.

All of those numbers can be useful. But none of them necessarily tells you whether you accomplished what you exist to accomplish.

Activity Is Not Impact

This is one of the easiest traps for an organization to fall into. We confuse doing something with accomplishing something.

If a food pantry distributes twice as much food this year, that tells us something about its activity. It doesn’t automatically tell us whether the community is better off.

If a workforce program enrolls 500 people, enrollment is an output. How many found employment? How many were still employed six months later? How many increased their income? Those are different questions.

The same problem exists in business:

A sales team can make more calls without making more sales.
A warehouse can process more units while creating more errors.
A customer-service department can reduce call time while making customers call back twice.
A nonprofit can serve more people while producing less meaningful change.

The metric improved. The system didn’t.

People Learn What Matters

The moment you attach importance to a measurement, people start responding to it. Usually they aren’t doing anything wrong. They’re doing exactly what the system told them mattered.

Tell a call center that shorter calls are better, and calls get shorter.

Tell a development department that dollars raised are the primary measure of success, and attention moves toward the donors most likely to produce dollars.

Tell a program team that the number of people served is the measure, and eventually there will be pressure to serve more people.

That’s why metrics can’t be separated from behavior. Every measurement sends a message: This is what matters here. If leadership isn’t careful, employees eventually optimize the measurement instead of the mission.

Sometimes the Best Number Goes Down

This is where measurement gets interesting.

Organizations are conditioned to believe that up is good. More clients, more programs, more donations, more volunteers, more activity, more reach.

But what if success makes a number smaller?

If you run a program designed to prevent homelessness, is serving more people always evidence of success? Maybe. Or maybe the number you really want to see decline is the number of people who reach the point where emergency intervention is necessary.

If you help students overcome barriers that keep them out of school, perhaps success isn’t measured only by how many students received resources. Maybe it’s also measured by fewer absences.

The direction of a number doesn’t determine whether it’s good. Its relationship to the mission does.

Measure the System, Not Just the Result

One of the most useful things data can do is show you what’s happening inside the process:

How long does someone wait?
How many times is information entered?
Where do requests stall?
How often is work corrected?
How much capacity goes unused?
How often does someone leave the process before receiving help?

Those measurements may never appear in an annual report. But they may tell you far more about the health of the organization than the number on the front page.

This is where all the hidden costs we’ve been discussing begin to connect: friction, waiting, complexity, poor data, duplicate work, good intentions. Each one can hide inside a system while the organization’s headline metrics keep looking perfectly healthy.

If you’re measuring the wrong things, you may never see them.

The Dashboard Is Not the Mission

I love data. I believe organizations should measure relentlessly.

But measurement isn’t the objective. Understanding is.

A dashboard should help you see what’s happening. It should help you ask better questions, expose problems earlier, and challenge assumptions. Sometimes it should make you uncomfortable.

If every metric on your dashboard is green every month, I’d start asking whether you’re measuring enough of the right things. Healthy organizations still have problems. The difference is that good systems let you see them.

But there’s another danger: eventually, the organization learns how the dashboard works.

When a Measurement Becomes a Target

Suppose you decide orders should be completed within 48 hours. That sounds reasonable, so you measure it. You put it on a dashboard. Leadership starts reviewing it. Then someone asks why the number dropped from 94% to 87%.

Nothing is inherently wrong with any of that. But watch what happens next.

People now know that 48 hours matters. Someone discovers that the clock doesn’t start until an order reaches a particular status. So orders sit in the previous status longer. The dashboard improves. The customer doesn’t.

Or employees begin prioritizing easy orders, because completing five simple orders helps the metric more than spending the same time solving one complicated order. Again, the number improves. The system doesn’t.

This doesn’t require dishonest employees. It only requires human beings who understand how their performance is being judged. People adapt to systems, and measurements are part of the system.

You May Be Creating the Behavior You’re Measuring

This is the part leaders sometimes miss.

We see behavior inside an organization and assume it originated with the employee. Sometimes it originated with us. We told people what mattered. We created the incentive. We built the dashboard. We asked about the number at every meeting. Then we’re surprised when people organize their work around improving it.

Imagine a nonprofit development director whose performance is discussed primarily in terms of dollars raised. Over time, what will get more attention: one $100,000 donor, or 1,000 people giving $25? If the organization’s long-term strategy is building a broad base of community support, those smaller donors may be extremely important. But the metric is teaching the employee something else.

Or imagine a volunteer program measured primarily by volunteer hours. Twenty volunteers standing around waiting for something to do can produce more hours than ten volunteers working efficiently. Which program looks better on paper? The inefficient one.

That’s the hidden power of measurement. You don’t simply measure behavior. You can create it.

The Numbers We Show Other People

There’s another layer to this problem, especially in the nonprofit world. We don’t only measure for ourselves. We measure for boards, funders, donors, government agencies, partners, annual reports, and grant applications.

Each audience tends to want something simple. How many people did you serve? How many meals did you distribute? How many volunteer hours did you generate? What percentage of your budget goes to programs?

Simple numbers are easy to communicate. But complex problems rarely fit neatly into simple numbers.

So organizations start collecting the numbers other people want. Those numbers make their way onto dashboards. Dashboards influence decisions. Eventually, an external reporting requirement can quietly become an internal management system.

That’s worth paying attention to. A metric can be useful for reporting without being useful for managing. Those aren’t necessarily the same thing.

Big Numbers Are Seductive

There’s a reason organizations love cumulative numbers: they only get bigger.

“We’ve served 100,000 people.” “Volunteers contributed 50,000 hours.” “We distributed one million items.”

Those numbers communicate scale, and scale matters. But scale isn’t impact. A million of the wrong thing is still the wrong thing.

This is especially important for organizations trying to solve social problems. If an organization exists to reduce a problem, an endlessly increasing service number raises an uncomfortable question: When does more become evidence that the underlying problem isn’t getting better?

That doesn’t mean the organization failed. Demand can increase for reasons completely outside its control. Population grows. Economic conditions change. Awareness increases. Other services disappear. But leadership should at least ask the question.

Because there’s a dangerous organizational incentive hiding here. If your funding, recognition, staffing, and perceived importance all increase when the number of people needing your service increases, what incentive exists to make that number go down?

That isn’t an accusation. It’s a systems question. And systems questions are worth asking even when the answers make us uncomfortable.

Measure What You Are Trying to Change

So what should we measure?

Start with a deceptively simple question: What are we actually trying to change? Not what do we do? Those are different questions.

A food program distributes food. That’s what it does. But what is it trying to change? Food insecurity? Childhood hunger? A family’s short-term financial crisis? Access to nutritious food? Each answer leads to very different measurements.

A workforce program provides training. That’s what it does. But perhaps what it’s trying to change is someone’s ability to get and keep employment that supports their family. Now attendance isn’t the final measurement. It’s one measurement along the way.

At Trusted World, we distribute clothing, food, and personal-care items. Those are activities, and they’re important ones. But they aren’t the reason the system exists. The larger question is whether providing those resources at the right moment removes a barrier for someone who is already working with a professional trying to help them move forward.

That’s much harder to put on a dashboard. Harder doesn’t mean we shouldn’t try.

Measure the Path, Not Just the Destination

Organizations make another mistake: we look for one perfect outcome metric. Usually there isn’t one.

If your mission involves human beings, the final outcome may depend on dozens of things you don’t control.

A school counselor can get a student a pair of shoes. That doesn’t mean the shoes caused the student to graduate. Claiming that would be ridiculous. But it doesn’t mean the shoes had no measurable value, either.

We can measure:

Whether the request was identified
Whether the correct resource was available
How long it took to fulfill the request
Whether the student received it
Whether the immediate barrier was removed
Whether the professional helping that student could continue working on the larger issue

Those measurements describe the path. Sometimes understanding the path is more useful than pretending we can take credit for the destination.

Use Pairs of Metrics

One of the best defenses against a misleading metric is another metric.

If you measure speed, measure quality beside it.
If you measure volume, measure outcomes.
If you measure utilization, measure waiting.
If you measure dollars raised, measure donor retention.
If you measure volunteer hours, measure productive output.
If you measure orders completed, measure errors.

Why? Because almost every metric can be improved in a way that damages something else.

Faster isn’t better if quality collapses. Cheaper isn’t better if people wait twice as long. More isn’t better if the added volume produces worse outcomes. Efficiency isn’t better if it makes the experience unbearable for the person using the system.

A second measurement creates tension. And sometimes that tension tells you more than either number on its own.

Ask What the Number Cannot Tell You

Every metric has a blind spot. Good leaders learn to look for it.

If customer satisfaction is 95%, who are the 5%? If 98% of orders were completed correctly, what happened with the other 2%? If the average wait is three days, is everyone waiting about three days, or are most people waiting one day while a smaller group waits three weeks?

Averages can hide extremes. Totals can hide individuals. Percentages can hide small populations. Growth can hide inefficiency. Efficiency can hide poor experiences.

The question isn’t whether a metric is accurate. The question is: What disappears when I reduce this system to this number?

That question should probably sit beside every dashboard.

Sometimes You Need to Stop Measuring Something

This may be the hardest part.

Organizations accumulate metrics. Someone requested a number five years ago, so somebody still produces it every month. Nobody remembers why. Nobody uses it to make a decision. But an employee still spends two hours compiling it. Another employee checks it. Someone puts it into a spreadsheet. Then it gets copied into a report.

That’s measurement creating its own hidden cost.

Data collection isn’t free. Every field someone enters takes time. Every report takes time. Every dashboard someone maintains takes time. Every metric someone reviews consumes attention.

So measurements should have to earn their place. For every recurring metric, I’d ask: What decision does this help us make?

If nobody can answer that question, why are we still measuring it?

The Final Hidden Cost

Over this series, we’ve looked at costs that rarely appear on a financial statement: the cost of friction, waiting, complexity, poor data, duplicate work, and good intentions. Each one can quietly consume money, time, capacity, and opportunity.

But measuring the wrong things may be the most dangerous hidden cost of all. The others create problems. This one can hide them.

An organization can have enormous friction and report record activity. It can make people wait and report increased volume. It can build unnecessary complexity and report more programs. It can duplicate work and report more hours. It can run on poor data and still produce beautiful dashboards. It can act with the best intentions in the world and never notice that those intentions aren’t producing the result it hoped for.

And every number on the dashboard can be technically correct.

The numbers aren’t necessarily lying. They may simply be answering the wrong questions.

Maybe “What Gets Measured Gets Managed” Isn’t Enough

So I’d change the old saying:

What gets measured gets attention.
What gets attention influences behavior.
What influences behavior eventually shapes the organization.

That means choosing what to measure isn’t an administrative decision. It’s a leadership decision.

Before adding another KPI, field, report, or dashboard, ask:

Why are we measuring this?
What behavior could this measurement encourage?
What could improve while this number gets worse?
What could get worse while this number improves?
What does this number hide?
What other measurement should sit beside it?

And most importantly:

If this number improves, does that mean we’re getting better at what we actually exist to do?

That last question is the one I keep coming back to. Because the goal isn’t to have better numbers. The goal is to build a better organization.

And those aren’t always the same thing.