Theory of Change: Mapping Real Impact and Strategic Action

Lena: Hey everyone, glad you're joining us today. You know, I was looking over some project plans recently, and it hit me—most of us are walking around with these invisible maps in our heads. We have this big goal, right? We want to change the world, or at least our corner of it. But if you actually ask someone how their specific actions lead to that big change, things get blurry fast. It's like we’re trying to build a skyscraper while only looking at a drawing of the front door.

Miles: That is such a classic trap. We get so caught up in the "doing"—the workshops, the meetings, the daily grind—that we stop questioning if those activities actually add up to the result we want . It's what some experts call having a "diagram of activity" instead of a true Theory of Change. You might have a logic model buried in a grant application somewhere, but let’s be honest, those are often just there to make funders happy. They show what you’re doing, but they rarely explain why it matters or what happens if the world doesn't behave exactly like your spreadsheet says it will .

Lena: Exactly! And that’s why we’re diving deep into Theory of Change, or ToC, today. This isn't just some academic exercise for evaluators. It’s about building mastery over how change actually happens in complex systems. It’s the difference between just working hard and actually being strategic. According to the Hivos guidelines, ToC is a "thinking and action approach" to navigate the sheer unpredictability of social change .

Miles: I love that phrasing—navigating unpredictability. Because let’s face it, social change isn't a straight line. It’s messy. It’s full of feedback loops and power dynamics that can knock you off course in a heartbeat. A solid ToC is like a living compass. It helps you zoom out to see the big picture and zoom in to make sure your day-to-day tactics are actually hitting the mark .

Lena: So, for everyone listening who wants to move beyond "business as usual," we’re going to break down how to build a robust ToC from the ground up. We’ll look at why your logic model might be telling the wrong story, how to surface those hidden assumptions that usually sink projects, and how to actually use this as a management tool, not just a document on a shelf .

Miles: And we’re going to get into the "dark logic" too—the stuff no one likes to talk about, like how well-intentioned programs can actually cause harm if we aren't careful . It’s going to be a rigorous look at what it takes to be a master of change. So, let’s start by looking at the foundation—the difference between the "what" and the "why."

Lena: So Miles, you mentioned that logic models often fall short. But I feel like I see them everywhere. For a lot of people, the logic model is the plan. Why isn't that enough?

Miles: It’s a great question, and it’s one of the biggest points of confusion. Think of a logic model as a snapshot—a one-page description that shows the connection between your resources, your activities, and your intended outcomes . It answers the "What." As in, "We plan to do X, which will give Y result" . It’s great for monitoring progress and giving an at-a-glance view of a program.

Lena: Okay, so it’s the "What." Then ToC is the "How" and the "Why"?

Miles: Spot on. A Theory of Change is more like a narrative or a comprehensive map. It doesn't just list components; it describes the pathways to change . It completes the sentence: "If we do X, then Y will change because..." . That "because" is the secret sauce. It’s the underlying research, the hypotheses, and the causal mechanisms that explain why you think your actions will actually lead to a shift in the real world .

Lena: I see. So a logic model might show that "Staff + Funding" leads to "Housing Navigation," which leads to "Placements." But it doesn't explain why a young person would trust that navigator in the first place, or what happens if the local rental market suddenly spikes .

Miles: Precisely. Logic models tend to be very linear. They assume that if you put the right ingredients in, the cake will always come out of the oven perfectly . But social justice work is more like raising a child than following a recipe. The outcomes are emergent. Context is everything. The same input can produce totally different results depending on the environment .

Lena: That really highlights the risk of "partial explanations." If we only look at our own program as the driver of change, we become blind to the active forces—like policy constraints or power imbalances—that are actually shaping whether our logic holds up .

Miles: And that’s the power of ToC thinking. It forces you to acknowledge that you’re working within a complex system . Hivos defines this as a system where elements are interconnected and interdependent, where interactions lead to "emergent properties," and where feedback loops can either promote or inhibit change . If you aren't mapping those loops, you're basically flying blind.

