Skip to main content

But Why Do I Need SOPs?

'But why do I need SOPs?' is a question I often get asked.

If you are working with Standard Operating Procedures then you will most likely hear this question too.

I always think having a few good answers up your sleeves is a good strategy to use; so here are some that I find useful when it comes to promoting the use of SOPs.
  1. The conversation between members of staff to find 'the one best way' is invaluable. Gathering the different opinions and making a decision is a really important process to go through.
  2. Reviewing SOPs periodically is also essential for maintaining good working practices. People deviate and try other things. By reviewing the standard and comparing it against reality the review can inform you whether you need to update your SOP or provide training to your team.
  3. When you have new members of staff join your team their training time can be reduced significantly when the appropriate guidance and instruction is available (the SOP).
So, there's a few good reasons that I refer to.

What reasons can you come up with?


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

P.S. If you are looking for some ideas on how to improve the quality and usage of your SOPs then check out my book 'Effective SOPs'.

Popular posts from this blog

Want more time for your projects? Try the 'Hour of Pain'!

Do you find your day being broken up by interruptions, stopping you from getting on with your work?

Continuous improvement projects often fall foul of this. The day can become so inefficient through the constant stopping and starting that we only just seem to have enough time to get the 'day job' completed.

I was in a meeting last week where this same issue cropped up. It also cropped up today. It's nothing new, but it is still a pain in the rear!

So, let me share with you an approach that has worked for my clients - the 'Hour of Pain!'.

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…

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? …