Standard Operating Procedures People Actually Follow

Twenty minutes into almost every engagement, a client tells me the same thing. “We have standard operating procedures for that.” Then someone opens a shared drive, scrolls past folders named “OLD,” “OLD 2,” and “Final FINAL,” and finally finds a Word document last edited three years ago by a person who no longer works there.

However, that document is not a procedure. It is an artifact. In fact, nobody on the floor has opened it since the week it was written, and when I ask the team how the task actually gets done, I get four different answers from four different people.

I have spent most of my career as an operations and process consultant walking into businesses like this one. For example, accounting firms, staffing agencies, marketing shops, IT service providers, and family companies that grew faster than their systems did. Interestingly, the problem is almost never that leaders don’t believe in standard operating procedures. On the contrary, they believe in them deeply. Still, they keep writing the kind nobody uses.

This article, therefore, is about the other kind. These are the standard operating procedures that live in the daily rhythm of the work, that new hires reach for without being told, and that experienced staff quietly defend when someone suggests skipping a step. Admittedly, they are not harder to write. Instead, they are written differently, owned differently, and placed differently. So here is how I build them with clients.

Why Most Standard Operating Procedures Die in a Shared Drive

Before fixing anything, it helps to understand why procedures fail. In my experience, the cause is rarely laziness or defiance. Rather, people ignore procedures for rational reasons.

The Five Reasons Procedures Get Ignored

The document describes a process that no longer exists. After all, work changes constantly. For instance, a new software tool arrives, a client asks for a different report format, or a manager reorganizes a team. Meanwhile, the written procedure stays frozen while the real procedure drifts. Consequently, after a few months, following the document would actually cause mistakes, so people stop following it, and they are right to.

It was written by the wrong person. Typically, a manager who hasn’t done the task in years sits down and writes how it should work. Then the people doing the job read it and immediately spot three steps that are wrong and two that are missing. As a result, trust in the whole document collapses on page one.

It is too long to use in the moment. For example, a twelve page procedure for processing a vendor invoice is not a reference tool. Instead, it is a reading assignment. Naturally, nobody stops in the middle of a busy afternoon to read twelve pages.

Nobody can find it. Similarly, if the procedure lives four clicks deep in a folder structure only the office manager understands, it may as well not exist.

There is no consequence for ignoring it and no reward for using it. Above all, when leadership never references the procedure, never updates it, and never asks whether it was followed, the team draws the obvious conclusion.

Adoption Is a Design Problem

Notice, however, that none of these failures are about writing quality in the usual sense. In other words, you can have beautifully formatted, grammatically perfect standard operating procedures that still go unused. Therefore, adoption is a design problem, not a documentation problem.

Build Standard Operating Procedures From the Work, Not a Template

The single biggest change I make with clients is reversing the order of operations. Usually, teams start by downloading a template, filling in the header fields, and then trying to describe the process. By contrast, I start by watching the process happen.

Watch Your Best Performer and Your Newest One

First, sit beside the person who does the task best and ask them to do it while talking out loud. Also, don’t interrupt. Take notes on everything, including the little things they do without thinking. For example, the sticky note on the monitor, the spreadsheet they keep open in a second tab, or the colleague they message every time a certain field comes up blank. In reality, those habits are the real procedure, because experienced people have quietly solved problems that the official process never addressed.

Next, sit beside someone who struggles with the task, or someone fairly new, and watch them too. Ultimately, the gap between these two observations is exactly where your procedure needs to do its heaviest lifting.

Narrow the Scope and Define Done

The writing guidance from ScreenSteps makes a point I agree with completely: narrow the scope. That is, one procedure should cover one task with one clear outcome. For instance, “client onboarding” is not a procedure, it’s a department. On the other hand, “setting up a new client in the billing system” is a procedure. Furthermore, when scope creeps, documents bloat, and bloated documents get ignored.

In addition, I ask one question before writing a single line: what does done look like? If the team can’t describe the finished outcome in a sentence, then the procedure isn’t ready to be written. In that case, the process itself needs fixing first, because documenting a broken process just makes the confusion official.

Write Standard Operating Procedures for the Person Doing the Job at 4:45 on a Friday

Picture who actually reads your procedure. Of course, it’s not a compliance auditor with a highlighter. Instead, it’s a tired employee near the end of the week, with a client waiting and a task they only do once a month. Above all, they need to get it right, quickly, and go home. Therefore, every writing decision should serve that person.

