Organizations sometimes measure what is easiest to count, rather than what is most meaningful. It’s a natural habit — attendance sheets and delivery logs are simple to produce. But they answer a narrower question than most funders, boards and communities actually want answered.
Four different questions, often confused for one
Consider four statements about the same program:
- “We delivered 20 workshops.” — an activity statement.
- “400 people attended.” — an output statement.
- “80% of participants demonstrated increased knowledge.” — a learning outcome.
- “Participating organizations implemented accessibility improvements afterward.” — evidence of organizational change.
Each is true, and each answers a different question. A report full of the first two can look impressive while saying almost nothing about whether the program actually worked.
Design evaluation early, not at the end
The most common evaluation mistake isn’t a bad survey — it’s timing. Evaluation designed after a program has already run can only measure what happened to be recorded along the way. Evaluation designed alongside a program, from a clear theory of change and a small set of real indicators, can actually tell you what changed and for whom.
Measurement should support improvement — not arrive as a report card after the decisions are already made.
A short set of questions worth asking
Before a program launches, it’s worth deciding how you’ll answer these, even briefly:
- Relevance — does this address a demonstrated need?
- Reach — who participated, and just as importantly, who didn’t?
- Implementation — was it delivered as intended?
- Outcomes — what actually changed?
- Equity — were outcomes experienced equitably across different groups?
Not every program needs a formal answer to all five. But naming them at the start makes it far more likely the program collects the right information along the way, instead of discovering the gap at the final report.
Related
See how Vantercor approaches Research, Evaluation & Systems Innovation →