Contents
Systems & Complexity
Section 1
The Core Idea
Interdependence means that parts of a system depend on each other. Change in one part affects others; those effects can feed back. The system is a web of relationships, not a set of independent units. Interdependence is the norm in organisations, supply chains, markets, and ecosystems. The strategic implication: optimising one part in isolation can suboptimise or harm the whole. You need a view of how the parts connect — who depends on whom, and how changes propagate. Interdependence can be a source of resilience (redundancy, mutual support) or of fragility (cascade failure, unintended consequences). The discipline is mapping dependencies and anticipating knock-on effects before acting.
Interdependence varies in strength and sign. Strong interdependence means one part's state heavily influences another (e.g. single supplier, critical component). Weak interdependence means the link exists but is loose. Positive interdependence means one's gain helps the other (e.g. platform and complementor). Negative interdependence means one's gain can hurt the other (e.g. competitors). Mapping the sign and strength clarifies where leverage is and where risk concentrates. The mistake is treating the system as if parts were independent — making a change and being surprised when second- and third-order effects dominate.
The model appears in supply chain (supplier-customer interdependence), in platform businesses (platform-developer interdependence), and in teams (role interdependence). It also appears in competition (rivals are negatively interdependent) and in cooperation (allies are positively interdependent). Strategy that ignores interdependence misses both opportunities (aligning positive interdependence) and risks (cascades, unintended harm from negative interdependence).
Section 2
How to See It
Interdependence reveals itself when a change in one part affects others, when people say "we can't do X without Y," or when a failure in one place propagates. Look for supply chains, platforms, teams, and contracts that create mutual dependence.
Business
You're seeing Interdependence when a product change improves one metric (e.g. engagement) but hurts another (e.g. retention or revenue). The metrics are interdependent; optimising one in isolation backfires. The same applies to departments: sales depends on product; product depends on engineering; changing one affects the others.
Technology
You're seeing Interdependence when a microservice fails and others that depend on it cascade. The system is a graph of dependencies. Changing or deploying one service can break others. Architecture reflects interdependence; managing it (e.g. fault isolation, versioning) is core to reliability.
Investing
You're seeing Interdependence when a portfolio company's fate is tied to a key customer, supplier, or partner. The company is interdependent with that counterparty. The investment thesis depends on the health of the relationship and the counterparty. Interdependence is concentration in the dependency graph.
Markets
You're seeing Interdependence when asset prices move together (correlation) or when the failure of one institution threatens others (systemic risk). Markets are interdependent; stress in one node can propagate. Regulation and circuit breakers aim to limit harmful interdependence.
Section 3
How to Use It
Decision filter
"Before changing one part of a system, map interdependence: who depends on this, and what does this depend on? How might the change propagate? Optimise for the system, not the part. Anticipate second-order effects."
As a founder
Map interdependence in the business: product, distribution, team, partners, capital. A change in pricing affects conversion and retention; a change in one team's output affects others. Design for positive interdependence (e.g. product and growth reinforcing) and avoid or mitigate negative interdependence (e.g. one team's goal undermining another). The mistake is local optimisation.
As an investor
Assess interdependence in portfolio companies: key customers, suppliers, talent, and internal functions. High interdependence with few nodes is concentration risk; interdependence that creates alignment (e.g. platform and ecosystem) can be a moat. Ask how a change or failure would propagate through the dependency graph.
As a decision-maker
Before a major decision, sketch the dependency graph. Who is affected? Who affects this? Will the change propagate in ways we want or don't? Interdependence means single-lever thinking often fails. Consider the system.
Common misapplication: Assuming independence when interdependence is high. "We'll just change our part" ignores the web. Map the graph; then decide. The other mistake is assuming everything affects everything — that leads to paralysis. Focus on the strong links first.
Second misapplication: Treating all interdependence as bad. Positive interdependence (e.g. platform and developers) can be a source of growth and lock-in. The goal is to understand and design interdependence, not eliminate it.
Section 4
The Mechanism
Section 5
Founders & Leaders in Action
Jeff BezosFounder & CEO, Amazon, 1994–2021
Bezos emphasised the flywheel: selection, experience, traffic, sellers — each reinforces the other. The parts of Amazon are highly interdependent; optimising one (e.g. price) without considering others (e.g. seller economics, logistics) would break the loop. He pushed for system-level thinking and avoided local optimisation.
Satya NadellaCEO, Microsoft, 2014–present
Nadella shifted Microsoft toward interdependence with the broader ecosystem — Azure with open source, Office with other platforms. He framed success as "partner success" and interdependence as strategic: the platform grows when complementors grow. Interdependence as design, not accident.
Section 6
Visual Explanation
Interdependence — Parts depend on each other. Change in one propagates. Map the graph; optimise the system.
Section 7
Connected Models
Interdependence connects to other systems concepts: feedback, coupling, and second-order effects. The models below either formalise interdependence (causal loops, feedback), describe its extremes (tight coupling), or help reason about it (systems thinking, ecosystems).
Reinforces
Systems Thinking
Systems thinking is the discipline of seeing wholes and relationships. Interdependence is the structure that systems thinking focuses on: parts are connected; change propagates. Systems thinking is the mindset; interdependence is the property being studied.
Reinforces
Causal Loops Diagrams
Causal loop diagrams map how variables affect each other — the structure of interdependence. The arrows are dependencies; the loops are feedback. CLDs make interdependence explicit and show where leverage and risk lie.
Reinforces
Feedback Loops
Feedback loops are closed chains of interdependence: A affects B, B affects C, C affects A. Feedback is interdependence that loops back. Reinforcing and balancing loops are types of interdependent structure that drive system behaviour.
Leads-to
Tight Coupling
Tight coupling is strong, fast interdependence: change in one part quickly and strongly affects another. Loose coupling is weak or slow. Interdependence can be tight or loose; tight coupling is high interdependence with short delay and strong link. It can mean cascade risk.
Leads-to
Second-Order Effects
Second-order effects are indirect consequences: A affects B, B affects C. Interdependence is what creates second-order effects. When parts are connected, first-order change propagates. Mapping interdependence helps anticipate second-order effects.
Reinforces
Ecosystems
Ecosystems are networks of interdependent species or actors. Platform ecosystems (developers, users, platform) are interdependent. The health of one affects the others. Interdependence is the defining feature of an ecosystem.
Section 8
One Key Quote
— John Donne"No man is an island, entire of itself."
Donne's line is a statement of interdependence: we are connected to others; what happens to them affects us. In systems, no part is an island. The quote is a reminder to map connections and consider propagation before acting as if the part were independent.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Map the dependency graph. For the system you care about (product, org, market), list the main parts and draw the links: who depends on whom? Which links are strong? The map reveals where change will propagate and where concentration of dependence creates risk.
Optimise the system, not the part. Incentives and metrics that optimise one part in isolation can hurt the whole when interdependence is high. Align metrics and goals with system outcomes, or explicitly model how local optimisation affects the rest. Interdependence makes local optimisation dangerous.
Design for positive interdependence. Where you want alignment (e.g. platform and developers), design interdependence so that one's success helps the other. Where you want isolation (e.g. fault containment), reduce or segment interdependence. Use the structure of interdependence deliberately.
Section 10
Test Yourself
Is this mental model at work here?
Scenario 1
A company optimises its checkout for conversion and sees conversion rise but repeat purchase and NPS fall. Revenue per customer drops.
Scenario 2
Two teams work on different products. They share no customers or code. A change in Team A's product has no effect on Team B.
Section 11
Top Resources
01
Book
Senge's systems thinking and interdependence: parts are connected; local optimisation can backfire. The organisation as an interdependent system.
02
Book
Meadows on stocks, flows, and feedback. Interdependence is the norm; the book shows how to map and intervene in interdependent systems.
03
Book
Sterman's treatment of feedback and interdependence in business. Formal modelling of how parts depend on each other and how change propagates.
Summary: Interdependence means parts of a system depend on each other; change in one propagates. Map the dependency graph, optimise for the system, and design interdependence where you want alignment. Avoid local optimisation when links are strong.
Further Reading: For systems and feedback, see Senge and Meadows. For supply chain and value chain interdependence, see operations and strategy literature. For platform ecosystems, see platform and network effects literature.
Why this matters next
mental modelsNetwork Effects
Interdependence applied the Network Effects mental model
mental modelsIncentives
Interdependence applied the Incentives mental model
mental modelsLeverage
Interdependence applied the Leverage mental model
mental modelsSystems Thinking
Interdependence applied the Systems Thinking mental model
mental modelsQuality
Interdependence applied the Quality mental model
mental modelsFeedback
Interdependence applied the Feedback mental model
Frequently asked questions
What is Interdependence?
Interdependence is a mental model used for better thinking and decision-making.
How do you apply Interdependence?
To apply Interdependence, identify situations where this framework is relevant, then use it as a lens to evaluate your options and decisions. The model is most useful when combined with other complementary mental models.
What category does Interdependence fall under?
Interdependence falls under the Systems & Complexity category of mental models. Other models in this category can be found on the Systems & Complexity hub page.
Why is Interdependence important?
Interdependence is important because it provides a structured way to think about problems that would otherwise be approached with intuition alone. Understanding this model helps you avoid common reasoning errors and make better decisions.
Continue exploring
LEANEMFLGLL(
Mental model
Lollapalooza Effects
When multiple cognitive biases or forces act in the same direction simultaneousl
Mental model
Antifragility
Beyond resilience — some systems actually gain from disorder, volatility, and st
Mental model
Emergence
Complex system-level properties that arise from simple interactions between indi
Mental model
Feedback Loops
Circular causal chains where the output of a system feeds back as input — either
Mental model
Gall's Law
A complex system that works is invariably found to have evolved from a simple sy
Mental model
Leverage (Systems)
Places within a complex system where a small shift produces large changes — Mead
More like this, in your inbox
I send a newsletter every week — free, no spam, unsubscribe anytime.