You can make a structurally sound decision — good reversibility, real upside, manageable downside — and still have it fail because of factors entirely outside your control. That's dependency risk: the degree to which your outcome depends on other people, external conditions, or circumstances you can't directly influence. It's the most underrated variable in most decision frameworks.
Why it's systematically underweighted
Dependency risk is underweighted because it's uncomfortable to acknowledge. Admitting that your success depends heavily on someone else's competence, someone else's decision, or a market condition you don't control feels like admitting weakness. So people tend to elide it in their analysis and assume more agency than they actually have.
This shows up consistently in startup postmortems. Founders describe their businesses failing due to market timing, a key partner walking, a customer concentrating too much revenue, or a regulatory change — all of which are dependency risks that were visible before the failure, but not weighted correctly. The structural analysis of the business idea was often sound. The dependency risk assessment was not.
The categories of dependency risk worth mapping
- ◆People dependencies — your outcome depends on a specific person's performance, competence, or continued involvement (a manager, a co-founder, a key client)
- ◆Market dependencies — your outcome depends on a market condition holding (interest rates, sector demand, consumer behavior)
- ◆Platform dependencies — your outcome depends on a platform or distribution channel that you don't control (a marketplace, an algorithm, a regulatory environment)
- ◆Timing dependencies — your outcome depends on things happening in a specific sequence or on a specific timeline
The co-founder case
Taking on a co-founder is one of the highest dependency risk moves in business. You're not just adding a person — you're making your entire trajectory contingent on the quality of that specific relationship under stress. The vast majority of startup failures involve co-founder conflict as a contributing factor. This doesn't mean don't take co-founders. It means the dependency risk is real, it's high, and it deserves explicit acknowledgment in the decision analysis rather than optimistic assumptions about how well things will work under pressure.
How to actually manage dependency risk
You can't eliminate dependency risk, but you can manage it through three approaches. First, diversify: where possible, reduce concentration in any single dependency. A business with five customers is more resilient than one with one customer who represents 80% of revenue. Second, hedge: for the dependencies you can't diversify, have a contingency. If the key person leaves, what's the plan? If the market condition shifts, what's the response? Third, prioritize reversibility: decisions with high dependency risk should weight reversibility even more heavily than usual, because you're accepting that the outcome is partially outside your control.
The question worth asking for every major decision
What's the one dependency that, if it failed, would make this decision clearly wrong? Name it specifically. Then ask: how likely is that failure, and what's my plan if it happens? If you can't answer the second question, you're not ready to make the decision.