Lena: So, ToC is the explanatory framework that makes the logic model "honest" . It provides the context that the logic model leaves out. It sounds like mastery here requires being able to hold both—the clear, simple summary of the logic model and the deep, nuanced explanation of the ToC .

Miles: That's exactly right. And to get to that level of mastery, you have to start by being incredibly precise about what you actually want to achieve. You have to move past the "mega-outcomes" that sound good in a brochure but don't actually give you a direction to march in .

Lena: You mentioned "mega-outcomes," and I think I know what you mean—those big, vague goals like "improving family functioning" or "empowering youth." They sound great, but how do you actually measure "empowerment"?

Miles: You can't, at least not directly. And that’s the first hurdle in building a real ToC. You have to "unpack" those big ideas into specific, tangible components . Mastery in ToC starts with what's called "backwards mapping" . Instead of starting with what you're doing today, you start with the long-term goal—the "dream"—and you work your way back to the present .

Lena: I love that—starting with the dream. Hivos suggests aiming for a change that’s "challenging and hard, stretching but just about reachable in 10 to 20 years" . It’s about having your "head in the clouds but your feet on the ground" .

Miles: Right! And the key question you ask at every step is: "What are the necessary and sufficient preconditions for this outcome to happen?" . It’s a very disciplined way of thinking. You’re essentially identifying the building blocks or the "ingredients" that must exist before your ultimate goal can be realized .

Lena: So, if our goal is "Long-term employment at a livable wage for domestic violence survivors," we don't just jump to "Start a job training program." We ask: what has to be true right before they get that job?

Miles: Exactly. Maybe they need "Marketable skills in nontraditional areas" and "Appropriate workplace behavior" and "Regular childcare" . Those are the penultimate outcomes. Then you take another step back: what do they need to get those skills? Maybe "Peer-to-peer counseling" or "Internships" . You keep walking backwards until you reach the very first thing that needs to happen—your "entry points" .

Lena: This really flips the usual planning process on its head. Most of the time, we start with "We have this funding for a training program, so let’s do it." Backwards mapping forces you to justify why that training program is even the right move .

Miles: And it helps you weed out the "nice-to-haves." If an outcome isn't absolutely necessary to reach the goal, it doesn't belong on the map . This logic keeps the pathway focused and plausible. You’re looking for that "causal chain" where each achievement sets the stage for the next .

Lena: I'm also seeing how this helps manage expectations. When you map it all out, you realize just how much work has to happen before you reach that big 20-year goal. It’s an "expectation management tool" because it shows the gap between the resources you have and the complexity of the change you're after .

Miles: It really is. And as you're drawing these pathways—which, by the way, shouldn't just be boxes and arrows; they should show inter-relations and feedback loops—you start to run into the "invisible" parts of the map . These are the assumptions we’re making about why one thing leads to another. And that’s where things get really interesting—and often where projects go to die if they aren't careful.

Lena: We keep mentioning assumptions, and honestly, it feels like the most "ToC" part of the whole process. It’s about making the implicit explicit, right?

Miles: That is the core of it. We all have these deep drivers of behavior—beliefs about life, human nature, and society—that shape how we see the world . They’re like the water a fish swims in; the fish doesn't even know it’s there . In a ToC, an assumption is just a belief that something is true or will happen, even if we haven't checked it .

Lena: So, "If we provide training, then people will get jobs." The assumption there might be that there are actually jobs available, or that employers are willing to hire this specific group .

Miles: Exactly. And if those assumptions are wrong, your whole project is built on sand. Hivos breaks these down into a few types. You have assumptions about the context—the problem, people’s needs, and the motivations of other actors. Then you have assumptions about the pathways—the actual cause-effect mechanisms you're relying on .

Lena: I love the idea of "checking the causal links." Just because you have arrows in your logic model doesn't mean they're causal . It might just be a relational link, like "Having resources leads to using resources." A true ToC explains the mechanism—the actual "how" of how resources lead to an activity that leads to a change .

