Chapter 32: Stop Doing, Start Building Leaders

Maya's phone buzzed at 7:40 on a Tuesday, and she knew the question before she read it.

Priya, the delivery lead she'd hired in the spring, wanted to know whether to send the Henderson audit with the longer intro or the punchy one. It was a thirty-second decision. Maya answered it in twelve seconds and felt, for that twelve seconds, useful. Then at 9:15 Tomas asked which of two onboarding emails to use. At 11:00 the contractor handling teardowns wanted to know if a client's discount still applied. By lunch she had answered fourteen questions, every one of which she could have answered in her sleep, and not one of which she should have answered at all.

This was the substitute, and it was the most flattering one she'd reached for all year. She told herself she was being a responsive leader. A good boss is available. A good boss has standards, and the only way to hold the standard is to put her eyes on every call before it goes out. So she made herself the hub. Every decision routed through her, and routing through her felt like control, and control felt like safety. The team of four ran at the speed of Maya's inbox, which meant when Maya was on a sales call for ninety minutes, the whole company sat with its hands folded, waiting.

The bill came due on a Thursday. She was in a closing conversation worth eleven thousand dollars when Priya texted twice and then, getting no answer, held a finished deliverable for four hours rather than guess. The client noticed the delay. Maya noticed she had built a business with exactly one brain in it, and the brain was the bottleneck she'd sworn last month she would stop being. She'd named herself the constraint in Ch 31. Naming it hadn't moved it.

She went back to the council, and the council was unsentimental about what she'd been doing. Dan Martell put a number on her exact habit:

I would sometimes only start on my own projects at 6 p.m. and have to work till 11 or 1 in the morning. What I was doing is called transactional leadership, and it'll create a complexity ceiling. Telling people what to do, check that they got done, and then tell them what to do next. Usually at about 12, 13 employees, about 1.2, 1.4 million in revenue, it becomes chaotic.

Tell, check, tell. That was her Tuesday in three words. She had four people and was already running her own nights to cover the gap, which meant she'd hit the ceiling years early by sheer force of personality. Brendon Burchard's fix was not to answer faster. It was to stop being the one who answers:

Step one is define the outcome the person has to achieve; you don't tell them how, you get really good at painting a picture of success. Step two, choose a number, a measurement that lets them know if they're making progress. The third step is coach: anytime you see them do something wrong, you write it down and use your one-on-ones to train them up. Over a 6-month or 12-month period it'll take less and less time with that person.

Paint the outcome, not the how. She'd been handing out hows all day. He went further, and the instruction was almost insultingly simple:

Next is measurement. How are things going to be measured? How do we know if we have success? Who's going to be responsible for this? How will we know if we've done well? What does success look like for all of us?

One number each. Priya didn't need Maya's verdict on every intro. Priya needed to own a number, like on-time delivery, and the authority to hit it. EntreLeadership said the part Maya least wanted to hear, that her whole capacity was capped at the size of her own two hands until she changed the unit she worked in:

Anybody who's in a business, you have to look at what's systemizable and what's scalable. Most businesses I found can be systemized, can be scaled. If the Blue Man Group can do it, any of us can do it.

The shape of the answer she'd been dodging was decision rules. Write down how a call gets made, hand the rule to a person, and let the person make the call. Roland Frasier named the discipline it would take, because Maya's reflex was to get sucked back in the instant anyone hesitated:

Remember, the business is there to work for you, not the other way around. If it's not working for you within the time period and the capital you've allocated to make it go, stop. It will change your life to not spend all your time working in businesses.

Distance was the product now. Every question she answered was distance she gave back.

Three camps argued over what she should actually do, and they did not agree.

The first camp said build the people, and growth follows. Martell and EntreLeadership wanted her to take her best person, make them a leader, and compound. EntreLeadership made it concrete:

You take your three best guys and they each form a team, so now we have three teams. You bring in two guys, you train them. Within six months they had three Blue Man Groups. Then they grew it again, they took each person off, now they had nine teams, and then they had 18 teams.

The second camp told her to do the opposite. Stay lean. Don't throw people at the problem at all:

