Skip to main content

SOPs Need To Detail Each Step

One of the key features of an effective SOP (Standard Operating Procedure) is the ability to capture each step along the way. I worked with a great team yesterday and this was one of the things we discussed after attempting to write some SOPs.


It is clear that writing them in isolation prevents you from getting the most out of your SOPs. Having too narrow a focus on the instruction stops you from writing a well rounded document that anyone can pick up. Working with others can help to prevent this.

Assuming that everyone knows all of the bits in-between the steps you have outlined is a recipe for disaster. In many cases the SOP isn't for you, it is for the new person joining the team, who doesn't know the process or the background to the way your department works. The 'bits in-between' are therefore essential.

Don't worry about the length of the SOP either. Including all of the necessary details rarely bloats the document so that it is unusable. What is unusable is a SOP that is missing the right information.

Take the time required to write your SOPs to ensure that they are complete and useful. By getting someone else involved that isn't directly involved with the process you should be able to write a decent SOP pretty quickly. With a good set of SOPs behind you, you should be able to improve the productivity of your team and protect yourself (to some degree) if one of your team members leaves.


Giles Johnston
...fixing MRP systems and re-engineering business processes

Popular posts from this blog

Where there is a (performance) gap there is a concern

I had a really good day yesterday working with a client's team.

The team has issues. Plenty of issues. Some are managerial issues, some are people issues and some are production issues.

When I first met the team they didn't know what to do with their issues, so I started by helping them to see more issues.

Issues everywhere, they didn't seem very impressed.

And then we captured the issues as 'concerns' into the tried and tested 'concern cause countermeasure' format and followed the process:

Concerns probed for root causes and root causes converted into countermeasures.
Soon they realised that some of their root causes dealt with numerous concerns and they gained momentum.

Yesterday we pulled another one of their processes apart and identified all of the gaps. The gaps became concerns and we fed them back into the process. Now they have a practical action plan (of countermeasures) to upgrade the process in question.

What do you do with your performance gaps? …

Continuous Improvement and the Five Legged Race

Many improvement projects need the buy in of several people before they can progress. Amongst these people there will be some that have a firm view of what needs to happen and are keen to make progress. Some of the people won't be sure and they will need more time. Other people might not be that interested and have other priorities they want to focus on.

None of this is wrong.

It is an observation of mine and one that I see repeat on a regular basis with the businesses that I come into contact with.

But, if we take the principle from the observation we have an interesting improvement strategy (one that I personally use when I get stuck with my client's improvement projects).

You might have worked out the approach from the title of this blog post, but it is analogous to a three-legged race (or four, five, nine...). If someone in the group moves in the wrong direction and / or at the wrong speed then the whole group falls over.


In the example I gave at the start it is no differe…

Do you have time to prepare (in order to become super productive)?

I had a funny conversation a few weeks ago with a team that was complaining about one of their colleagues spending 'ages' preparing their workstation within their factory. I meet a lot of people that spend too long preparing (and effectively procrastinating) so I was intrigued by their comment. It turns out that this individual didn't spend too long but rather his colleagues dived into their work without thinking through what the best way to work was...

The slower to start gentleman did in fact prepare his work area. He was also able to produce a far greater amount of work in the same time period because he had invested in a smarter way of working than his counterparts. The time spent preparing his working area was valuable and not overdone.

This example reminds us of the importance of the second S in 5S (set in order) and how workstation design is critical if we want to maximise the productivity of our teams. Whether this is a physical work area in a factory, the filing s…