The Hidden Assumptions That Decide Whether Your Strategy Works

Jun 01, 2026

11 min read

1 views

87%

The real problem is not planning, it is believing your plan

Most strategies fail for a reason that is embarrassingly ordinary: they depend on things nobody bothered to name. A program is launched, a policy is rolled out, a team commits to a new process, and everyone acts as if the chain from action to outcome is obvious. Then reality intervenes. People do not behave as expected, incentives shift, context changes, and the elegant design turns out to have been built on invisible guesses.

That is the core tension behind any serious attempt to understand change. A plan is never just a plan. It is a bundle of assumptions disguised as certainty. The better the plan sounds, the more dangerous this disguise can become, because confidence tends to hide the weak joints.

This is why many initiatives are not defeated by bad execution alone. They are defeated earlier, at the level of interpretation. The team thought it knew what would happen. It did not. The gap was not simply between intention and outcome, but between assumed logic and lived reality.

The hardest part of making change work is not choosing actions. It is making the assumptions behind those actions visible, testable, and revisable.

That idea sounds simple. In practice, it changes everything.

Why logic models fail when they are treated like blueprints

People often approach a theory of change or evaluation framework as though it were a map of the world. But a map is not the territory, and a model is not a machine. A model is a story about how change might happen, told in a way that can be inspected, challenged, and improved.

This distinction matters because many organizations confuse explanation with prediction. They build a neat sequence: activities lead to outputs, outputs lead to outcomes, outcomes lead to impact. The sequence feels reassuring, but it is only as good as the assumptions holding it together. If the assumption that participants will show up is false, the rest of the chain weakens. If the assumption that a policy will be adopted by front-line staff is false, the downstream outcomes never materialize.

A useful analogy is architecture. A blueprint shows beams, rooms, and load paths. But the building stays up because of assumptions about materials, soil, weather, and use. Ignore the soil and the most beautiful design can crack. Social change works the same way. The visible design matters, but the hidden conditions determine whether the structure holds.

That is why theory-based evaluation is most valuable when it refuses to treat observed outcomes as the whole story. Results are important, but they are not self-explanatory. When an intervention succeeds, it is tempting to call the strategy brilliant. When it fails, it is tempting to call it flawed. Yet both judgments may be premature if they ignore context and assumption. The real question is not merely, did it work? The deeper question is, under what conditions, through what mechanism, and on the basis of which beliefs about people and systems?

That shift changes the purpose of evaluation. Evaluation is no longer just an audit of success or failure. It becomes a disciplined way of learning how reality differs from our mental model.

Assumptions are not footnotes, they are the engine of change

Every theory of change contains assumptions, whether written or not. Some are obvious, such as the belief that funding will be available. Others are subtler, such as the belief that people will trust the messenger, that staff will have time to apply new skills, or that beneficiaries will interpret an offer as intended.

The biggest mistake is to treat assumptions as minor caveats. They are not caveats. They are the load-bearing beams of the whole design.

Think of a public health campaign meant to increase vaccination rates. The logic may say: provide information, reduce hesitancy, increase uptake. But beneath that chain lie assumptions about trust in institutions, access to clinics, transport, language, prior experiences, and peer influence. If the message is persuasive but the clinic is inaccessible, the campaign underperforms. If access is easy but trust is broken, the same thing happens. In other words, the intervention does not fail in a vacuum. It fails at the point where an assumption collides with reality.

This is why assumption work is not administrative housekeeping. It is strategic intelligence.

A strong assumption practice does three things:

Names the belief clearly, rather than hiding it in vague optimism.
Tests the belief against evidence, experience, or pilot data.
Monitors drift, because assumptions can become false over time even if they were once true.

That third point is easy to miss. Assumptions are not static. A community can gain trust or lose it. A labor market can tighten. A policy environment can shift. What was true at launch may be false six months later. Many organizations evaluate outcomes without rechecking the beliefs that made those outcomes plausible in the first place.

This is where theory-based evaluation becomes especially powerful. It does not just ask whether change occurred. It asks whether the presumed causal story survived contact with the world.

Good strategy is less about having the right answer upfront and more about discovering, quickly and honestly, which parts of your answer are wrong.

A better mental model: change as a chain of bets

The most useful way to understand assumptions is not as abstract beliefs but as bets. Every intervention is a sequence of bets about how the world behaves. If you fund training, you are betting that training will improve capability. If you improve capability, you are betting that people will use it. If people use it, you are betting that the environment will reward the new behavior.

This chain of bets is powerful because it makes uncertainty concrete. It also reveals a subtle truth: the problem is rarely one giant assumption. It is usually a series of smaller ones, any one of which can break the chain.

Imagine a nonprofit introducing a new case management system. The logic might be:

Staff will adopt the system.
The system will reduce administrative burden.
Reduced burden will free time for client contact.
More client contact will improve service quality.
Better service quality will improve outcomes.

Each step looks reasonable. But each hides assumptions. Staff must see the system as useful, not punitive. The system must actually be intuitive. Managers must allow the saved time to be reallocated rather than absorbed by new tasks. Clients must benefit from the added contact. The system works only if these smaller bets pay off.

This is why many initiatives are overconfident at the design stage and underinformed during implementation. They assume the chain is linear when in fact it is conditional. Real change behaves more like a suspension bridge than a straight road. The bridge holds because tension is balanced across many cables. Remove one cable, and the whole structure changes shape.

