If you want an honest diagnostic of how dependent your company is on you, don't look at the org chart. Sit quietly in your weekly leadership meeting and watch who talks, who defers, and who is actually driving decisions. Fifteen minutes will tell you more than any consulting deck.
What the Room Actually Reveals
In companies that still run through the founder, the meeting has a familiar shape. The founder opens with updates. Team members report status. When a genuine decision needs to be made — a pricing exception, a hiring tradeoff, a resource conflict — eyes turn to the founder, and the founder answers. Efficient, in a way. Also a clear sign the meeting is decorative; the real decision-making happens in the founder's head, informed by whatever they heard in the room.
Contrast that with a meeting where a functional leader opens with a specific problem, presents two options with a recommendation, and the group debates the recommendation rather than waiting to be told what to do. The founder might weigh in. But the meeting does not depend on the founder to function.
Why Founders Accidentally Train the First Pattern
Nobody intends to create a room full of order-takers. It happens gradually, usually because the founder is fast and confident, and it's genuinely quicker for the founder to just decide than to wait for a team member to build the case. Speed in the short term trains dependency in the long term.
I've watched founders get frustrated that their team "won't step up," without recognizing that every time someone tried to step up with an incomplete recommendation, the founder took the decision back rather than coaching the recommendation to completion. The team learns the fastest path is deference.
Resetting the Room
Changing this requires the founder to change their own behavior first, before asking the team to change theirs. That means, in the next meeting, responding to a request for a decision with a question instead of an answer: "What would you recommend, and why?" It means tolerating an answer that isn't quite as sharp as what the founder would have said themselves, and building on it instead of overriding it.
It also means being explicit about the shift. I've had founders literally say to their team, "Starting this week, I want you to bring me recommendations, not questions." That clarity matters, because teams that have been trained to defer won't reinterpret silence as permission to lead.
The Long Game
This shift takes months, not one meeting. But the payoff compounds: a leadership team that can run the operating rhythm without the founder in the room is a team that can also run the company during a capital raise, a sick week, or a strategic pivot that demands the founder's full attention elsewhere. The weekly meeting is a small stage. What happens on it is the whole story.