Rules for Writing Each Step in Your Standard Operating Procedures

Lead each step with a verb. For example: “Open the client record.” “Confirm the billing address.” “Attach the signed agreement.” Action words tell the reader exactly what to do. In contrast, sentences that begin with background explanation make people hunt for the instruction.

One action per step. Generally, if a step contains the word “and” twice, it is probably three steps. Splitting them, moreover, makes it far easier to pick up where you left off after an interruption, which in real offices happens constantly.

Put the reason in only where it prevents a mistake. Admittedly, most steps need no explanation. However, when a step looks pointless and people are tempted to skip it, add a single line on why it matters. For instance: “Check the tax ID against the W9 before saving. Mismatches block the first payment run.” In fact, that one sentence does more for compliance than a page of policy language.

Use the exact words on the screen. If the button says “Submit for Review,” then the procedure says “Submit for Review,” not “send it to your manager.” After all, people scan for matching words, so make the match easy.

Show the decision points clearly. Of course, real work branches. For example, if the client is international, do one thing. Likewise, if the invoice is over a certain amount, route it differently. Consequently, mark these forks plainly so nobody has to guess which path applies to them.

Write for the Newest Competent Person

Aim your writing at the newest competent person on the team. In other words, not a total beginner, and not the twenty year veteran. Indeed, TechTarget’s overview of SOP creation notes that procedures for experienced staff should differ from those written for new employees. Accordingly, I usually solve this with layers: a short core sequence anyone can follow, with links out to deeper detail for people who need it.

Run the Cold Read Test

Whenever I hand a draft to a client, I always run what I call the cold read. First, give the procedure to someone who has never done the task. Then watch them attempt it using only the document, and don’t help. Every place they hesitate, ask a question, or make an error is a place the procedure failed, not the person. Similarly, the Houston Chronicle’s small business guidance recommends exactly this kind of testing, first yourself and then with an employee. In my view, it remains the most valuable hour you will spend on any procedure.

Choose the Right Format for Your Standard Operating Procedures

Not every procedure should look the same. In fact, one of the quiet reasons standard operating procedures fail is that teams force every process into a single long template, even when the work itself calls for different shapes. For this reason, I generally use three formats.

Checklists for Short, Repeatable Work

Checklists suit work where skipping a step is the main risk. For example, opening procedures, month end close items, and client handoff confirmations. Essentially, a checklist assumes the person knows how to do each item and simply ensures nothing gets missed.

Moreover, the evidence for checklists is hard to argue with. In a study led by the Harvard School of Public Health with the World Health Organization, researchers tested a 19 item surgical safety checklist across eight hospitals in eight cities, including one here in Manila. As a result, major complications in the study operating rooms dropped from 11 percent at baseline to 7 percent once the checklist was introduced. Even more striking, inpatient deaths after major operations fell by more than 40 percent. Remember, these were skilled surgical teams. So the checklist didn’t teach them surgery. Instead, it caught the small omissions that expertise alone does not prevent. Likewise, your accounts payable team is no different in principle.

Step Sequences for Occasional Tasks

Step sequences, on the other hand, fit tasks someone does occasionally and needs to be walked through. These are the classic procedure: numbered actions, decision points, and expected results. Most likely, the majority of your library will live here.

Flowcharts for Branching Processes

Finally, flowcharts work best for processes with many branches or handoffs between people. For instance, when a task moves between three departments and depends on several conditions, a simple diagram often explains in seconds what paragraphs cannot. In addition, TechTarget points out that flowcharts are especially useful for showing who is responsible for each step, and that responsibility clarity is often the whole problem.

As a result, many of my clients end up with a blend: a one page flowchart showing the overall journey, linked to step sequences for each stage, with a checklist at the end to confirm completion. In short, the format follows the work, never the other way around.

Put Standard Operating Procedures Where the Work Happens

Location is the most underrated factor in whether standard operating procedures get used. Simply put, if a procedure takes longer to find than the task takes to complete, people will skip it every time.

One Click or One Glance Away

That is why the rule I give clients is simple: the procedure should be one click or one glance from the work.

In practice, for example, that looks like a link to the procedure pinned inside the project management tool, right on the recurring task card. Alternatively, it could be a laminated checklist at the shipping station, a link in the email template that kicks off client onboarding, or a short procedure embedded directly in the help field of a form. Likewise, for software heavy processes, short screen recordings work beautifully, provided they are kept brief and updated.