Miles: Right, like Miles's bread example. Flour, water, and yeast don't just become bread. You have to mix, knead, and bake . The ToC explains why kneading creates that elastic dough. In social change, we often assume that "Increased knowledge" will lead to "Behavior change," but is that an assumption or do we have evidence to back it up? .

Lena: And that’s the key. You have to ask: "Did we check our assumptions? Is there evidence?" . This is where mastery comes in—it’s not just naming assumptions, it’s doing a risk analysis on them .

Miles: Hivos has this great matrix for that. You look at the "likelihood of the assumption being invalid" versus the "seriousness of the consequences" if it is . If something is very likely to be wrong and it would ruin your project, that’s a "watch out" area. You either need to redesign your intervention or put that assumption at the top of your learning agenda .

Lena: It’s about being honest about where you're taking a "leap of faith" . And being explicit about those leaps actually increases your credibility with partners and funders. It shows you’ve thought through the risks .

Miles: It also helps a group build consensus. You might find that everyone in the room has a slightly different idea of how change happens. One person thinks it’s through "political contestation," another thinks it’s "economic growth," and another thinks it’s "individual empowerment" . If you don't surface those worldview differences, you’re going to have a hard time working together .

Lena: So, surfacing assumptions isn't just about being "rigorous." It’s about team effectiveness. It’s about alignment . But even with all the assumptions surfaced, there’s still another layer we have to peel back—the power dynamics that are always at play.

Miles: You know, one of the biggest critiques of simplified logic models is that they treat the world as a neutral playing field. Like, if we just provide the service, everyone will benefit equally. But we know that’s not true.

Lena: Absolutely. Power is everywhere. Hivos is really clear about this: unequal power relations at every level—from the household to the international stage—are what cause poverty and injustice in the first place . If your ToC doesn't have a power lens, it’s basically ignoring the engine of the whole system.

Miles: Right. And power isn't just "power over"—the negative kind, like repression or coercion. It’s also "power with," which is collective strength and solidarity. It’s "power to," the potential of every person to shape their world. And "power within," which is self-worth and dignity . A master of ToC looks for all of these.

Lena: I think that "Power Cube" framework is so helpful for this. It asks you to look at the spaces where power is exercised—is it "closed" behind doors, "invited" where we get a seat at the table, or "claimed" by the people themselves? . And the forms of power—is it "visible" like laws, "hidden" like who gets to set the agenda, or "invisible" like the social norms that make people accept the status quo? .

Miles: And gender is a huge part of that "invisible" power. We all have gender biases—men and women alike. We internalize these ideas about what men and women "should" do, and those biases creep right into our program designs .

Lena: Exactly. If we aren't careful, our "strategic choices" will just reinforce the existing inequalities. A fully integrated gender analysis in a ToC means asking: "Does this desired change actually benefit women? To which strategic gender interests does it contribute?" . It’s about looking at the division of labor, access to resources, and who actually gets to make decisions .

Miles: It’s also about realizing that "women" or "men" aren't monolithic groups. We have to be specific—which women? Which men? . This is where the "Rich Picture" tool comes in so handy during the situation analysis. You draw the system, the stakeholders, the conflicts, the resources—and then you overlay that power and gender lens to see what's really going on .

Lena: It strikes me that this kind of analysis can be a bit confrontational. It might uncover "structural inconsistencies" in your own organization—like how power is exercised internally versus what you preach to the world .

Miles: It definitely can be. But that’s where the real learning happens. ToC mastery isn't just about having a pretty diagram; it’s about having the "new eyes" to see the systems you’re part of . And that leads us to something even deeper—the "dark logic" and the unintended consequences that we often prefer to ignore.

Lena: We’ve been talking about the "positive" pathways—the things we hope will happen. But Miles, you mentioned "dark logic" earlier, and that really stuck with me. What is that, exactly?

Miles: It’s a concept that basically says: for every pathway you map toward a good result, there’s a parallel pathway where things could go wrong or even cause harm . It’s the "negative logic." Mastery means mapping those before the program starts, so you can build in protections .

