There is always one person. The Chief of Staff. The COO. The founder's right hand. The one who knows which initiative belongs to which bet, which team owns which deliverable, why that thing in last quarter's plan got quietly dropped, and which dependency is about to slip.
They are indispensable. That's the problem.
Indispensability is a system failure, not a virtue
When the strategy-to-execution link lives in one person's head, three things are true:
- The company cannot scale that person's clarity to more than the rooms they're in.
- A two-week holiday is a two-week visibility blackout.
- The day they leave, six months of institutional context leaves with them.
We celebrate these people. We should be alarmed by their existence.
If your weekly leadership review depends on one person remembering everything, you don't have an operating system. You have a person.
What "the picture" actually is
The picture is a graph. Strategic bets at the top. Objectives under each bet. Work items under each objective. Owners on every node. Health on every edge. Most companies have this graph — it just lives across one person's memory, three spreadsheets, two Notion docs, and a recurring Friday review.
Making that graph a real artifact, accessible to everyone with a reason to see it, is the entire job. It is also the only way to fire the bus factor.
The succession test
Imagine your indispensable person quits on a Friday. Could the leadership team run Monday's review without them? Could a new hire reconstruct the strategic bets, their current health, and what's being done about the at-risk ones from looking at your tools?
If the answer is no, you have a personnel risk masquerading as competence.
The Vindaris view
The job of an execution layer is to make the person-in-the-middle redundant in the best possible way — by making the strategy graph a shared artifact instead of a private cognition. The person stays valuable. They stop being a single point of failure.