For most of a decade, both Barcelona and Argentina were built with Messi at the centre. That produced remarkable results and a well-documented question that followed both teams: what happens when he is unavailable?
Key-person dependency is not an accident. It is a design decision, usually made because it works.
The people question this raises
Concentrating your best resource where it has most leverage is good management. Concentrating it until nothing functions without that person is a risk you accepted without pricing. Most companies have at least one of these and only discover it during a resignation or a hospital stay.
Where this shows up at work
- One engineer understands the billing system, so every release waits for their review.
- One founder holds every key client relationship personally.
- One operations manager knows the workarounds that keep month-end from breaking.
How to keep the leverage and cut the fragility
- 1Name the single pointsFor each critical process, write the name of the person it stops without. Keep the list to one page.
- 2Rank by damage, not seniorityAsk how long the business functions in their absence: a day, a week, a quarter?
- 3Document, then rotateWritten runbooks first, then a deliberate second owner who actually does the work sometimes.
- 4Pay for the sharingRecognise the star for building others' capability, or the dependency will quietly rebuild itself.
The aim is not to make the star smaller. It is to make the team large enough that the star's absence is a setback rather than a stoppage.
Interpretation, not fact: how much either team's fortunes depended on one player is debated by people with far better data than mine. The documented part is only that both were built around him, and both were repeatedly asked about the succession question.
Over to you
If your most critical person disappeared for a month, which process breaks first — and who else could run it today?