SOP optimisation and continuous improvement: the complete guide

A good standard operating procedure is short, accurate and used. Many organisations have the opposite: thick manuals written for an audit years ago, stored in a shared drive nobody opens, describing a process that has since changed. Meanwhile, the real knowledge of how to do the work well sits in the heads of a few experienced people, and leaves when they do.

This guide draws on the briefings in our improvement series. It sets out how to turn what your best people do into clear procedures, link those procedures to measures, and set up the improvement routines that keep them alive. It applies to offices, warehouses, laboratories and production lines alike.

Why most SOPs go unread

Procedures are ignored for predictable reasons. They are too long, written in formal language that does not match how people talk about the work, and stored far from where the work happens. They describe the ideal rather than reality, so experienced staff know they are wrong and new staff learn by watching colleagues instead.

The fix is to make procedures short, visual and part of the work itself. Use the words operators use. Put steps in order, with one action per line. Replace paragraphs with photos, diagrams and checklists wherever possible. And put the procedure where the work happens: at the workstation, on a tablet beside the machine or inside the system screen where the task is done. A procedure in a drawer will not be used.

Capture how the best people work

The best performers often have shortcuts and habits that make the work faster, safer or more accurate. Capturing them raises the standard for everyone. The approach is simple, but it takes time on the floor rather than at a desk.

1. Observe. Watch several people do the same task and note the differences in sequence, tools and checks.
2. Ask why. Understand the reason behind each variation before deciding which is best; some apparent shortcuts hide real risks.
3. Agree the standard. With the people who do the work, choose the best way and write it down.
4. Test it. Have someone unfamiliar with the task follow the draft and note where they hesitate.
5. Train and publish. Teach the standard, place it where the work happens and record who has been trained.

Involving the people who do the work is not just courtesy. They will spot steps the observer missed, and they are far more likely to follow a procedure they helped to write.

Video can help for complex or physical tasks. A two-minute clip of an experienced operator changing a tool or packing a fragile order, with a short narration of what to watch for, often teaches more than several pages of text. Keep clips short, focused on one task and stored alongside the written procedure so that both are updated together.

Write SOPs people will use

Good procedures share a common structure: a clear purpose, named owners, defined inputs and outputs, the steps themselves, and what to do when something goes wrong. Exceptions matter, because that is when people most need guidance and are most likely to improvise.

Digital procedures work best. Placing SOPs inside your business systems or intranet puts them where people already work, makes updates instant and lets you see which procedures are actually opened. Where regulation applies, as in food, medical devices or financial services, align SOPs with ISO-style quality systems and the relevant regulatory expectations, so the same documents serve operations and audit.

Link SOPs to measures

A procedure tells people how to do the work; measures tell everyone whether it is working. Attach a few key indicators to each important process, such as accuracy, cycle time or first-time-right rate, with simple dashboards that show performance by team and site.

Keep the measures few and visible. A typical warehouse team might track pick accuracy, orders shipped on time and safety incidents on a board at the start of the shift. When a number moves, the team can look first at whether the procedure was followed and then at whether the procedure itself needs changing.

Avoid using the measures to blame individuals. When a number is used to find someone at fault, people learn to hide problems rather than raise them. The aim is to show where the process or the procedure needs attention, and to give the team the information to fix it themselves.

Standard work enables improvement

You cannot improve what is done a dozen different ways. If every shift follows its own method, there is no baseline against which to judge a change. Standards give you that baseline.

The cycle is straightforward. Define the baseline: agree one way of working and measure it. Test changes against it: when someone has an idea, try it on a small scale and compare the results. Update the standard: when a better way is proven, change the procedure, retrain and tell everyone why. Over time, the standard becomes a record of everything the organisation has learned about doing the work well.

Run daily huddles and improvement cycles

Lean routines keep procedures alive. The simplest and most effective is a short daily huddle: ten minutes, standing at the workplace, in front of a board.

• Keep it short and structured: yesterday’s results, today’s plan, and any blockers.
• Track a few measures: safety, quality, delivery and one measure the team chooses.
• Assign actions to named people and check them the next day.
• Escalate what the team cannot fix, and report back when it is resolved.

Beyond the huddle, hold a short root-cause review whenever a significant problem recurs, and encourage small experiments rather than waiting for large projects. Most improvement comes from many small changes, each tested and adopted into the standard.

The huddle board did more for quality than the new manual. People could see the numbers every morning, and the fixes came from them.

Site manager, food production client

Keep procedures owned and current

SOPs decay without owners. Assign an owner and a review date to every procedure, and make reviews part of the routine rather than a scramble before an audit. Retire procedures that are no longer used, and merge those that overlap. The trade-off is time: reviews take effort from busy supervisors. Keeping procedures short makes reviews quick, which is another reason to resist long documents.

Done well, the work delivers consistent quality whoever does the job, faster onboarding for new staff, clear and current records for audit, and a culture of small, steady gains. Start by choosing the five tasks where errors or variation cause the most trouble, observe your best people doing them, and rewrite each procedure on a single page.

Source: Intelliversal analysis, drawing on the briefings in this series.

Frequently asked questions

How long should an SOP be?

As short as possible while still being complete. For frequent tasks, one page with photographs or a checklist is usually enough; detailed background belongs in training material.

How often should procedures be reviewed?

At least annually, and whenever the process, equipment or system changes. High-risk or regulated procedures may need more frequent review.

Who should write SOPs?

The people who do the work, supported by someone skilled in clear writing and accountable to a named process owner. Procedures written only by managers or consultants are less likely to be followed.

Explore SOP optimisation and continuous improvement