Skip to content

7 Reasons Why People Are Process Resistant

Picture of Ryan Johnson

7 Reasons Why People Are Process Resistant

Photo Credit: UX Indonesia; Unsplash

What Does this Phrase Do to You?

When you hear the phrase, standard operating procedures (SOPs) do your eyes light up and does a satisfying smile start to emerge?

Or, do your palms start getting sweaty and the excuses start lining up in your head ready to launch out at the next poor soul who mentions that you need them.

Well, if your answer is the latter there is a good chance that you are process resistant.

But that begs the question, Why?

Well, this is not a comprehensive list but here are seven reasons.

7 Reasons why People are Process Resistant

  1. Lack of time: Creating SOPs are not always easy and they take time and effort, and people may feel that they do not have the time to devote to this task.
  2. Lack of resources: Developing and implementing SOPs may require additional resources, such as software or specialized training, which may not be available.
  3. Resistance to change: Some people may resist the idea of creating SOPs because they feel that it will disrupt their existing workflow or that they will lose control over how they do their work.
  4. Perception of unnecessary bureaucracy: People may view SOPs as an unnecessary bureaucratic process that adds complexity to their work.
  5. Fear of being held accountable: Creating SOPs can make people feel accountable for their work, and some may fear being held responsible if something goes wrong.
  6. Limited knowledge or expertise: Some people may not have the necessary knowledge or expertise to create effective SOPs.
  7. Lack of perceived benefits: People may not see the benefits of creating SOPs or may not understand how they can improve the quality and efficiency of their work.

The Reasons Behind the Reasons

Some of these 7 reasons are understandable but others are not. So, let's establish why we need SOPs.

Full disclosure, I like SOPs and the development process.

I know that sounds weird to you, it even sounds weird to me as I write this, but let me explain.

The reason I like SOPs is not just because I enjoy the physical process. I like them because of the outcomes they produce.

Like...

  • Clarity
  • Teamwork
  • Efficiency
  • Consistency
  • Quality Control
  • Revenue Growth

Now, doesn't that sound better!

The bottom line is, if you don't have well documented SOPs and someone who knows that a process is not being completed then your process and production will stop!

Even worse, if someone quits or passes away then their knowledge goes with them along with a lot of time, energy and money.

Then, you and your team are forced to work long hours figuring this process out along with all the regular duties that can't stop either.

This could cause a chain reaction of several things:

  • Team frustration and conflict
  • Decreased production
  • Increased expense
  • Decreased revenue

So, you have to ask yourself...

"Is saving time now, not creating SOPs with your team, worth the risk of losing a lot of money or the future of your company later?"

In my opinion, it's not!

In fact, I would even go as far to say that if you are not willing to ensure the stability of your company's future with SOPs, you are being negligent and irresponsible.

It's not leading, it's hoping.

Sorry for the rant but this is important.

On a positive note...

If your company truly wants to grow then it's a great way you can ensure that everyone knows what they are supposed to be doing, when they are supposed to do it and how they are supposed to do it.

This will bring confidence and ownership to everyone across the company that will produce great synergy, results and help everyone "win" together!

Hopefully, now you see the value in SOPs.

Keep it Simple

Ok, here is the good news about creating SOPs.

You can create them, get all the benefits that I've already mentioned AND you don't have to create a massive document that is terribly time consuming to write and read.

The goal of SOPs is to make our lives easier and more efficient NOT make them harder and more complex.

SOPs should be:

  • High level steps NOT every little common sense detail.
  • Comprehensive enough that a professional in your field understands them.
  • Easily accessible to everyone involved.
  • Created by the team AND edited by the team, when needed.
Tip: Use technology to keep SOPs accessible and editable.

Of course some SOPs will be very complex due to the size of the company and the amount of steps.

However, you can get creative to make them easier to create and digest.

Suggestions to Creating Effective SOPs

  1. Use the Cloud: Use a shared folder, document or software solution to ensure anyone in the company can access it anytime, anywhere.
  2. Use Visuals: Pictures and symbols are much easier to follow. Create a workflow that can be comprehensive enough and easy to review quickly.
  3. Use Bullet Points: Give an SOP a very basic name that everyone understands. Then, list each step underneath it, as a phrase or a sentence, using bullet points.

Your team needs to determine what style works best for them.

In addition, they should all be in agreement with the steps or else they WILL NOT be followed and valuable time WILL BE wasted.

Just Do It

Ok, so you are probably wondering where you should start.

Great question, I'm glad you asked.

First, ensure everyone understands why this needs to happen and who needs to be involved and who should be responsible.

Second, provide time and resources to help your teams create great processes that will get great results.

Now, follow these steps to create effective SOPs:

  • Appoint a team & a team leader
  • Ask the team(s) to determine the most critical SOPs
  • Set a quarterly deadline
  • Let the team create it & DON'T micro mange!

Once this process gets going then it will become part of your culture.

You will get better at it and your company will be stronger for it.

Enjoy the Process!

Grow more. Risk Less

 

Maximize Your Personal & Business Production
, , , , , , , , , , , , , , ,