Systems thinking for leaders — seeing the whole system.
Most leadership advice fixes the wrong level. It treats the latest crisis as the problem, when the problem is the structure quietly producing crises like it. This is a plain-language primer on seeing the system underneath the symptom — and intervening where the leverage actually is.
Systems thinking is seeing the structure that keeps producing the problem — not just the problem.
Linear thinking asks: what caused this, and who do I hold responsible? It treats every issue as a fresh event with a single cause and a single fix. Systems thinking asks a harder, more useful question: what structure keeps producing this result, no matter who is in the seat?
The shift matters because companies are not chains of isolated events. They are webs of incentives, information flows, roles and beliefs that interact over time and produce behaviour. Fire the person, and the role keeps generating the same outcome. Solve the incident, and the pattern returns next quarter. Until you can see the system, you are playing whack-a-mole with your own company — and losing, expensively.
From cause-and-effect to seeing the web.
Linear thinking is fast, intuitive, and right often enough to feel reliable. That's exactly why it's dangerous at scale.
Linear thinking finds a culprit
One cause, one effect, one fix. It works for a broken build or a late shipment. It fails the moment a problem has more than one parent — which describes almost every problem worth a founder's attention.
Systems thinking finds the loop
It asks what feeds back into what. The hire that didn't work may be a recruiting problem — or a sign the role itself is structured to fail. Same symptom, very different intervention.
The cost of getting the level wrong
Solve a structural problem at the event level and you buy a few weeks of quiet before it returns. You spend real money and attention on a fix that was never going to hold. Most founder firefighting is this — competent effort aimed one level too shallow.
Four levels — and why advice usually fixes the top one.
The iceberg is the single most useful map in systems thinking. Every problem lives on one of four levels, and the level you act on decides whether anything changes.
1 · Events — what just happened
The visible tip. A key engineer quit. A launch slipped. Two leaders clashed in a meeting. Events demand a reaction, and most leadership energy is spent here — which is why so little of it produces lasting change.
2 · Patterns — what keeps happening
Step back and events repeat. Senior people keep leaving that one team. Launches in that division keep slipping. The same two leaders keep clashing. A pattern is the first sign you're not dealing with bad luck — you're dealing with a system.
3 · Structures — what produces the pattern
Below the waterline: the incentives, roles, reporting lines, information flows and policies that make the pattern almost inevitable. The team loses people because two managers own overlapping mandates and nobody resolved it. Structure is where real leverage begins.
4 · Mental models — what holds the structure in place
The deepest level: the beliefs and assumptions nobody questions. "We don't have time to define ownership clearly." "Conflict means someone is failing." Structures are built on mental models. Change the structure without touching the belief and the old structure quietly rebuilds itself.
Most leadership advice — and most coaching — operates at level one or two. It manages events and soothes patterns. The durable work happens at three and four. For more on the levels a problem can live on, see the frameworks.
Small shifts, big change — if you find the right place to push.
A leverage point is a place in a system where a small, well-placed change produces disproportionate results. The trap is intuitive: leverage almost never sits where the symptom is loudest. The loudest symptom is usually the place where pushing harder does the least.
When a metric is bad, the instinct is to push directly on the metric — more dashboards, more meetings, more headcount, more pressure. That's a low-leverage intervention. You're adding force against a system that will absorb it and snap back. The high-leverage move is usually quieter: change one incentive, redraw one ownership line, surface one unspoken assumption. The shift looks small. The effect compounds because the system itself now works for you instead of against you.
"The founder who solves every problem themselves is building a company that can't think without them."Naina Sahni
That line is itself a systems insight. The founder-as-bottleneck isn't a time-management problem to fix with a better calendar. It's a structure — every decision routed through one head — held in place by a mental model that says "I'm the only one who can be trusted with this." Push on the calendar and nothing changes. Push on the structure and the belief, and the whole company starts thinking again.
The two loops running quietly inside your company.
Systems behave the way they do because of feedback loops. There are only two kinds, and once you can name them, a lot of stuck situations suddenly make sense.
Reinforcing loops — momentum that compounds
A change feeds more of itself. Trust earns more trust; a team that ships builds confidence that helps it ship again. The same engine runs in reverse: one missed commitment breeds caution, caution slows delivery, slow delivery breeds more caution. Reinforcing loops are how small things become large — for better or worse.
Balancing loops — the quiet pull toward a target
A system resists change and pulls back toward a set point. Push a team past what feels sustainable and they slow down — not from laziness, but because an invisible balancing loop is protecting the set point. You add headcount; informal coordination cost rises to match; throughput stays flat. The loop is doing exactly what loops do.
The same disagreement, re-litigated every quarter
Here's a loop most companies live with for years. A decision gets made. The underlying disagreement was never surfaced, so the people who lost quietly route around it. Friction builds. The decision is reopened. It's made again, the same way, with the same buried disagreement — and the loop resets. The fix isn't deciding faster. It's surfacing the real disagreement once, at the structural level, so the loop has nothing left to feed on.
Most stuck companies are one named loop away
A reinforcing loop running unchecked, or a balancing loop nobody has named. The relief of systems thinking is that the chaos is rarely random. It has a shape. Find the loop, name it out loud, and you can finally intervene where it lives.
How I use this with founders.
I'm Naina Sahni — an executive coach to founders and CEOs at some of India's defining companies. Systems thinking isn't a slide I present; it's the lens I work through. I'm a Master Practitioner trained at the MIT Centre for Systems Awareness (Cohort 7), and a PhD scholar whose doctoral work developed original constructs in this space.
In practice, the work is almost always moving down the iceberg. A founder arrives with an event — a resignation, a stalled launch, a conflict between two leaders. The cheap response is to react to the event. The coaching response is to ask what pattern this belongs to, what structure produces the pattern, and what belief holds the structure in place. By the time we reach the bottom of the iceberg, the founder is usually looking at a problem they've solved at the surface five times — and can finally solve once.
"During the transition from Grofers to Blinkit — Naina was the uncomfortable but necessary voice pushing everyone, including me, to seek more clarity."Albinder Dhindsa · CEO Eternal / Founder, Blinkit
I coach 12+ founders — including at Zomato, Blinkit, CARS24, Bijnis, Xpressbees and Animall. The throughline is the same: a leader who can see the whole system holds steadier under pressure and stops paying the same problem twice. If you want to go deeper into how that shows up in leading a startup, read leadership coaching for startups.
From the writing.
Essays on systems, clarity and the inner game of leading.
The frameworks
The levels a problem can live on — and why most coaching fixes the wrong one.
Leadership coaching for startups
How systems thinking changes the way a founder leads through hyper-growth.
What a CEO coach actually does
The work on judgment and clarity that every other decision flows from.
The blog
Over 150 essays on leadership, systems and learning organizations.
Systems thinking, answered.
What is systems thinking for leaders?
Systems thinking is the discipline of seeing a company as a set of interconnected parts that produce behaviour over time, rather than a chain of isolated cause-and-effect events. For a leader it means asking what structure keeps producing this result, instead of who is to blame for the latest one. It shifts attention from reacting to events toward changing the conditions that generate them.
What is the iceberg model in systems thinking?
The iceberg has four levels. Events are what just happened — the visible tip. Patterns are events recurring over time. Structures are the policies, incentives, roles and information flows that produce those patterns. Mental models are the beliefs that hold the structures in place. Most leadership advice fixes events; durable change happens at the structure and mental-model levels.
What is a leverage point?
A leverage point is a place in a system where a small, well-placed shift produces large change. Leverage rarely sits where the symptom is loudest. Adding more effort at the symptom — more meetings, dashboards, headcount — usually pushes against the system. The higher-leverage move is changing the structure, incentive or belief that keeps generating the problem.
What's the difference between a reinforcing and a balancing loop?
A reinforcing loop amplifies change in one direction — momentum that compounds, like trust building trust. A balancing loop resists change and pulls a system back toward a target — like a team quietly slowing down when workload exceeds what feels sustainable. Most stuck situations are a reinforcing loop running unchecked or a balancing loop nobody has named.
How does Naina use systems thinking in coaching?
Naina is a Master Practitioner trained at the MIT Centre for Systems Awareness and a PhD scholar whose doctoral work developed original constructs in this space. In coaching she helps founders move down the iceberg — from the triggering event to the structure and mental model underneath — so they intervene where the leverage actually is, rather than firefighting the same pattern every quarter. The first pilot session is free.