Lena: So, it’s not just "unintended consequences" that we discover later. It’s anticipating them. Like, if a case management structures built around compliance, attendance requirements, documentation, and regular check-ins are too rigid, it might actually drive away the very people who need it most because it feels too much like the systems that have already failed them .

Miles: Exactly. Or take a data system meant to coordinate services. If the privacy protections aren't rock-solid, you might be exposing vulnerable people to law enforcement risks they didn't sign up for . The "dark logic" model asks: "For whom does this program work, and at whose expense?" .

Lena: It reminds me of the "housing coalition" example. If they only focus on placements, they might ignore the fact that some landlords might treat tenants differently once the caseworker stops checking in . If that’s not in the ToC, it’s an invisible risk.

Miles: Right. And these patterns aren't usually unpredictable. They're often predicted by the community members themselves, well in advance . The question is whether we’re actually listening to them. This is why a ToC that’s only built by "experts" in a room is so dangerous.

Lena: This is where the "Theory of Action" comes in—the specific part of the ToC that focuses on what your project is doing . You have to zoom in on your "Sphere of Control" (what you do) and your "Sphere of Influence" (how others react) . If you aren't accounting for how people might push back or how the system might react to your intervention, your "Theory of Action" is incomplete.

Miles: And that’s where "reverse logic analysis" is so powerful. You ask: "Are there other pathways to this same outcome that we haven't considered?" . If research shows that just giving people money—vouchers—works better than your case management model, you have to grapple with that. You don't have to abandon your approach, but you have to be honest about why you're choosing yours .

Lena: It’s about moving from "attribution"—proving we caused the change—to "contribution"—showing how we’re one part of a bigger shift . It takes the ego out of it and puts the focus back on the result.

Miles: Exactly. And to get that honest view, you have to bring in the people who actually live the problem. You can't master change if you're only looking at it from the outside.

Lena: We've talked about power, and we've talked about dark logic. It seems like the only way to navigate both is to make the ToC process truly participatory. But that’s easier said than done, right?

Miles: It really is. A lot of times, "participation" is just a checkbox. But in a real ToC process, the perspectives of local stakeholders are a condition for a grounded theory . They have the knowledge of the context and the local dynamics that no outside expert can replicate .

Lena: Hivos calls this "grounding the conversation in real and specific circumstances" . If the people who are supposed to benefit aren't involved in the design, how do we even know our "desired change" is something they actually want? .

Miles: Exactly. And it’s not just about asking them for input. It’s about them being co-authors. There’s this great example of a community-based participatory evaluation where the community members didn't just affirm the "expert" logic model—they reshaped it entirely . They restructured the working groups to reflect how they understood the problem, not how the researchers categorized it .

Lena: That’s a huge shift. It means being willing to let go of your own "mega-outcome" and listen to what success looks like on their terms . It might take longer, but the result is a theory that’s actually owned and used .

Miles: And that ownership is what makes the ToC a "living" product. It’s a temporary snapshot, a reflection of the thinking at a specific moment . As the project moves on, as the context changes, the ToC has to be revisited and adapted .

Lena: That makes sense. Hivos says a review can be triggered by context changes, stakeholder shifts, or just when an indicator shows a key assumption might not be valid . It’s about "adaptive planning and management" .

Miles: It’s also about having a "learning agenda." Instead of just monitoring for accountability—did we do the activities?—you monitor for learning . You use your critical assumptions as entry points for research . You're constantly checking: "Is our theory actually working in reality?" .

Lena: I love that. It turns the whole project into an action-learning cycle . You're building an evidence base as you go. And that’s really the mark of mastery—realizing that your ToC is never "finished." It’s just the best hypothesis you have right now.

Miles: Exactly. So, let’s wrap this up with a practical playbook. How do you actually sit down and start doing this tomorrow?

Lena: Okay Miles, we’ve covered a lot of ground—from the big-picture systems thinking to the nitty-gritty of dark logic. If someone is listening and thinking, "I want to overhaul my project’s Theory of Change," where do they actually start?

