A commercial cleaning company serving a cluster of mid-sized office buildings started with the founder and two crews. She walked every new site herself before the first clean, set the standard out loud, what counts as done, what gets flagged, what never gets left for the client to notice, and signed off on every contract renewal personally.
Eighteen months later, the business has seven crews and seventeen staff on the books. On paper, that looks like growth working exactly as it should: more buildings, more revenue, more people doing the work.
In practice, the founder now spends most of her week doing site walk-throughs she thought she'd delegated within a month of hiring someone, fielding client calls about inconsistent standards between crews, and re-explaining, team by team, the same handful of judgment calls she thought she'd already handed over twice before. She has more staff than she's ever had, and she is more tired than she's ever been.
The Obvious Diagnosis Was Capacity
The instinct, when a business starts to strain, points in one direction: add. Hire someone, buy a tool, spend more on marketing, push through this stretch and sort the structure out later. Addition feels like action in a way that pausing to examine the design never does. A job ad can go up this afternoon.
That instinct wasn't wrong exactly, in this case. The company genuinely had more work than two crews could physically clean. Hiring more people to actually do the cleaning was a real response to real demand.
What the hiring didn't do was make the founder less busy. If anything, she now has more open questions landing on her desk each week than she had when the business was a third of the size. More people clean more buildings. More people also ask more questions, make more judgment calls nobody has written down, and need more correcting when the standard drifts, because nobody told them precisely what the standard was in the first place.
Hands and Capability Don't Travel on the Same Curve
The Designed Business makes a specific distinction here that's easy to miss while hiring feels urgent: adding people gives a business more hands. It does not automatically give the business more capability.
Capability is the ability to reproduce the promised result without the founder checking first. It depends on whether a new hire knows the result they personally own, which decisions are theirs to make, what information they need to make those decisions well, and what standard their work is judged against. Hands are simply more people available to do tasks.
The two aren't the same thing, and the gap between them doesn't stay flat as a business grows. It compounds. One undertrained cleaner missing the standard on one job is a correction. Five crews, each missing a slightly different piece of an unwritten standard, each handling client complaints differently, each escalating different judgment calls back to the founder, is a business that has become measurably heavier to run than it was with two crews, not lighter.
The book names the end state of this plainly: a business that hires people without giving them a defined result, real decision rights, and a clear standard hasn't built a team. It has built a queue.
Where the Weight Actually Piled Up
Run that distinction against the cleaning company's seven crews, and the pattern that looked like random chaos turns out to be specific and locatable.
The quality standard existed only in the founder's head, demonstrated, never written down. Each team lead had watched her do a handful of walk-throughs early on and extrapolated from there, which meant seven crews were running seven slightly different versions of "done," none wrong exactly, all different enough that a client whose two buildings were cleaned by two different crews noticed the inconsistency immediately.
Decision rights hadn't been named either. A team lead facing an unusual request, a last-minute schedule change, a damaged item during a clean, had exactly one playbook: call the founder. Not because any individual team lead lacked judgment, but because nobody had ever told any of the seven leads which calls were theirs to make and which genuinely needed her.
And because neither of those existed, every new hire didn't just add a pair of hands to the roster. Each one added a fresh source of unstandardized judgment calls that funneled straight back to the one person already drowning in them. Seventeen staff were producing work. Seventeen staff were also producing questions, at a rate that grew faster than the crews did, because each new person arrived into the same undescribed standard and had to independently rediscover, through trial, correction, and the occasional client complaint, what the first two crews had learned by watching the founder directly.
The founder hadn't built a more capable business by hiring. She'd built a wider funnel, all of it still draining back to her desk.
What Changes Before the Next Hire
The useful move here isn't to stop hiring. The company genuinely needed more crews, and most growing businesses genuinely need more people at some point. The useful move is to ask a sharper question before the next person joins: will this hire carry a result, or will this hire return questions to me that I haven't yet answered for anyone?
That question has a concrete answer once the missing pieces are written down rather than left as something only the founder can feel. A specific, checkable description of what "done" looks like on a standard office clean, short enough to fit on one page, removes the need for seven separate extrapolations from watching her work. A short list of decisions a team lead can make without checking, a minor schedule adjustment, a small discount for a missed spot, which supply substitution is acceptable, removes most of the calls that currently default to her by habit rather than necessity. A named threshold for what genuinely needs escalation, rather than a vague sense that anything unusual probably does, stops team leads from calling about things they were already equipped to decide on their own.
None of that work happens automatically because headcount increased. It has to happen before headcount increases, or the next hire simply inherits the same gap the last one did, and the business gets heavier again.
Before the next job ad goes up
A few questions worth running honestly against whatever hiring is currently planned or already underway.
Can you describe, in writing, what "done well" looks like for the role you're about to hire into, specific enough that someone could check their own work against it without asking you?
Which decisions will this person be allowed to make without checking with you first, and have you actually said that out loud, or only assumed it will become obvious over time?
If you hired three more people exactly like your last hire, would your week get lighter or heavier?
Growth Didn't Create the Weight. It Just Made It Visible Faster
None of this is an argument against hiring, or a case for waiting until every standard is perfectly documented before anyone joins a team. Early in most businesses, that documentation doesn't exist yet because the founder hasn't learned what actually matters well enough to write it down.
The point that matters is narrower: more staff is not the same intervention as more capability. Treating a capacity problem as the whole problem, without asking whether the standards, decision rights, and information a new hire needs already exist, means every additional hire adds weight somewhere in the business, usually back onto the one person who was already carrying too much of it.
A business that hires into a defined role gets lighter with every person added. A business that hires into an undefined one gets heavier, no matter how good the people are.
If you're sizing up a hiring plan right now and wondering honestly which kind of hire you're about to make, share this with a founder who's about to post the same job ad you are. It's a cheaper conversation to have before the offer goes out than after.


"It hasn't built a team. It has built a queue" is such a clear way to put it. The first question in your checklist is the one I'd start with too, because the page that tells a new hire what "done well" looks like is also the thing you should interview against. Without it, every interviewer judges the candidate against their own idea of the job, and you add rounds trying to agree. I'd add one step before the job ad goes up: pick the two or three decisions this person will own from day one, and ask every candidate about a time they made a call like that. How do you get founders to write the standard down when they're already too stretched to breathe?