I think we just threw people at stuff instead of being smart. Now we're half the team size we were even 6 months ago and we're nimble again and it feels amazing.

This camp had a point that stung, because the version of Maya that hated managing wanted desperately to believe it. A bigger team meant a business she might grow to resent, full of meetings and payroll and other people's drama. If she only wanted margin and freedom, four people and contractors was plenty, and the move was to fix her own habits, not hire her way out.

The third camp ignored the size of the team entirely and warned her about its people. Dwarkesh Patel said the operators who got her here might not be the ones who take her up:

A company goes through different orders of magnitude of size. People that could help manage a 50-person company versus a 500-person company versus a 5,000-person company versus a 50,000-person company. You outgrew people. It's not always the same team.

The deciding variable was where Maya actually stood, which was nowhere near 500 people and squarely against the founder-dependency ceiling. The replace-at-each-10x camp was solving a problem two orders of magnitude ahead of hers. The stay-lean camp was right that she shouldn't bloat, and she wasn't going to. Her problem was not headcount. Four people was already too many for one brain to run as a switchboard. The lean camp's own logic pointed back at the first camp's fix: a small team only moves fast if the people in it can decide without her. So she chose to build the one lead she had, with rules, not to add bodies and not to swap anyone out. Build people first, kept small.

She wrote the decision rules that night. Not a manual. One page. Martell's tiered authority, scaled down to her tiny shop:

I have a $50 rule for anybody to solve a problem they run into as long as they tell their leader. I also have 500 for managers, 5,000 for directors, and 50,000 for C-level leaders where they can fix anything without approval as long as they let me know, because it pushes the decision to fix problems down to the people that have the most information to actually solve it.

Her version: any judgment call under a hundred dollars of client impact, the team decides and tells her after. Intro length, email choice, a small make-good for a late deliverable. All theirs. She promoted Priya to delivery lead, gave her on-time delivery as her one number, and said the sentence that cost her something real: from now on, you don't ask me which intro. You decide, and if I'd have done it differently, I live with it.

The toll came two days later. Priya shipped a teardown with the punchy intro, the one Maya would not have used, to a buttoned-up accounting firm. Maya watched it go out and her hand actually moved toward the phone. She put the phone down. The client replied an hour later: Loved the energy, when can we start. Maya had been wrong, and being wrong, quietly, with her hands folded, was the most freeing thing that had happened to her all month.

Marcus resurfaced that Friday, and for once he had news. He'd launched. After fourteen months of perfect decks and unbuilt courses, the thing was live, people had paid, and Marcus sounded wrecked. He was answering every support email himself at midnight. He wrote every lesson, ran every call, approved every refund, designed every graphic, because nobody else could do it to his standard. "I can't hand any of it off," he told her. "It all has to be me." Maya heard her own Tuesday coming out of his mouth, the switchboard she'd nearly drowned in, and understood that Marcus had finally crossed the start line only to build himself the exact cage she was unlocking. He'd paid the launch toll at last. He hadn't learned the one after it.

By the next week Priya was deciding things Maya never saw, and the company kept moving while Maya sat in an eleven-thousand-dollar call without her phone buzzing once. Capacity she didn't personally supply. It felt like getting an arm back.

Then she did the math on it and the next wall appeared. One promoted lead and one page of rules had bought her maybe ten hours a week. Human leverage compounds, and it compounds slowly, six to twelve months per person by Martell's own clock. She didn't have six months of patience and she couldn't hire her way to speed without becoming the thing the lean camp warned about. There had to be a kind of leverage that scaled in days, not quarters. She'd been hearing the word all year and flinching from it. AI.

My verdict. Being needed is the most comfortable cage a competent person ever builds. It looks like leadership and feels like control, and every question you answer is proof you matter, which is exactly why you keep answering them. The substitute you're hiding behind is your own indispensability. You stay the hub because if everything runs through you, nothing can go wrong without you, and nothing can grow without you either. The work you're avoiding is letting someone make a call you'd make differently and not touching it when they get it wrong. Write the rule down. Hand it over. Live with the 80%. The four-word version of this whole chapter: build leaders, not tasks.