Skip to main content

What Can A Detached Retina Teach Us About Standard Operating Procedures?

I had a fascinating / terrifying personal experience very recently that had relevance to a meeting I had this week... about Standard Operating Procedures (SOPs).

A few weeks ago I was diagnosed as having a detached retina. Thankfully I live near to a superb hospital and they worked their magic on my poorly eye (and yes, I got to watch them as the whole procedure was done under local anaesthetic...).

Which brings me to my conversation about SOPs.

One of my client's team was struggling to get their staff to adhere to their SOPs. They couldn't see the relevance of following a certain procedure; they couldn't see the benefits to the business and for themselves.

So, I explained about my eye. I explained that I had been given some strict instructions (which were already standardised) to follow after the surgery. I explained that I followed them to the letter; I didn't want to go blind.

There was some clear cause and effect that I could demonstrate from my eye treatment, and I then did the same to my client's SOPs.

The staff in question couldn't see the effect, they just thought that they were following a procedure for the sake of it. When I demonstrated the knock on effect for them and the rest of the business we started to have a different conversation. It is sometimes a lack of appreciation about the 'why' behind a new process (and its related SOP) that needs to be clarified, rather than just trying to beat people up to follow a process.

So, I have a re-attached retina and hopefully you have a new perspective on how to help your fellow colleagues embrace the business' standard operating procedures.


Giles Johnston
Author of Business Process Re-Engineering

Standard Operating Procedures
Also available in PDF format

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…