The Playbook Nobody Writes

I almost missed my daughter's basketball game because I was the only person who could do the thing that had to get done that night.

Not a complex thing. A routine one. The kind that has a right answer, the same right answer every time, that I'd run dozens of times and never once written down.

That's the trap I almost talked myself into ignoring: I was the system. And a system that lives in one person doesn't scale. It just gets more tired.

There's a version of this playing out inside a lot of businesses right now. The owner, management, or team, are capable. Revenue is climbing. And the whole operation runs on a combination of tribal knowledge, habit, or one person in an area of the business holding the keys.

It works until it doesn't.

What I've noticed, working with operators across a range of industries, is that there's a specific ceiling most companies hit somewhere between $5M and $40M, then again at $150M, and again at higher levels. Growth slows. The company is busier than ever but the business isn't actually moving faster.

When I dig into it, it almost always comes back to the same thing.

No one ever built the operating manual.

Not a formal handbook. Not a 200-page policy document. I mean the practical, step-by-step record of how good work actually gets done. The stuff that lives in someone's head. The way the best version of a task gets handled. How a decision gets made on a Thursday afternoon. What happens when something escalates and the usual person isn't available.

That knowledge is locked inside individuals. And the moment any one of them has a bad month, or just a bad Tuesday, it doesn't get done the same way.

I call this the Spray Paint Problem.

Imagine you need to paint the same pattern on a hundred walls. You can hire a talented artist for each one and hope they paint roughly the same thing. Or you build a stencil once, hand it to anyone, and get the same result every time.

The stencil is your playbook. The talented artist is what you're relying on now.

Building the stencil isn't as complicated as it sounds. Do the thing you need to document while recording yourself doing it. Narrate as you go. Hand the recording to someone and say: turn this into a checklist I can give the next person. Fifteen, twenty minutes. What you get back is knowledge that no longer lives only in your head.

The objection I hear constantly: "We don't have time to build systems right now."

Not having time to build systems is the reason you don't have time. The two are the same problem. Every hour you spend being the only one who can do something is an hour you spend because you never built the system.

The other one: "Our business is too complex to systematize."

Every person I've heard say that had a business that wasn't actually that complex. What they had was a belief that their judgment was the special ingredient, and they hadn't figured out how to document judgment yet. You can. It just takes capturing the decision criteria, not only the steps.

The companies that scale past their plateaus aren't smarter than the ones who are stuck. They figured out how to encode what works, so the business stopped depending on memory.

They built the stencil.

I made it to the basketball game, for the record. She hit three threes in the first half. Worth every minute.

The task I almost stayed late for? I did it once more, recorded myself doing it, and turned it into something I'll never have to be the only one to do again.

That's the math that compounds.

THIS WEEK'S KEY QUESTION

Where is your business relying on memory instead of a system? Pick one recurring thing that lives only in someone's head, yours or someone else's, and use the recording method this week.

Don't build the whole manual. Build one stencil. See what it does for your next two weeks.

-N.F