ATTENTION, PEOPLE WITH EIGHT DIRECT REPORTS AND ONE CALENDAR THAT HAS STARTED BITING!
PEOPLE WHOSE TEAM CAN DO ABSOLUTELY ANYTHING EXCEPT DECIDE WHO IS ALLOWED TO DECIDE IT! PEOPLE WHO HAVE BECOME THE HUMAN ESCALATION PATH FOR A QUESTION ABOUT A SPREADSHEET TAB!
Are you tired of not being copied on every message?
Have you spent another week discovering that the thing blocking six people was a decision only you were allowed to make, which nobody told you about, because you were in a meeting about a different one?
Then congratulations.
You qualify for the Five Number One Rules of Being the Manager Without Being the Bottleneck — five Number Ones, no inspirational cardigan, and no requirement to become a mystical lake person who “empowers” everyone by disappearing.
“Wait,” you’re shouting at the screen, “they can’t all be Number One!”
That’s exactly what Big Numbering wants, while it sells you a personality trait as an operating model.
These failures are specialists.
Ownership stops a decision stalling — but it doesn’t create capacity.
Delegation creates capacity — but it doesn’t surface information you never receive.
Dialogue surfaces that information — but it doesn’t tell anybody what their discretion is for.
Standards guide discretion — but they won’t reveal a system that only survives because you keep performing an emergency extraction in business casual.
One magnificent manager can cover one gap for a while. That isn’t a team that can act. That’s a single point of failure with good reviews.
So here they are.
Five rules.
Five Number Ones.
No substitutions. No waiting for the manager to bless a comma. No heroic inbox archaeology mistaken for leadership.
RULE #1: MAKE THE DECISION OWNER VISIBLE
Introducing COMMITTEE-FOG™, the revolutionary decision process in which everyone is invited, everyone is consulted, and everyone leaves believing somebody else has the final call.
When a decision is stuck, name the roles before anybody argues the merits.
DACI gives you four. The Driver scopes it, gathers what’s needed, and gets it made by an agreed date. The Approver — one person — has the final call. Contributors bring expertise and recommendations, and do not vote. Informed people find out afterwards.
The word doing all the work there is one.
A group can contribute. A group can execute. A group can care enormously and produce a very crowded calendar invitation. A final decision still needs a single owner.
That isn’t a worship service for hierarchy. It’s the antidote to diffuse accountability — the state where a decision looks collective and therefore belongs to nobody, which is also the state where it can quietly not happen for five weeks.
Use DACI on a decision, not as a general organisational tattoo. RACI covers execution across a group. An approval-authority table handles spending limits. DACI does one thing: it names the Approver at the moment of the actual call.
A decision with many voices may be wise. A decision with no named closer is merely well-attended.
The meeting isn’t over because the room got tired. It’s over because the Approver decided.
RULE #1: DELEGATE THE OUTCOME WITH A BOUNDARY
NOW AVAILABLE: MICROMANAGE-A-TRON DELUXE!
From the makers of “I delegated it, then requested endless previews” comes the product that converts any capable report into an exceptionally expensive pair of hands.
Delegation is not a mood.
State who decides. State the outcome you want. State the boundary that’s actually real. State when you need to hear something.
Then make the authority match the sentence, which is the part that usually fails.
Delegation Poker is useful here because it names seven distinct commitments where most people have two: Tell, Sell, Consult, Agree, Advise, Inquire, Delegate. Tell means you decide and announce. Sell means you decide and explain. Consult gathers input before you decide. Agree is joint. Advise is your non-binding input on their call. Inquire means they decide and tell you after. Delegate means they decide, full stop.
Those aren’t seven decorative synonyms for collaboration.
Have the manager and the report each pick a card for a decision category before the work starts. A mismatch tells you the two of you have been operating different theories of who owns this.
Delegate in theory plus Consult in practice isn’t delegation. It’s a person being asked to carry responsibility they were never actually handed.
Situational Leadership offers a second useful prompt, with one honest caveat. Its enduring insight is to reassess competence and willingness per task — somebody can be entirely capable on familiar work and genuinely new to something adjacent. Its specific style-to-readiness mapping, though, didn’t hold up in direct tests in 1987 or 1997. Use it to ask a better question, not to outsource the judgment to a quadrant.
The boundary itself is what military doctrine calls mission command: give somebody the intent and enough limits that they can act when the detailed order can’t arrive in time. The German Reichswehr built that capacity between 1919 and 1935 through sustained training — which is the part everyone skips.
Decentralised execution doesn’t rest on a better-worded message. It rests on prepared judgment plus clear intent.
Delegate the result and the boundary. Keep the rescue rope, not the puppet strings.
If every decision comes back for the manager’s fingerprints, delegation has been quietly replaced by remote-control labour.
RULE #1: RUN ONE-ON-ONES FOR INFORMATION YOU DO NOT HAVE
BEHOLD STATUS-REPORT-O-RAMA™ — the meeting where a manager reads a dashboard aloud to the people who filled it in, then wonders why nobody mentioned the problem hiding behind the green square.
A working one-on-one is not a manager broadcast, a performance ritual, or a weekly live-action reading of the project tracker.
The report brings the topics. The report keeps the running document between meetings.
That convention isn’t politeness. It’s what makes the meeting capable of surfacing the thing you don’t have: a dependency, a customer signal, an ambiguous decision, a conflict forming, a risk still too small to escalate formally — which is exactly when you want it.
Andy Grove framed the interval as insurance against a problem outgrowing informal disclosure. Shorter for someone newer or less independent. Longer for someone proven. Weekly and biweekly are the conventions, usually 30 to 60 minutes, and the right answer depends on how interdependent the work is.
Be honest about the evidence, though. There’s no comparably sized study isolating weekly against biweekly one-on-ones for retention or performance. Cadence is argued practice, not a measured result. The nearest real number is Gallup’s: about three in ten U.S. workers strongly agree their opinions count at work, and moving that ratio toward six in ten is associated with 27% lower turnover and 12% higher productivity.
That’s about being heard. It isn’t proof that an appointment causes anything.
Treat the meeting as close to non-cancellable. When it’s the first thing dropped from a crowded week, it announces that local information is optional right up until it becomes an emergency — and people believe you.
Take fewer notes than the report expects, or the meeting becomes a transcription service with your name on it.
The manager’s unknowns do not disappear because the dashboard has no column for them.
A one-on-one isn’t a status meeting with better coffee. It’s an information sensor with a human interface.
RULE #1: SET THE STANDARD BEFORE THE EMERGENCY
AND NOW, from the makers of “WE’LL FIGURE OUT WHAT GOOD LOOKS LIKE AFTER THE QUARTER,” comes CRISIS-VALUES EXPRESS™ — discover your principles at maximum heart rate, while everybody asks whether the principle includes this particular exception.
State the standard before a crisis comes asking for one.
A standard tells people how to execute a role. A principle tells them what to protect when the exact case wasn’t in the manual. Both reduce how much discretion has to be invented under pressure, which is the worst possible moment to be inventing any.
Bill Walsh’s Standard of Performance is the clearest example of the form. The 49ers had gone 2–14 before he arrived. His first season was also 2–14. The second was 6–10. By 1981 they won the Super Bowl, and two more followed.
The record doesn’t isolate the standard’s effect — Montana and Rice arrived during that window, and it would be dishonest to pretend otherwise. What it demonstrates is the shape: specify component behaviour down to a lineman’s stance, not just the scoreboard.
The same architecture works nowhere near a football field. In September 1982, seven Chicago-area deaths were traced to cyanide-laced Tylenol capsules. Johnson & Johnson recalled roughly 31 million bottles nationwide inside about a week, halted production and advertising, and offered exchanges — with no legal obligation to recall a product contaminated after it left the factory.
Its one-page credo, written in 1943, put responsibility to the people using its products ahead of shareholders. That ordering already existed. Which is the only reason it was usable at speed.
State the outcome. State the boundary that can’t be crossed. State the principle that settles a trade-off. Then train against it enough that somebody can act while you’re unreachable, instead of waiting for a full screenplay for a scene nobody foresaw.
A value becomes a management tool only when it can decide something expensive.
The standard arrives before the smoke. Otherwise it’s just a retrospective caption.
RULE #1: REVIEW THE SYSTEM, NOT JUST THE HEROICS
THIS IS THE ONE THEY TRIED TO HIDE BEHIND A PLAQUE READING “CLUTCH.”
Introducing RESCUE-LOOP PRO™, in which every preventable failure becomes fresh proof that the manager is indispensable, because the manager prevented the failure from becoming worse.
When you save a project, take the win. Then look hard at what it had to save.
Was there a named Approver?
Did the Driver get the call made by the agreed date?
Did the report have Delegate authority in words and Consult treatment in practice?
Did a one-on-one surface the local information in time?
Was the intent clear enough for somebody to act without you?
A heroic recovery can be genuinely valuable. It’s also diagnostic evidence, and it’s the only kind that arrives pre-labelled.
Resist the urge to fix this with the org chart. Rajan and Wulf studied more than 300 large U.S. firms from 1986 to 1999 and found CEO direct reports rising while layers fell. GE dismantled a nine-layer structure as headcount dropped from 411,000 in 1980 to 299,000 in 1985. Those are patterns, not permission to delete a layer because a diagram looked crowded.
Review the mechanism instead. Delegation research broadly correlates more delegation with motivation, trust, commitment and task performance — correlates, which is not the same as a universal causal prescription. And leadership research warns specifically against the charisma-only rescue story: transformational behaviours correlate strongly with rated effectiveness, but many of those studies ask the same follower to rate both, which inflates the result.
A system gets stronger when the manager asks what conditions made the rescue necessary. Not when the manager makes another speech about personal stamina.
The same audit covers succession, which is the version of this problem that arrives with no warning. In one Canadian survey of small and medium business owners, 10% had a formal written succession plan, 38% had an informal one, and 52% had nothing at all.
A team that only works through one heroic manager hasn’t solved the management problem. It has booked a future absence and declined to open the invitation.
Heroics are a fine response to an emergency and a terrible specification for normal operations.
If the rescue keeps recurring, the system is asking to be redesigned, in a very loud voice.
BUT WAIT, THERE’S MORE!
“What if the team is tiny?”
Same rules. A small team still needs a named decision owner, an explicit delegation level, a route for local information, a stated standard, and a look at recurring rescues. The names can be lighter. The architecture can’t.
“What if the work is creative and nobody can specify every move?”
Same rules. Commander’s intent exists precisely for conditions where a detailed order can’t anticipate the case. Set the outcome and the boundary. Don’t confuse a standard with a screenplay.
“What if the report is new?”
Same rules. Shorten the interval, make the delegation level explicit for the task. Being new at one thing doesn’t permanently define readiness at everything.
“What if the emergency genuinely requires me to take over?”
Same rules. Take over when the boundary demands it — then review why the system couldn’t carry the intent without you.
The details change.
The architecture doesn’t.
THE FIVE, WITHOUT THE CARDIGAN
Make the decision owner visible. One Driver, one Approver, named Contributors, and everyone else Informed.
Delegate the outcome with a boundary. Authority level, intended result, real limits, and report-back expectation — all agreed before the work starts.
Run one-on-ones for the information you don’t have. Their agenda, their topics, your unknowns.
Set the standard before the emergency, so discretion doesn’t have to be invented at speed.
Review the system, not the heroics. Treat every recurring rescue as evidence about decision rights, information flow, intent, and succession.
DO THIS TONIGHT, BEFORE THE CALENDAR EATS ANOTHER AFTERNOON
Find the decision currently circling like a shopping cart with one bad wheel.
Write its DACI. Who Drives, who Approves, who Contributes, who’s merely Informed.
If two people think they hold the final call, resolve that before anybody builds another deck. If nobody claims it, assign one Approver and a date, tonight.
Then take one recurring category of work and run the cards. You pick a number. Your report picks a number. Compare them before either of you explains.
If the cards differ, you’ve found the work. That gap has probably been costing you both something for months.
Open each report’s running agenda and protect the next meeting. Ask the three questions the dashboard can’t: what don’t I know, what decision is ambiguous, and what gets expensive if nobody sees it early?
Finally, write one standard that could survive your absence. The outcome. The boundary nobody crosses. The principle that settles the trade-off when both options are defensible.
Then after the next rescue — and there will be one — go looking for which of the five was missing.
For the low, low price of refusing to be the world’s most exhausted routing layer, the complete Five Number One Manager System is yours.
No subscription. No charisma serum. No laminated card reading “DELEGATE” while every decision waits in your inbox.
Just a team that knows who decides, what can move, what has to be said out loud, what good looks like, and what a rescue is trying to tell everybody.
Operators are no longer standing by.
The operator is the team when the manager is not in the room.