Your new hire is sharp, eager and three days in. And for three days, they've been following you around.
Every few minutes: "How do you want this done?" "Where's the template for that?" "What do we do when the customer says…?" You answer every question patiently, because it's faster than explaining where to look. There's nowhere to look. It's all in your head.
Then you remember: you actually tried to fix this once. A consultant, or a slow winter, or a burst of motivation produced a binder of procedures. Fifty pages. It's on a shelf somewhere. Nobody has opened it in two years, including you.
Why most procedures fail
The problem was never that your business can't be documented. It's that most documentation is written for the wrong reader.
Binders and manuals are written to be complete. Playbooks are written to be used. A busy person in the middle of a job won't read ten pages. They'll read one, if the answer to their question is on it, and if they can find it in under a minute.
Most procedure projects fail for the same few reasons:
- Too long. Nobody reads a 12-page process while a customer is waiting.
- Written by the owner, alone. You know the work too well to see the steps a new person misses.
- Written once, never updated. The first time it's wrong, people stop trusting it.
- Stored somewhere nobody looks. A binder on a shelf, a folder three levels deep.
- Describes tasks, not standards. It says what to do, but not what "done right" looks like, so people still ask you.
Playbooks are how you leave the building
If you've worked through The Owner Bottleneck, you sorted your Decision Log into four boxes. Two of them, teach and systematize and document it, are playbook territory. Every playbook you write is one less question that has to come to you.
And here's the bigger reason playbooks matter: they're how the knowledge in your head becomes an asset the business owns. A buyer will pay more for a business that runs on documented systems than for one that runs on its owner's memory. We'll come back to that in What Makes a Small Business Sellable?
The free tool: a one-page playbook format
Every playbook gets one page. If it needs more, it's probably two playbooks.
| Section | What goes here | Example: "Quoting a repeat customer job" |
|---|---|---|
| Outcome | What this playbook produces | An accurate quote sent within one business day |
| When to use it | The trigger | A repeat customer requests a quote for standard work |
| Owner | One name or role | Office manager |
| What "done right" looks like | The standard, so nobody has to ask you | Uses current price guide, minimum margin met, sent same or next day, follow-up scheduled |
| Steps | Ten or fewer, in order | 1. Pull customer history. 2. Open price guide… |
| Decisions and limits | What they can decide on their own | Discounts up to 5%; anything outside the price guide goes to the owner |
| Common mistakes | What usually goes wrong | Forgetting travel time; using last year's prices |
| Tools and links | Templates, logins, files | Quote template, price guide, CRM link |
| Last updated | Date and name | Date / who |
That "decisions and limits" line is what separates a playbook from a to-do list. It's where you write down the guardrails from How to Delegate Decisions, Not Just Tasks, so the person running the playbook doesn't need to come back to you at every fork in the road.
Which playbooks to write first
Don't try to document the whole business. Start where it pays off fastest:
- The questions you answer most. Your Decision Log will show them. If you answered it five times last week, it needs a playbook.
- The work that breaks when you're gone. What stalls on your vacation?
- The work that's done inconsistently. If three people do it three different ways, customers notice.
- The work you'll hire for next. A playbook turns a new hire's first month into their first week.
Three playbooks this month beats thirty "someday."
How to write a playbook in 30 minutes
Writing from a blank page is slow and painful. Don't do it. Capture the work as it happens instead:
- Do the work and record it. Narrate out loud while you do the task, on a phone voice memo or a screen recording. Explain why as well as what: "I check last year's job first because customers remember what they paid."
- Turn the recording into a draft. Have it transcribed, then ask an AI assistant to turn the transcript into the one-page format above. This is exactly the kind of work AI tools do well, and it turns 30 minutes of talking into a usable first draft. (Never paste customer, employee or other private information into a tool your business hasn't approved.)
- Hand the draft to the person who'll do the work. Have them follow it, step by step, while you watch and say nothing. Every time they hesitate or ask a question, the playbook has a gap.
- Fix the gaps together. Let them edit it. People follow instructions they helped write.
- Store it where the work happens. A shared folder everyone can reach from their phone, a pinned page in your project tool, or a laminated page at the workstation. One place, clearly named.
Keep playbooks alive
A playbook is never finished. It's a living record of the best way your business knows how to do something, today.
- Every playbook has an owner who keeps it current, usually the person who does the work, not you.
- When a mistake happens, update the playbook, not just the person. "What would have prevented this?" usually becomes a new line on the page.
- Review on a rhythm. A quick quarterly pass catches outdated prices, tools and steps.
- Use it in training and in check-ins. When someone asks a question the playbook answers, point to it. When it doesn't, add the answer.
Over time, your team's questions shift from "How do I do this?" to "Should we change how we do this?" That's the sound of a business that's learning without you in the middle.
Where AI fits
Once you have a set of playbooks, they become even more useful. An AI assistant that's been given your playbooks can answer your team's "how do we…?" questions at any hour, using your standards instead of generic internet advice. That's one of the most practical first uses of AI in a small business, and we'll cover it in Where AI Fits in a Small Business.
Frequently asked questions
What's the difference between an SOP and a playbook? In practice, the terms overlap. A "playbook," as used here, is short (one page), outcome-focused, and includes the standard and the decision limits, so the person using it can finish the work without asking the owner.
How many SOPs does a small business need? Fewer than you think to start. Document the handful of processes that generate the most questions or break when you're gone, then add more as you hire and grow.
Who should write the playbooks? The owner explains the standard; the person who does the work drafts or edits the playbook. Recording and transcription, with AI help, make the first draft fast.
How do I get my team to actually use them? Keep them to one page, store them where the work happens, and point to them every time someone asks a question they answer.
Back to the new hire
Picture that new hire again, three days in. This time they're not following you around. They've got a short folder of one-page playbooks for the work they're learning. When they hit a question, they check the page. When the page doesn't have the answer, they write the question down for your Friday check-in, and the playbook gets better.
The next time a new person asks you, "How do you want this done?", notice it. That question is a playbook waiting to be written. Record yourself answering it, and you'll never have to answer it again.
Go further: build your delegation and AI role plan with Greg
This guide gives you the one-page playbook format. In The Great American Business Owner Workshop, you'll turn what lives in your head into a delegation and AI role plan: which work goes to people, which goes to AI assistants, and the first playbooks that make it run, as part of your 90-Day Owner Plan.
Not ready for the workshop? Take the 3-minute Owner Scorecard.
Previous guide: The 13-Week Cash Flow Forecast · Next guide: Where AI Fits in a Small Business
Related: The Owner Bottleneck · How to Delegate Decisions, Not Just Tasks