In 1919, Henry Ford was called to testify in a lawsuit brought by the Chicago Tribune, which had called him an anarchist and an ignorant idealist. Ford's attorneys decided to demonstrate his intelligence by questioning him on general knowledge. The Tribune's lawyers had the same idea — and began asking Ford basic historical questions. When was the American Revolution? What army did Benedict Arnold fight for? Ford, who had left school at 16 and built the most productive manufacturing operation in human history, could not answer most of them. He grew visibly frustrated, finally declaring: "I have a row of electric push-buttons on my desk, and by pushing the right button I can summon to my aid men who can answer any question I desire to ask. Why should I clutter up my mind with general knowledge when I have men around me who can supply any knowledge I need?"
The courtroom laughed. Ford did not. He had just described the most sophisticated understanding of delegation in the room.
The leader who insists on knowing everything and doing everything does not build an organization. They build a dependency. The leader who pushes the right button — who develops people capable of answering questions they themselves cannot — builds something that outlasts them.
The most common root. High standards for the outcome, combined with a genuine belief — often accurate — that you can produce that outcome better than anyone currently on your team. So you retain the work rather than risk a substandard result. This feels responsible. It is not leadership.
Steve Jobs was famous for his inability to delegate design decisions. Every pixel, every material choice, every visual judgment passed through him. The products were extraordinary. The organization was brittle. When Jobs left Apple the first time, the company nearly collapsed — not because it lacked good people, but because those people had never been allowed to develop the judgment that delegation builds. When he returned and was forced, by scale, to develop leaders rather than just products, Apple built the most valuable company in history. The constraint was not talent. It was his own grip.
Less about standards, more about the discomfort of uncertainty. When someone else is doing the work, the outcome is less predictable. For leaders who are uncomfortable with that predictability gap, the solution is to stay involved — through excessive check-ins, detailed instructions, constant updates. This is not distrust of the team. It is discomfort in the leader — and it communicates distrust regardless of intention.
Some leaders hold onto work because delegating it feels like burdening someone else with what they should be carrying. This is especially common in player-coaches — leaders who came up as strong individual contributors and now manage people doing similar work. The solution is not a delegation technique. It is a clearer understanding of what leadership actually is: not doing the important work, but building the people who do it.
Choose one project you currently hold that someone on your team could theoretically own. Write down the outcome — not the process, not the steps, just what success looks like. Hand it over with three things: the outcome, the relevant resources, and one escalation criterion — come to me only if this specific thing happens. Then commit, explicitly, to non-interference unless they come to you.
The discomfort you feel doing this is the data. It shows you exactly where the control anxiety lives — which makes it available for examination rather than just avoidance. Every leader who has made this shift reports the same surprise: people rise to real ownership faster than expected. They were waiting for permission to be trusted. You were waiting to feel comfortable giving it. One of you had to go first.