The Problem with Measuring What's Easy to Count

There's a predictable pattern in how nonprofits talk about their impact. Meals served. Training sessions delivered. Individuals reached. Hours of programming provided. Calls answered. Beds filled.

These numbers are real. They represent genuine work. And they are, in nearly every meaningful sense, not measures of impact.

They're measures of activity. And the difference matters more than most organizations realize.

Why outputs dominate

Activity-level data has a lot going for it. It's easy to collect. It's straightforward to verify. It tells a clean, concrete story — this is what we did, this is the scale at which we did it — that feels satisfying to report and comfortable to receive.

Outcomes, by contrast, are harder. They take longer to observe. They require more thoughtful measurement tools. They're more likely to surface ambiguity, partial progress, or results that are difficult to attribute cleanly to any single intervention.

So organizations drift toward outputs. Not because they don't care about outcomes, but because outputs are manageable and outcomes are complicated. Over time, what gets measured starts to feel like what matters — and the harder questions quietly fall away.

The ceiling outputs create

Here's the practical problem: when organizations report primarily on activity, they lose the ability to make a compelling case for their actual value.

A donor or funder looking at 'served 1,200 individuals' cannot tell whether any of those individuals are better off. They can't tell whether the program is working well, working partially, or simply producing volume. They're being asked to fund a number, not an outcome.

And internally, activity data doesn't help staff make better decisions. Knowing that 400 people attended a workshop doesn't tell you whether the workshop changed anything. It doesn't tell you what to keep, what to adjust, or what to stop.

Activity metrics create a ceiling. They answer the question 'how much?' while leaving the more important question — 'so what?' — unanswered.

The resistance to outcome measurement

When organizations push back on outcome measurement, the objections are usually genuine. Outcomes are influenced by factors outside the program's control. Change takes time, and reporting cycles are short. Collecting outcome data requires participant cooperation and staff capacity. And sometimes the most important outcomes — a shift in how someone sees themselves, a restored sense of safety, the slow accumulation of trust — don't fit neatly into a survey.

All of that is true. It's also not a reason to stop at outputs.

It's a reason to think carefully about what outcomes are realistic to measure, at what point in time, with what level of precision. It's a reason to acknowledge complexity rather than avoid it. And it's an opportunity to develop appropriately modest evaluation approaches—that claim what the evidence supports, rather than either overclaiming or retreating to activity counts.

Getting comfortable with harder measures

Outcome measurement doesn't have to be elaborate to be meaningful. A well-designed pre/post survey. Structured staff observations. Periodic interviews with a small sample of participants. A few carefully chosen indicators that connect directly to the change the program is trying to produce.

The key is choosing measures that reflect what success actually looks like for the people being served — not just what's convenient to track, and not just what a particular funder asked for once.

Organizations that do this work tend to find something unexpected: that their outcomes data, even when it's imperfect and partial, tells a richer and more credible story than their outputs ever could. Because it's honest about what the work is trying to do, and honest about what the evidence shows.

That's the kind of story that builds trust over time. And it starts with being willing to measure what's hard—not just what's easy.