Unpopular opinion: your procedures manual is the reason nobody follows your procedures

You spent weeks writing the manual. Nobody's opened it since, and your team still rings you to ask how to do the job.

Maybe it was a big push after something went wrong. Maybe an auditor, an insurer or a customer asked for it. Either way, it's sitting in a folder somewhere, 30 or 40 pages long, and it hasn't changed how a single job gets done.

Sound familiar? So you've decided your staff just don't follow procedures. Or you've decided it's COMMON SENSE and they should know it by now.

Here's the unpopular part. Most of the time, the procedure is the problem. It was written in a way nobody on the job could use.

This post is for owners with a team who keep getting asked the same questions. If you're a one-person business, start with What systems does a solopreneur actually need? instead.

What is a standard operating procedure?

A standard operating procedure, or SOP, is the written steps for doing a job the same way every time, so the result doesn't depend on who's doing it.

That's it. It doesn't need to be long, formal or written in policy language. It needs to help the person doing the job get it right, without ringing you.

When procedures work, the business stops living in your head. That's the whole reason to have them. I wrote about why everything comes back to the owner in You hired staff. So why does everything still come back to you?

Why don't staff follow procedures?

Usually it's one of these.

They're too long. Nobody reads 30 pages on a job site, or in the middle of a busy day. If the answer is on page 17, they'll ring you instead.

They were written by the owner, for the owner. They make sense to you because you already know the job. To someone new, half the steps are missing.

They live where nobody looks. A folder on your laptop or a binder in the office is no use to someone standing in front of the job.

They're out of date. The job changed two years ago. The procedure didn't. Your team worked out it's wrong and stopped trusting it.

Nobody checks. If following the procedure and ignoring it get the same reaction, people do it their own way.

Nobody knows why it matters. People skip steps that look pointless. Most steps are there for a reason. The reason just never got written down.

What makes a procedure people actually use?

Atul Gawande wrote The Checklist Manifesto about checklists in surgery, aviation and construction. These are people who are highly trained, under pressure, doing complex work. What he found is that the checklists that work are short, cover the steps people tend to skip, and are used at the moment the job's being done.

The ones that fail are long, try to cover everything, and sit in a drawer.

The same goes for your business. A procedure people use has six things.

  1. It fits on one page. If it can't, it's two jobs. Split it.
  2. It's written with the person who does the job. They know the steps you've forgotten you do. They also know the shortcuts that work.
  3. It lives where the job happens. On their phone, on the wall, or inside the job in your job software.
  4. It says why in one line. "Check the seal before you start, because a leak means redoing the whole job" gets followed. "Check the seal" gets skipped.
  5. It says what done looks like. A photo, a reading, a signature. Something you can check.
  6. It has an owner and a review date. One person is responsible for keeping it right, and it gets looked at on a set date, not when something goes wrong.

In my business we've moved from documents nobody opened to a library of one-page procedures, kept in one place, named the same way. It isn't finished. But when someone asks how a job's done and there's a one-pager for it, the answer is a link instead of a phone call.

Is it the procedures, or something else? My free quiz, Why does everything still come back to you?, shows you why your team brings you everything. Sometimes it's missing procedures. Sometimes it's something else entirely.

Which procedures should you write first?

Don't try to write them all. You'll get halfway, the business will get busy, and the half-finished folder becomes another thing that makes you feel bad.

Start with three.

  • The job that comes back to you most. Count the questions for a week. The top one goes first.
  • The job where a mistake costs the most. Money, safety, a customer you can't afford to lose.
  • The job a new starter does in their first week. That one pays off every time you hire.

Write one a week. In three months you'll have twelve, and they'll be the twelve that matter.

The how-to is in If it's longer than a page, nobody's reading it. If you'd like AI to do the typing while you talk it through, I explain how in Write the job down before you open the AI.

How do you get your team to actually use them?

Writing it is half the job. Getting it used is the other half.

Build them into induction. New starters learn the job from the procedure, with someone checking. Then it's normal from day one. More in Your new starter's first week shouldn't depend on you.

Point to the procedure when someone asks. When the question comes, send the one-pager back instead of the answer. It feels slower the first few times. Then the questions stop.

Check the "done" part. If the procedure says take a photo, look at the photos. People do what gets checked.

Change it when they tell you it's wrong. If your team says a step doesn't work, believe them, test it, and update the page. That's how they learn the procedures are real.

Put them where the job is. If your team uses job software, attach the procedure to the job. I wrote about why job software so often falls short in 5 signs your team isn't really using your job software. For checks at the start of a shift, see The prestart checklist nobody fills in properly.

What do you do with the manual you've already got?

Don't bin it. There's good stuff in there.

Go through it and pull out each job as its own one-pager. Throw out the policy waffle, keep the steps, add the why, and put each page where the job happens. Then file them so anyone can find them. Where does your business actually live? covers that.

The big manual can stay for the auditor. The one-pagers are for your team.

Do you need special software?

No. A shared drive with a clear folder structure, a template, and a phone your team already carries is enough to start. Software can come later, once you know what you need.

What matters is the habit: the job gets written down, kept in one place, and used.

What to do next

Find out what's really going on. Take my free quiz, Why does everything still come back to you?. It shows you why the questions keep landing on you, and gives you something to fix it with straight away.

Want someone to work through it with you? The BAR is where owners with staff work out what to fix first, find the time to do it, and get held to it. It opens in February 2027. Join the waitlist.

HI, I'M SAM

I've co-run a field service business for 22 years and served 12 years in the Navy. Now I help solopreneurs get the back-end stuff done, the money, systems, marketing and AI, so they get their weekend back.

NOT SURE WHAT'S SLIPPING?

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore.

+123-456-7890000

Newsletter

Subscribe now to get daily updates.

Created with © systeme.io