By Matthew Boos
Every small business has at least one process that lives entirely inside one person’s head. The day that person leaves, you find out what it cost you.
As a small business owner, you have at least one. It’s the sequence for pricing a bid, the call that turns a complaint into a referral, or the trick for sequencing a crew so nobody stands around. It works and it lives in one place: inside your head alone.
The same execution risk sits in almost every small business, whether a plumbing company, an electrical firm, a paint contractor, or a structural engineering shop. You won’t find this risk on the balance sheet or buried in the backlog. You’ll find it in the recipe.
What happens if the chef doesn’t show up
If you think about your business as a kitchen, you are the chef who never writes anything down. Every dish depends on whatever is in your head. The day you are out, the line cook grabs the wrong recipe, the sauce breaks, tickets stack up, and the dining room notices fast.
It plays out like this when your estimator who has priced jobs by feel for fifteen years is gone for three weeks, or the project manager who knows how change orders get routed takes another job. The work does not stop. It just starts getting worse for weeks before you see it in the numbers.
You know this exists, so start by naming the processes that live only in your head or in one employee’s. Estimating logic? Vendor negotiation? Which jobs to walk away from? If “what happens when that person is out for a month” gets you a shrug from your team, you have found a real exposure. Knowledge that never gets written down disappears the moment that person walks out the door, and a smart successor does not fix that. You have to write down the recipe.
Why the binder on the shelf never gets opened
Some of you have already tried this. You may already have a binder or a shared drive folder labeled “SOPs” that nobody has opened since the consultant left. It’s the kitchen problem. If your team cannot understand the recipe, there is no point in writing it down.
A recipe that gets printed once and never touched again is not a real recipe. A working recipe lives on the counter, gets flour on it, and gets corrected when the original method does not survive a smaller oven. It earns trust because people use it and fix it often, not because it was written perfectly the first time. Your badge of honor is an SOP that has been worked, reworked, and reworked again when new information becomes available.
SOPs fail the same way. They get written for an audit, not for the person doing the work. “Coordinate with the customer on scheduling” is not a procedure. It is a wish. “Call the customer’s cell, confirm the arrival window in the CRM, send the confirmation text” is something a new hire can execute without guessing. The gap between a document that gets followed and one that gets ignored usually comes down to whether it was written for your newest hire or your most senior one. If you write for the rookie, you are covered at the top too.
The last reason binders die is ownership. When the SOP belongs to nobody, nobody updates it, nobody defends it when shortcuts creep in, and it goes stale within a quarter. A recipe nobody tastes now and then is a recipe that eventually causes problems. Every procedure needs one named person who notices when it stops matching reality.
Turning the recipe box into a working kitchen
In the businesses where SOPs actually run the day-to-day, a few things look different.
First, the recipe has to live where the work happens, not in some separate place the crew has to remember to check. If checking it takes longer than guessing, your team will guess. On a jobsite, that means the field checklist lives on the same tablet used for time tracking, not in a binder in the truck.
Second, it needs a trigger for updates, not a calendar reminder that gets ignored. Forget “we review this every January.” The real signal is “a tool changed, a code changed, a foreman found a better sequence, so we update it this week.” If you treat documentation as a one-time project, it goes stale. If you treat it as a habit, you catch drift before it costs you a callback or a change order fight.
Third, leadership needs to reward following the recipe instead of working around it. If a crew skips the safety walkthrough and still hits its numbers, and leadership stays silent, the message lands: results matter more than process. Good SOPs die exactly this way, while still technically in force.
Either you enforce the standard, or the crew learns to work around it. There is not much middle ground.
Start with the one that would hurt most
Do not document everything at once. Pick the process that would cost you most if the person holding it left tomorrow. Start there.
For most owners, that is estimating. It is the process most likely to live entirely in one person’s judgment, and a mistake there never shows up as a complaint. It shows up as margin quietly eroding on every job.
If your best estimator vanished tomorrow and someone half as experienced priced your next ten bids, what would that cost you by the end of the quarter? Run the actual number before you move on. This is why it matters, not some vague belief that you should have better SOPs.
Once you have picked the process, do not write it from memory. Memory is what got you here. Do the job the way you normally would and have someone else write down every step, including the shortcuts you do not think of as steps. Or record yourself talking through it, the way you would explain it to a new hire, and turn the recording into a checklist.
Then test it. Hand the draft to your newest hire and watch them try to follow it without asking a question. Every place they get stuck is a gap in the recipe, not in them. Fix the gaps and you have a working document. Skip that step and you have built another binder for the shelf.
Before anything else this week: pick the one process that scares you most to lose. Get it out of your head. Everything else here depends on that one existing.
What this buys you
None of this is about compliance. What it protects is gross margin, and your life, once the business stops running on one person’s memory.
The recipe in your head does not help anyone else. The one on the counter, tested, corrected, and used every day, is what separates owning a business from owning a job you can never leave.