Miles: Step one is always about purpose. Ask: "Why are we doing this? What do we want to be different for the team and our partners or allies as a result?" . Don't just do it because a donor asked. Do it because you want to be more effective. Decide if you're building a high-level "System Map" or a context-specific "Theory of Action" .

Lena: And once the purpose is clear, you go to the "dream." Describe the desired change, but be specific. Who is it for? Why is it desirable? . Use tools like the "Time Machine" or "Celebrating Success" to help people visualize a positive future .

Miles: Then, dive into the situation analysis. Draw that "Rich Picture." Map the stakeholders, the power dynamics, and the gender inequalities . Don't just look for problems; look for "leverage points" and opportunities for change .

Lena: Step four is identifying "Domains of Change." You can't do everything. Pick three to five broad areas where change is essential for your goal to be possible . Then, prioritize. Where does Hivos or your organization have the "unique contribution"? Where can you realistically make a difference in three to five years? .

Miles: This is where you start mapping the pathways. Work backwards from your long-term goal. Ask: "What are the necessary and sufficient preconditions?" . Formulate these as results—changed behaviors or conditions—not activities . Instead of "Train teachers," say "Teachers use inclusive methods in the classroom" .

Lena: And as you're mapping, surface those assumptions. Write them down! Use that risk matrix to identify the ones that could sink you . If you find a "leap of faith," turn it into a learning question .

Miles: Don't forget to operationalize your indicators. For every precondition, ask: "Who or what will change? By how much? And by when?" . This is the blueprint for your evaluation. It makes your theory testable .

Lena: Finally, build your "Theory of Action." Match each outcome in your pathway to a specific intervention . This is where you get tactical. And remember to keep it a "living" document. Schedule regular "zoom-in and zoom-out" sessions to review the ToC and adjust based on what you're seeing on the ground .

Miles: And throughout all of this, use visualization! Drawing together stimulates critical thinking in a way that just talking doesn't . It helps surface those hidden differences in perception. It doesn't have to be pretty; it just has to be meaningful to the group .

Lena: This really is a rigorous process, but you can see how it builds that "shared understanding" that’s so critical for success . It moves the whole team from being "implementers" to being "strategic thinkers."

Miles: That's the goal. Mastery isn't about having all the answers; it’s about having the right framework to keep asking the tough questions.

Lena: You know Miles, as we bring this home, I’m thinking back to that Marcel Proust quote at the beginning of the Hivos guide: "The voyage of discovery is not in seeking new landscapes but in having new eyes" .

Miles: It’s so fitting. Building a Theory of Change isn't about inventing a whole new world. It’s about finally seeing the one we’re actually operating in. It’s about taking those invisible maps we carry around and putting them out on the table where we can challenge them, refine them, and actually use them to find our way .

Lena: Right. It’s moving away from the safety of the "diagram of activity" and stepping into the complexity of real social transformation . It takes courage to admit that our logic might be partial, or that our assumptions might be wrong. But that’s where the real power is .

Miles: It really is. And to everyone listening, I hope this doesn't feel like just another task for your to-do list. I hope it feels like a tool for liberation—liberation from ineffective programs and from the frustration of working hard without seeing the results you dream of.

Lena: Mastery in Theory of Change is an ongoing process. It’s an "action-learning cycle" that never really ends . So, as you wrap up this episode, I’d encourage you to pick just one project you’re working on. Take a look at its logic model or its plan. What’s one assumption you’re making that you’ve never actually checked? What’s one power dynamic that might be shaping your results from the shadows?

Miles: Just starting with that one question can change everything. It’s the first step toward those "new eyes."

Lena: Absolutely. Well, Miles, this has been a deep dive, and I’ve learned a ton. Thank you for walking through this with me.

Miles: It’s been a pleasure. And thanks to all of you for listening and for the work you’re doing out there.

Lena: We really appreciate your time and your commitment to doing this work with rigor and heart. Take some time to reflect on what we’ve talked about today, and we’ll see you in the next landscape.

Miles: Catch you later.