Where Does Authority Live in Your Company?
Most founders would say the transition is going well. The successor is capable. The team is aligned. The org chart reflects the new structure. Ask a harder question and watch what happens.
Where does authority live right now — functionally, not formally? Not what the chart says. What actually happens when a hard decision needs to be made and needs to stick?
If the honest answer is “it depends,” you already have your answer. Drift is present.
Key Takeaways •The diagnostic question of any transition: where does authority live functionally — in practice — not on the org chart.•When the honest answer is “it depends,” the organization is already compensating. Drift is present. •The goal isn’t a perfect transition. It’s a coherent one, with one center of authority, one decision channel, one set of commitments that hold. •Name the dependency, then design it out. A short self-assessment makes the gap visible before it reaches the P&L. |
“It Depends” Is a Structural Problem
“It depends” means the organization has more than one center. Decisions route differently depending on who is in the room, whose blessing feels safest, who might push back later. That is not a communication issue or a personality mismatch. It is the organization compensating for authority that has not finished forming around the successor.
The compensation looks responsible in the moment. Over months, it becomes the culture.
The most revealing version of this question is not what any one person says. It is the gap between answers. When the founder, the successor, and the executive team each describe authority differently, everyone is operating from a private map. The maps do not agree. That is precisely why decisions reopen, why execution slows, why capable people keep checking before they act.
The Goal Isn’t a Perfect Organization
It’s a coherent one.
One center of authority. One decision channel. One set of commitments that hold without being chased. Coherence is what lets a company move through a handoff at speed instead of stalling into politeness and second-guessing.
It shows up quietly. Decisions stay closed. People stop checking “just to be safe.” The founder is respected, and no longer functions as the default stabilizer. Meetings get shorter because the real decision isn’t happening somewhere else.
None of it is dramatic. The absence of drama is the point.
Name the Dependency. Then Design It Out.
That is the whole of the work in a sentence.
If decisions depend on the founder’s informal blessing, name that — and build the structure that removes the need for it. If executives are running a back-channel because the successor’s decision lane is unclear, name that — and make the lane explicit. Drift survives on dependencies no one says out loud. The moment they’re named, the work can begin.
You don’t need a three-year process. You need an honest read of where authority actually lives today, and the willingness to redesign the two or three dependencies that are quietly running the place.
The fastest way to get that read is to measure it, to turn “something feels off” into something you can see, compare across your leadership team, and act on before it reaches the P&L.
The title says the transition is settled. The answer to one question tells you whether it actually is.
If you made it this far, you recognize the dependency.
Maybe it’s a decision that keeps reopening. Maybe it’s a founder whose informal blessing is still the real approval. Maybe it’s an executive team running a back-channel because the decision lane was never made explicit. The Legacy Drift Quick Scan is the next step: five minutes to see where authority actually lives, measured across the people who lead — before it reaches the numbers.