One Home for All Standard Operating Procedures, No Duplicates

Besides placement, I also push teams to consolidate. Ideally, that means one searchable home for all procedures, organized by role or by department, with consistent titles that start with the action. For instance: “Process a refund.” “Onboard a new contractor.” “Close a support ticket.” When titles follow a consistent pattern, people find what they need through search instead of through memory.

Finally, kill the duplicates. After all, nothing destroys trust faster than finding two versions of the same procedure that say different things. So archive old versions where people won’t stumble onto them, and keep a single live copy.

Give Your Standard Operating Procedures an Owner and a Pulse

Here is the uncomfortable truth: most procedures start dying the day they are published. Therefore, the only cure is ownership.

Specifically, every procedure in your library needs a named owner. Not a department, but a person. That person is responsible for keeping it accurate, answering questions about it, and approving changes. Ideally, they are someone close to the work, rather than three levels above it.

Of course, this isn’t a new idea. The United States Environmental Protection Agency has published detailed guidance on preparing standard operating procedures for decades. Notably, one of its consistent themes is that whenever a procedure changes, the written document should be modified and approved so policies stay current and appropriate. Indeed, regulated environments learned long ago that an outdated procedure is worse than none, because it gives false confidence.

Three Habits That Keep Standard Operating Procedures Current

A visible review date. First, put “Last reviewed” and “Next review” at the top of every procedure. When readers see a recent date, they trust the content. Conversely, when they see a date from 2022, they know to ask questions first.

A trigger list for updates. Beyond scheduled reviews, certain events should also prompt an update automatically. For example, a software change, a new client requirement, an audit finding, or a repeated mistake. In particular, if the same error happens twice, the procedure is the first place to look.

An easy way to flag problems. Lastly, give every reader a simple path to say “this step is wrong,” such as a comment field, a dedicated channel, or a short form. After all, the people doing the work will spot drift long before any scheduled review would catch it. Moreover, when they report a problem and see it fixed within a week, they become the procedure’s strongest defenders.

Build Adoption for Standard Operating Procedures Instead of Announcing Them

The most common rollout I see goes like this. First, a manager writes a batch of procedures. Then they send a company email announcing them and consider the job done. Yet six months later, nothing has changed. Clearly, adoption is built through use, not announcement.

Five Ways to Build Real Adoption

Involve the team in writing. When the people who do the work help create the procedure, they own it. Additionally, they catch errors before publication, which protects the document’s credibility from day one.

Train with the procedure in hand. In other words, don’t explain the process from memory and then mention that a document exists. Instead, train using the actual procedure, step by step, so people learn the work and the reference tool at the same time. Consequently, when they get stuck later, they already know exactly where to look.

Make leaders use it publicly. For example, when a manager answers a question by saying “let’s check the procedure,” it signals that the document matters. On the other hand, when a manager answers from memory and contradicts the document, it signals the opposite.

Start with pain, not policy. Initially, pick the processes that cause the most rework, complaints, or late nights, and document those first. That way, early wins build appetite for more. Otherwise, starting with low value processes just teaches people that procedures are busywork.

Frame procedures as freedom. Notably, Michael Gerber made this argument back in 1988 in The E-Myth: documented systems free people from constantly reinventing routine work. Similarly, good standard operating procedures handle the predictable so your people can spend their judgment on the unpredictable. As a result, when staff understand that the procedure exists to protect their time and reduce blame, resistance drops considerably.

How to Tell If Your Standard Operating Procedures Are Working

Of course, you can’t manage what you never check. Fortunately, a few simple signals tell you whether your procedures are earning their place.

Error rates on documented tasks. First, track mistakes before and after a procedure goes live. If errors don’t fall, then the procedure has a problem, either in content, format, or location.

Time to competence for new hires. Generally, good procedures shorten onboarding for new hires noticeably. So if new people still need weeks of shadowing for routine tasks, your library has gaps.

Questions to the same expert. In every business, there’s one person everyone asks. Therefore, count how often they get interrupted for routine questions. When procedures work, those interruptions fall, and consequently your expert gets their days back.

Usage data. Also, most knowledge platforms show page views. Procedures nobody opens are either unnecessary or invisible. Either way, act on it.

Feedback volume. Oddly enough, a procedure that gets regular correction requests is often a healthy one, because it means people are using it closely enough to notice when something is off. In contrast, silence usually means neglect.

A Simple Test Before You Publish Standard Operating Procedures

