Pre-read 5: The Law of Empowerment
Only secure leaders give power to others. "I can do it faster myself" is the opposite of this law, and it is the most common reason new leaders fail.
The standard first: task-relevant maturity (Grove)
Andy Grove's book High Output Management gives delegation a clear rule. The variable that decides how to manage someone is task-relevant maturity (TRM): how much experience and judgment they have on this specific task, not how senior they are in general. A brilliant senior engineer has low TRM the first time they lead a production incident. A mid-level engineer can have high TRM on the system they have worked in for two years.
The rule: low TRM gets detailed, structured oversight. Medium TRM gets two-way coaching. High TRM gets goals and light monitoring, nothing more. Micromanaging a high-TRM person insults them and slows them down. Leaving a low-TRM person alone drowns them. Both mistakes come from managing by your own comfort instead of by their maturity.
Two extensions make it sharper. First, delegation levels: "collect the data", "recommend a decision", and "decide and inform me" are three different grants. Saying the level out loud prevents the classic failure where both sides guess differently. Second, David Marquet's intent ladder: move people from "tell me what to do" up to "I intend to do X". That turns a team from one brain with many hands into many brains.
Google's Oxygen data agrees from the other side: "empowers the team and does not micromanage" is one of the behaviors that separates the best managers from the rest.
The law behind the standard
Maxwell focuses on the blocker, not the mechanism: only secure leaders give power to others. The reasons people hold on to work are rarely about the work. Job security ("if they can do it, why am I here?"), speed ("faster myself"), quality ("they will do it worse"), trust. Each reason feels true in the moment, and each one is fatal over time, because a leader who cannot hand off power limits the team to the size of their own hands. Empowerment means giving people the authority to make decisions that could embarrass you, and accepting their version of good.
On your track
- IC (Staff/Principal): hand ownership of the component only you understand to a mid-level engineer, and accept their first bad decision. Until you do that, you do not own the component. It owns you.
- Lead/EM: hand over decisions, not just tasks. A delegated task where you keep the decision is not empowerment. It is assistance.
The story: Amazon single-threaded owners
Amazon built empowerment into its org design. A single-threaded owner runs one thing with real authority over it. The leaders above them are forced to delegate, because the owner holds the work, not the executive. The design accepts that some decisions will be worse than the executive's, on purpose. Many good-enough decisions made quickly beat a queue of perfect decisions waiting behind one busy brain.
Before the session
Come with one question this reading left you with. Starting points:
- List what you did last sprint that someone else could have done 80 percent as well. What is the honest reason you did not hand it off?
- Whose TRM are you reading wrong right now, in either direction?