Your Theory of Change Isn’t Enough

Here’s something I’ve been sitting with lately, and honestly, something I see play out in my work more often than I’d like to admit.

A lot of nonprofits have invested real money into theories of change, logic models, and strategic frameworks. And those documents can be genuinely valuable. A good theory of change can sharpen your thinking, align your team, and give funders a clear picture of how you believe change happens. I’m not here to dismiss them. But somewhere along the way, the sector got really good at producing the deliverable without building the infrastructure to actually bring it to life.

Here’s the pattern I keep running into: a beautifully crafted theory of change sitting in a strategic plan, maybe on a website, probably in every grant application submitted in the last three years, while the data systems needed to actually measure that change just aren’t there yet. No consistent data collection practices. No centralized storage. No clear process for pulling it all together when someone asks hard questions about impact. The document exists. The capacity to live it out doesn’t.

And honestly, that’s not a criticism of any one organization. It’s a reflection of how the sector has been resourced for a long time. Funders love funding planning documents. They love logic models and frameworks and visuals that show a clean line from inputs to outcomes. What they fund far less often is the operational infrastructure that makes any of that measurable. So nonprofits end up doing the best they can with what they have, producing the documents that open doors without always having the systems to back them up.

I was recently brought on to conduct a retrospective evaluation for a nonprofit, meaning I was hired to look back at their programs and services and help them understand their impact over time. It’s exactly the kind of work that should be straightforward if an organization has been capturing data consistently. What I ran into instead was a struggle to get access to anything meaningful. Not because the people there weren’t smart or committed. They are. But the data infrastructure just wasn’t there to support the ask. And this organization had invested in a theory of change. The document existed. The systems to measure it didn’t.

So here’s the gentle nudge I want to offer: if someone hired an evaluator to review your programs tomorrow, what could you actually hand them right now?

If the answer feels uncomfortable, that’s useful information. Not a reason to spiral, but a reason to reprioritize. You don’t need a big system overhaul to start making progress. Pick one program. Define what success looks like in plain language. Figure out how you’re going to capture that consistently. Build from there. Small, intentional steps toward a data practice that actually supports the work you’re already doing.

A theory of change tells a compelling story about the future. Data infrastructure is how you prove the story is true. Both matter. But one of them tends to get a lot more attention than it deserves.

If any of this resonated and you’re not sure where to start, I’d love to connect. Request a free discovery call here.