Before any procedure goes live with my clients, it has to pass five questions.

• Can someone new complete the task using only this document?
• Does it describe how the work actually happens today?
• Is it one click or one glance from where the work takes place?
• Does it have a named owner and a review date?
• Is it as short as it can possibly be while still being complete?

If the answer to any of these is no, then the procedure isn’t ready. So fix it first. Otherwise, publishing a flawed procedure teaches the team that procedures can’t be trusted, and that lesson takes a long time to unlearn.

Final Thoughts on Standard Operating Procedures

Ultimately, standard operating procedures are not paperwork. Instead, they are how a business remembers what it has learned. Every time someone figures out a better way to handle a tricky client, avoid a billing error, or speed up a handoff, that knowledge either gets captured or walks out the door when the person leaves.

In short, the businesses that get this right don’t write more procedures than everyone else. Rather, they write fewer, better ones. First, they watch the work before documenting it. Then they write for the tired person on Friday afternoon, put the procedure inside the workflow, give it an owner, and keep it alive. If you do those things consistently, you end up with something rare: standard operating procedures people actually follow, because following them is simply the easiest way to get the job done right.

Frequently Asked Questions About Standard Operating Procedures

What are standard operating procedures?

Standard operating procedures are written instructions for completing a routine task the same way every time, regardless of who performs it. As a result, they produce consistent, reliable outcomes. Learn more from TechTarget.

How long should standard operating procedures be?

Ideally, as short as possible while still being complete. Most effective procedures fit on one or two screens. However, if a procedure runs much longer, it usually covers more than one task and should be split. Learn more from ScreenSteps.

Who should write standard operating procedures?

The people who do the work should help write them, while a manager or process lead edits for clarity and consistency. Otherwise, procedures written only by managers often miss real steps and lose the team’s trust. Learn more from the Houston Chronicle.

How often should standard operating procedures be reviewed?

At least once a year, and also immediately whenever the process, tools, or requirements change. In addition, each procedure should show its last review date and have a named owner responsible for keeping it current. Learn more from the EPA’s SOP guidance.

What is the difference between a checklist and standard operating procedures?

A checklist confirms that every step was completed and assumes the person already knows how to do each one. In contrast, standard operating procedures explain how to do the steps. Therefore, many teams use both together. Learn more from Plane.

Do checklists really improve results?

Yes. In fact, a WHO and Harvard study found that a simple surgical checklist reduced major complications by more than a third across eight hospitals worldwide. Learn more from the Harvard T.H. Chan School of Public Health.

References

1. ScreenSteps. How to Write an SOP that Employees Can Easily Follow. https://blog.screensteps.com/write-standard-operating-procedure-sop
2. TechTarget. What is a Standard Operating Procedure (SOP)? https://www.techtarget.com/searchbusinessanalytics/definition/standard-operating-procedure-SOP
3. Houston Chronicle Small Business. How to Create a Standard Operating Procedure. https://smallbusiness.chron.com/create-standard-operating-procedure-1973.html
4. U.S. Environmental Protection Agency. Guidance for Preparing Standard Operating Procedures (EPA QA/G6). https://www.epa.gov/sites/default/files/2015-06/documents/g6-final.pdf
5. Harvard T.H. Chan School of Public Health. Hospital Sites Demonstrate Surgical Safety Checklist Drops Deaths and Complications. https://www.hsph.harvard.edu/news/press-releases/hospital-sites-demonstrate-surgical-safety-checklist-drops-deaths-and-complications/
6. Haynes AB, Gawande AA, et al. A Surgical Safety Checklist to Reduce Morbidity and Mortality in a Global Population. New England Journal of Medicine. https://www.nejm.org/doi/full/10.1056/NEJMsa0810119
7. Harvard Gazette. Surgical Safety Checklist Drops Deaths and Complications by More Than One Third. https://news.harvard.edu/gazette/story/2009/01/surgical-safety-checklist-drops-deaths-and-complications-by-more-than-one-third/
8. IndustryWeek. The Amazing Power of Checklists. https://www.industryweek.com/the-economy/article/22010925/the-amazing-power-of-checklists
9. ThinkAdvisor. Unchecked Growth. https://thinkadvisor.com/2011/08/24/unchecked-growth
10. Plane. What Is Process Documentation? Meaning, Types, and Best Practices. https://plane.so/blog/what-is-process-documentation-meaning-types-and-best-practices