Why Linear Planning Fails in Complex Systems
- 5 days ago
- 6 min read
A plan gets approved.
Two years later, the problem it was designed to solve is still there. The project report is complete. The indicators were met. But on the ground, not much has changed.
This is not rare. It is, in fact, quite common. The question worth asking is why.
The Way We Usually Plan
Linear thinking is not a mistake. It is how most of us were taught to think: find the cause, remove it, observe the result. It works in bounded, stable systems, like a machine with a faulty part or a supply chain with a broken link.
Development work rarely looks like that. But the pressure to show results and justify budgets means understanding gets compressed into a few interviews and a workshop, and what fills the gaps is assumption. One cause, one fix, one expected outcome. Not because anyone is being careless, but because the system rewards plans that look clean.
In simple problems, that assumption holds. In complex ones, it is usually the first thing to break.
When the Fix Becomes the Problem
A well-intentioned programme in drought-prone Karnataka set out to revive millet farming. Millets are hardy, nutritious, and climate-resilient, well-suited to a region battered by erratic rains. The plan was clear: subsidised seeds and a processing machine. That should do it.
Except the farmers still had to sell their produce to middlemen who transported it to processing centres 100 kilometres away. Without local processing or direct market access, prices stayed low. Without reliable electricity, the machines ran inconsistently. Without any effort to build consumer awareness in nearby towns, demand did not grow.
One intervention. Five unaddressed bottlenecks.
SELCO Foundation's work on small-scale millet processing confronted this reality directly. Millet farmers were not struggling because of one missing input. They were caught in an interconnected web of climate stress, market dependency, energy unreliability, and financial exclusion. Addressing just one thread would not untangle the knot.
This is what systems thinkers call an unintended consequence:
when an intervention solves one problem but, by not seeing the larger system, quietly reinforces others.
The Feedback Loop We Keep Missing
What might be shaping this problem in ways we don't immediately see?
One of the foundational ideas in systems thinking is the feedback loop: the way that actions ripple back and change the very conditions they were meant to address.
Consider a familiar example. A city introduces a subsidised water supply scheme to reduce the distance women and girls walk for water. Pipes are laid. Taps are installed. But the scheme is poorly maintained and often runs dry, so families continue relying on private tankers. The tanker operators, now entrenched, actively lobby against infrastructure repairs. The solution has reinforced the problem it was meant to solve.
When we miss feedback loops, we can end up contributing to the very dynamics we are trying to change.
This is not a failure of intent. It is a failure of the mental model.
Why Complexity Demands a Different Kind of Planning
Complex systems, whether a rural agricultural economy, a slum neighbourhood's health ecosystem, or a tribal community's livelihood structure, share certain qualities that make linear planning inadequate.
They have many interacting parts. Changing one affects others, often in ways no one predicted. They contain feedback loops, so an action today can change the conditions you are working in tomorrow. They are deeply context-dependent: a solution that works in Rajasthan may fail in Odisha, even when the problem looks identical on paper. And they resist prediction; no single vantage point can fully anticipate where a complex system is heading.
This is what makes systems mapping different from simple problem analysis. Consequences can circle back and become causes.
This is why systems thinking changes the questions we ask. Instead of what is the cause?, systems thinkers ask what are the patterns? Instead of who is to blame?, they ask what structures are producing these outcomes?
Back to the Field: What a Systems Lens Reveals
Return to the millet farmer in Karnataka. A systems lens would ask different questions at the very start.
Who buys the farmer's produce, and at what price? What gives the middleman that power? What does the local energy infrastructure look like, and how reliable is it for running processing equipment? Is there a market for millet products nearby? Do consumers know or trust millet as food? Can the farmer afford a processing unit? What happens to soil health and food security if millet gives way to commercial crops?
These questions do not have a single answer. They invite a map. And that map becomes the foundation for designing something that actually holds.
SELCO Foundation's approach to millet processing did something that is still uncommon: it combined decentralised solar-powered processing units with attention to the entire chain, from energy access and equipment, to income security and market linkages.
It treated the problem as a system, not a silo.
The Deeper Problem With Linear Plans
Linear planning does not just produce poor outcomes. It also shapes how organisations learn, or do not.
When a project is designed as a straight line from input to output, there is no built-in mechanism for noticing when the world has changed, when a feedback loop has kicked in, or when a community's reality has quietly diverged from the theory of change drawn up in a conference room.
This is why so many programmes get renewed year after year, even when the evidence for their impact is thin. The plan becomes the proof. The process becomes the outcome. And the communities they were meant to serve keep waiting.
A systems approach expects surprises. It builds in learning. It asks practitioners to stay close to the ground, watch for unexpected consequences, and adapt continuously.
It treats implementation as an ongoing conversation between the plan and reality, not the delivery of a predesigned solution.
So, What Does Better Planning Look Like?
It starts with a genuine effort to understand the system before designing anything. That means talking to people at multiple points in the system, not just the intended beneficiary, but the traders, the local officials, the community health workers, the moneylenders. It means drawing out the relationships: what connects to what, what reinforces what, what blocks what.
It means designing for adaptability rather than rigid timelines. Learning milestones rather than fixed deliverables. The willingness to pivot when the system reveals something the plan did not account for.
And it means being honest about what the intervention cannot do, and about who else would need to act for the problem to actually shift.
All of this requires something harder to measure than a logframe: curiosity, humility, and the willingness to keep asking what am I not seeing?
A Final Thought
India's development challenges, farmer distress, urban poverty, healthcare access, climate vulnerability, are not simple problems with solutions waiting to be applied. They are systems within systems with systems, shaped by decades of policy, geography, culture, and power related vicious cycles.
Linear planning will always feel simpler. But in a complex world, simple plans often create complex new problems. The real work is learning to sit with that complexity, and plan from within it.
A linear plan, however well-funded and well-intentioned, will keep running into the walls of that complexity.
The Centre for Systems Practice exists because the field needs practitioners who can think differently, who can hold the complexity, map the connections, and design interventions that work with the system rather than against it.
Linear planning will always feel simpler. But in a complex world, simple plans often create complex new problems. The real work is learning to sit with that complexity, and plan from within it.
Try It for Yourself
Think of a problem you are currently working on. Not the solution you have designed for it. The problem itself.
Now ask: who else is part of this picture? What connects them? Where does money flow, where does information flow, and where do both get stuck? Who has power in this system, and why? What are you assuming will happen that you have not actually verified?
The worksheet below is a Rich Picture. It is a way of drawing out what you know about a system before you decide what to do about it. No right answers. No correct format. Just an honest attempt to map the thing as it actually is, not as the plan assumes it to be.
Start drawing. See what surfaces.
And if something in the worksheet raises a question, or if you want to think through your rich picture with us, write to us at info@centreforsystemspractice.org. We would love to hear what you are working on
The Centre for Systems Practice is a SELCO Foundation initiative. If this piece was useful, our newsletter goes out every month with one piece of practical thinking from the field.
Comments