That picture suggests a practical discipline: map not only what must happen, but what must already be true for each step to make sense.

Ask:

What has to be true for this activity to matter?
What has to be true for the output to be used?
What has to be true for the outcome to persist?
What would make this belief false?

When teams ask these questions honestly, the theory of change stops being a poster and becomes a learning tool.

The most useful evaluation question is not “Did it work?”

The question “Did it work?” is attractive because it sounds decisive. It is also misleadingly simple. In complex settings, a better question is, What did we believe would happen, what actually happened, and where did the difference come from?

That difference matters because it can reveal several distinct lessons.

Sometimes the intervention idea was sound, but the context was wrong. A workforce program may succeed in one region and fail in another because local employers differ. Sometimes the logic was right, but the implementation was weak. A school attendance initiative may depend on teachers using the process faithfully, but that never fully occurred. Sometimes the intervention achieved the intended immediate effects, but the final outcome was shaped by a larger system outside its control.

This is why theory-based evaluation is so useful in public policy, philanthropy, and organizational change. It lets you distinguish between:

Theory failure: the causal story itself was wrong.
Implementation failure: the theory was plausible, but execution broke the chain.
Context failure: the theory assumed conditions that were not present.
Scale failure: the theory worked in a pilot, but the assumptions did not survive expansion.

That taxonomy is more than academic. It prevents two equally bad mistakes: abandoning a promising idea too quickly, and protecting a bad idea just because it had decent intentions.

A small example makes this concrete. Suppose a city launches a text-message reminder system to reduce missed appointments. If no-shows drop, is the intervention responsible? Maybe. But perhaps the effect came because the text made the system feel more personal, or because reminders helped only certain groups, or because the appointment slots were easier to reach during the pilot period. Without a theory of change, you see only a number. With one, you begin to understand mechanism, boundary, and fragility.

That is the difference between being satisfied with a result and being able to learn from it.

How to work with assumptions without getting trapped by them

A common fear is that once assumptions are exposed, confidence will collapse and action will stall. The opposite is usually true. Hidden assumptions create brittle confidence. Visible assumptions create adaptable action.

The goal is not to eliminate assumptions. That is impossible. The goal is to manage them deliberately.

Here is a practical framework for doing that:

1. Separate the claim from the hope

Teams often write theories of change that blend evidence and aspiration. Try to split them apart. What do you genuinely know from data, prior experience, or credible analogies? What are you hoping will happen but do not yet know?

This separation is clarifying because it keeps wishful thinking from wearing the costume of evidence.

2. Identify the weakest link, not just the most visible one

People tend to focus on the most dramatic assumption, such as budget or staffing. But the weakest link is often more behavioral: trust, motivation, legitimacy, timing, or local fit. The question is not which assumption sounds important, but which one would most quickly collapse the chain if false.

3. Convert assumptions into tests

An assumption that cannot be tested is just a belief with nicer formatting. Turn assumptions into small experiments, pilots, interviews, observations, or process measures. If you believe staff will use a new tool, do not wait for annual results. Look for early signs of uptake, friction, and misuse.

4. Revisit assumptions as conditions change

Assumptions age. Build in scheduled moments to ask whether the context that supported your theory is still present. This is especially important in fast-changing environments, where a once-valid theory can quietly expire.

5. Treat disagreement as diagnostic data

When people disagree with a theory of change, do not rush to compromise. Disagreement may reveal that different stakeholders live in different causal worlds. That insight is gold. It shows where hidden assumptions diverge and where implementation may later fracture.

This approach makes evaluation more humane as well as more rigorous. It acknowledges that people act from partial models, not omniscience. That is not a failure of intelligence. It is a feature of complex systems.

Key Takeaways

Name the assumptions behind every plan. If they are not explicit, they are already running the strategy from underground.
Treat theories of change as hypotheses, not guarantees. Their job is to guide learning, not to decorate certainty.
Test the weakest link early. The most fragile assumption often sits in behavior, trust, or context, not in the obvious operational details.
Use results to refine the causal story, not just to judge success. Ask what changed, why it changed, and which beliefs survived.
Revisit assumptions over time. A theory that fit last quarter may be wrong this quarter if the environment has shifted.

The deeper payoff: humility that improves performance

There is a reason assumption work feels uncomfortable. It exposes the fact that our plans depend on a world we do not fully control. But that discomfort is productive. It prevents organizations from mistaking narrative elegance for causal truth.

The deepest value of theory-based evaluation is not bureaucratic rigor. It is epistemic humility with operational force. You become more honest about what you know, more alert to what you do not know, and more able to adapt when the world refuses to cooperate with your model.

That is a better definition of intelligence than certainty. Certainty says, “I know what will happen.” Intelligence says, “Here is the story I am betting on, here are the assumptions inside it, and here is how I will know when the story needs revision.”

In the end, the most reliable strategies are not the ones with the fewest assumptions. They are the ones that know where their assumptions live.

And that reframes the entire game. Success is not proof that your theory was perfect. Failure is not proof that your intentions were weak. Both are information about the relationship between your model and the world. The real craft lies in learning to see that relationship clearly enough to improve it.

Once you start thinking this way, every plan becomes a more interesting question: not just what are we doing, but what must be true for this to work? The moment you ask that, you stop managing activities and start managing reality.