Week 5 Day 6: The Leader Who Does Too Much Creates a Team That Does Too Little

When you jump in to solve a problem your team is working on, you send a message. The message is not 'I am helping.' The message is 'I do not think you can handle this.' You may not mean it that way, but that is how it lands. Over time, the team adjusts. They stop trying as hard on difficult problems. They wait for you to step in. They start bringing you half-finished work because they know you will finish it anyway. You have built a dependency without realizing it.

There is a test I use to check myself. At the end of each week, I look at everything I did and ask: could someone on my team have done this? If the answer is yes for more than one or two items, I have a problem. Not because the work was beneath me -- there is no such thing when you are a leader -- but because I took a growth opportunity away from someone. That status update I rewrote? A tech lead could have written it and gotten feedback. That architecture discussion I led? A senior engineer could have facilitated it and built their cross-functional skills. That vendor call I took? A product manager could have run it and learned how to manage external relationships. Every time I do these things myself, I get the task done faster but the team grows slower. And which matters more in the long run? The math is obvious once you see it. The hard part is seeing it in real time when the task is sitting in front of you and doing it yourself takes five minutes while coaching someone through it takes thirty.

Liz Wiseman's quantitative research in 'Multipliers' measured the impact of what she calls 'Diminishers' -- leaders who, often with good intentions, centralize decision-making and personally intervene in their team's work. Her data shows that Diminishers extract only about 50% of their team's available intelligence and capability, while Multipliers extract close to 100%. The mechanism is not motivation -- team members under Diminishers often report working hard. The difference is in where they direct their cognitive effort: under Diminishers, team members spend significant mental energy managing up, second-guessing themselves, and waiting for validation. Under Multipliers, that same energy goes directly into the work. David Marquet's experience on the USS Santa Fe provides a military parallel: when he stopped giving orders and started requiring his crew to state their intentions ('Captain, I intend to submerge the ship'), the crew's ownership and initiative increased dramatically, and error rates dropped to the lowest in the submarine fleet. The principle is consistent: the leader who does less operational work creates the conditions for the team to do more meaningful work.