
The Answer Is the Problem
The Answer Is the Problem
There is a version of leadership that feels like dedication and functions like sabotage. You can spot it everywhere in service businesses. The founder who answers every question. The director who steps in whenever things get uncertain. The owner who has trained their team, without ever intending to, that independent thinking is neither required nor welcome. They are helpful, available, and always there. And the business reflects it. Nothing works without them.
This is not a character flaw. It is the natural end point of a founder who was once the best person in the room at solving problems. They got good, they got trusted, and then they kept going. The trouble is that every question they answer trains the team not to answer it themselves. Every time they step in, they send the message that the team cannot be trusted to find their own way through. Over time the team stops trying. Why would they? The founder will sort it.
The most effective coaches in high-performance sport understand this problem precisely. The instinct when someone is struggling is to give them more information. More technique, more variables, more options. It feels like help. What it actually does is overload the person in front of you with possibilities they are not yet equipped to navigate, and strips them of the one thing that would actually develop them: the experience of working through the problem themselves. The coach who cannot resist showing everything they know is not teaching. They are performing. And their students stay dependent as a result.
The parallel in a service business is exact. Most founders brief their team with every possible variable, every contingency, every nuance, because they are afraid of the team getting it wrong. But the team is not at that level yet. They do not need every variable. They need the core principle, clearly stated, and then the space to apply it and make mistakes. The mistakes are not the problem. The mistakes are the lesson. What you learn from getting it wrong when the stakes are low is worth ten times what you learn from being given the right answer.
Extreme Ownership starts here. Not with blaming yourself for past decisions, but with being honest about what you have actually built. If your team cannot operate without your input, that did not happen to you. You created it. Probably with good intentions. Definitely with consistent behaviour over a long period of time. And the only way to reverse it is to stop doing the thing that caused it.
That means sitting with discomfort when someone brings you a problem you could solve in thirty seconds. It means asking a question back instead of giving an answer. It means accepting that their solution will be slightly worse than yours for a while, and understanding that this is not a cost. It is the investment. Decentralised Command does not happen because you decide one morning to trust your team. It happens because you deliberately, consistently, create the conditions for them to develop their own judgment.
The environment matters more than most founders realise. People become a product of what surrounds them. If the environment signals that the founder has all the answers, the team will wait for the answers. If the environment signals that independent thinking is expected and mistakes are tolerable, the team starts to think. This is not a culture statement on a wall. It is a function of what behaviour gets rewarded and what behaviour gets bypassed every single day.
Simple is one of the most underused principles in operational leadership. Not simple as in dumbed down, but simple as in stripped to its essential truth. What is the one thing this person needs to understand to handle this situation without you? Start there. Give them that. Let them work with it. Most of what founders add beyond that first essential principle is noise. It is knowledge that has not yet been earned, and knowledge that has not been earned cannot be applied.
The ripple effect of getting this right is bigger than most founders allow themselves to imagine. A team member who learns to think clearly and take ownership of their work does not just perform better in their role. They carry that standard home. They raise their own expectations. They model it for people around them. The business that develops people rather than creates dependency does not just run better operationally. It builds something that compounds.
The founder who has built a team that needs them for everything has not built a business. They have built a very complicated personal responsibility. The way out is not a restructure or a new process. It is a fundamental shift in what leadership actually requires from you.
Stop answering the question.
That is where it starts.