You are staring at a dashboard full of numbers that all point in different directions. Revenue is up, but margins are shrinking. Customer acquisition costs are falling, but churn is climbing. You have hired two senior people this quarter, and somehow the team is less productive than before.
The instinct is to pick the most alarming metric and throw resources at it. Fix churn. Cut costs. Reorganize the team. But six months later, you are back in the same room, staring at the same kind of dashboard, wondering why nothing stuck.
The problem is not the metrics. The problem is that you are looking at individual numbers when you should be looking at the system producing them.
Learning how to think in systems is the single most important upgrade a leader can make — and it is far more accessible than it sounds.
Why Most Leaders Chase Symptoms Instead of Systems
There is a reason smart, experienced leaders keep solving the wrong problem. They were trained to think in things, not systems.
Consider this distinction from Drago Dimitrov in Instant Competence:
“What’s the difference between a ‘system’ and a ‘thing’? A system entails a relationship of things. A system is never just a solo item in isolation. In fact, any individual thing that you look at can be reframed and decomposed into a system or network of other things — sub-components, variables, factors — that somehow work together to make the big thing work.”
Your revenue is not a thing. It is the output of a system — a system of pricing, customer mix, sales velocity, retention, and a dozen other variables working together. When you try to “fix revenue” directly, you are treating a system output like a thing you can grab and move. You cannot.
As Dimitrov puts it:
“The reason we are experiencing a ‘problem’ in the first place is because we are unable to change the outcome variable directly — if we could, we would. Instead we engage in a ‘problem-solving’ process because we realize that the only way to change the outcome variable is to do so indirectly, by changing the variables driving the system behind it.”
This is the fundamental shift. You do not change outcomes. You change the configuration of the system that produces outcomes.
The Body Temperature Test: Systems Thinking in 60 Seconds
If this sounds abstract, try this thought experiment. You feel cold. That is a problem — a gap between your current state (cold) and your desired state (warm). You cannot snap your fingers and change your body temperature directly. So what do you actually do?
You instinctively identify the variables in the system driving your body temperature: weather, air conditioning, clothing, food and drink. Then you ask which of those variables you can change, and which changes would have the biggest impact.
Maybe the AC is set too low. Maybe you are wearing a t-shirt in a cold office. Maybe you skipped lunch. Each of these is a “knob” you can turn — and the combination of all of them determines your felt temperature.
This is systems thinking. You just did it without a textbook, a consulting framework, or a whiteboard. The challenge is doing it deliberately when the system is your business, your team, or a high-stakes strategic decision.
How to Think in Systems: The Formula Behind Every Outcome
Once you see that every outcome is produced by a system, you need a way to map that system precisely. The Instant Competence framework uses a simple but powerful formalization:
Y = w₁a + w₂b + w₃c + w₄d + w₅e
Here, Y is the outcome you care about — revenue, team productivity, customer satisfaction, whatever you are trying to change. The letters (a, b, c, d, e) are the variables that drive it. And the weights (w₁, w₂, w₃…) represent how much each variable influences the outcome.
Think of it like a mixing board in a recording studio. Each slider controls a different instrument. Some instruments carry the melody (high weight). Others add texture but do not define the song (low weight). The final sound — the outcome — is the combination of every slider position.
Here is why this matters practically:
- Not all variables are equal. A single turning click on one knob may produce more effect than cranking another one to maximum. Many leaders waste enormous energy optimizing a variable with a low weight while ignoring the one that actually drives the outcome.
- You cannot change Y directly. You change the variables. This reframes every strategic question from “How do we increase revenue?” to “Which knobs in the revenue system have the highest weight, what are their current states, and which ones can we realistically turn?”
- Mastery is systems knowledge. As Dimitrov notes: “All expertise involves precision. Mastery of any endeavor means understanding what systems are involved and discerning how to change the configuration of the system’s variables.”
The Connected Knobs Problem
Here is where systems thinking gets genuinely powerful — and where most leaders get tripped up. In real systems, the knobs are not independent. They are connected.
Dimitrov describes two critical types of connection:
First, a variable’s impact depends on the state of other variables. Imagine you increase marketing spend (variable a) to boost revenue (Y). If product quality (variable b) is high, that spending works — customers convert because the product delivers. But if product quality is low, the same increase in marketing spend might generate clicks that turn into complaints and returns. The knob you turned did not change. The system around it did.
Second, sometimes knobs are glued together. You turn one knob, and another one turns with it — whether you intended it or not.
“Imagine that when you turn knob of variable a with the goal of producing some effect onto your outcome KPI, Y, the knob of variable b also starts to turn incidentally. It’s like knobs a and b are somehow glued together on the back end, moving in tandem.”
The book gives a vivid example: a company implements just-in-time (JIT) inventory to reduce storage costs. That is one knob (inventory management). But turning that knob also turns the supplier relationship knob — JIT requires more frequent deliveries, tighter quality control, and deeper supplier coordination. The inventory decision is also, whether anyone planned it or not, a supplier strategy decision.
This is why isolated fixes so often backfire. You optimized one variable without noticing that it was connected to three others. Six months later, you are solving the problems your solution created.
A Practical Exercise: Map Your Connected Knobs
Pick an outcome you are trying to improve right now — team velocity, customer retention, deal close rate, whatever is keeping you up at night. Then:
- List the variables. What are the 5-7 components that influence this outcome? Do not judge yet — just generate. (For team velocity, you might list: hiring quality, onboarding process, tool stack, meeting load, scope clarity, team morale, technical debt.)
- Assign rough weights. Which variables have the highest influence on the outcome? Rank them. You do not need precise numbers — even a rough ordering (high / medium / low impact) reveals where your effort should concentrate.
- Check for connections. For each variable, ask: “If I change this one, which other variables will also shift?” Draw arrows between connected knobs. This is where the real insight lives. You might discover that improving scope clarity (one knob) also reduces meeting load (another knob) and improves morale (a third). That is a high-leverage move — one change that moves three knobs in the right direction.
- Find the highest-weight, most-connected knob. The variable with the most influence on the outcome AND the most connections to other variables is your best candidate for action. It is the intervention that propagates improvement through the system.
From Fuzzy to High Definition
The real power of systems thinking is what Dimitrov calls the upgrade from “fuzzy” to “HD” — high-definition problem framing. Most leaders define problems at the outcome level: “We need more revenue.” “Our team is too slow.” “Customer satisfaction is dropping.”
These statements are accurate but useless. They describe the symptom without revealing the system producing it.
“The upgrade we’re doing here is moving away from a high-level frame of: The current state of (value-informed KPI/outcome) is not the desired state. To the more specific and detailed frame: The current state of the system driving the (value-informed KPI/outcome) is not the desired state.”
“Customer satisfaction is dropping” becomes “The system of response time, first-contact resolution, product reliability, and onboarding experience that drives customer satisfaction has variables in suboptimal states.” Now you have something you can actually diagnose and fix.
This is not just wordsmithing. It is the difference between treating a fever and diagnosing the infection. One approach suppresses the symptom. The other finds and eliminates the cause.
Three Signs You Are Not Thinking in Systems
Most people do not realize they are thinking in “things” rather than systems until someone points it out. Watch for these patterns:
- You keep solving the same category of problem. If churn keeps coming back, if team conflicts keep resurfacing, if your growth stalls every time you hit a certain revenue threshold — you are probably fixing variables without addressing the system configuration that keeps producing the same output.
- Your solutions create new problems. Every aggressive fix that spawns two side effects is a sign that you changed a knob without checking what it was connected to. The JIT inventory example above is a mild version. In practice, the consequences can be severe — a pricing change that improves margins but triggers your best customer to shop competitors, or a reorg that solves a communication gap but destroys the informal networks that actually got work done.
- You are certain about the cause. Dimitrov’s framework includes a tool called Tiers of Certainty that separates what you know, what you assume, and what you do not know. In complex systems, premature certainty about causation is one of the most expensive errors a leader can make. If you have not mapped the system, you have not earned the right to be certain about what is driving the outcome.
Systems Thinking Is a Learnable Skill
The good news: you already think in systems every time you adjust the thermostat, plan a meal, or navigate rush-hour traffic. The upgrade is doing it deliberately and rigorously when the stakes are high and the variables are complex.
Start with the exercise above. Pick one outcome, map the variables, check the connections, and find the highest-leverage knob. You will be surprised how much clarity emerges from twenty minutes of structured thinking — and how many “unsolvable” problems turn out to be systems with a few knobs in the wrong position.
Ready to Think Differently?
The approach described in this post is part of Drago Dimitrov’s Instant Competence system — a battle-tested methodology for leaders who need to make the right call, even when the path is not clear.
Read Instant Competence to get the complete system, with real case studies and practical exercises.
Or start with the free Clarity Worksheet — a guided tool for defining and solving your most pressing challenge.