Skip to main content

What if your team just don't understand the 'why' behind your changes?

Change can take a really long time for some businesses to engage with. I don't mean the kind of rapid change that our businesses need when things are going wrong, I am talking about the longer term improvements that we all need to engage with.

Do you ever watch your staff / colleagues agree to a new way of working, only to watch this approach ebb away after a few days or weeks?

There may be a million reasons why the change doesn't stick. I'm sure that you can think of a whole host of reasons just off the top of your head, I know I can!

But, what if a lot of these reasons boiled down to the fact that the people just didn't understand the change, in a meaningful way? What if they conceptually understood the request, but it had no value to them, that the reason was missing?

In lots of cases I have seen people have the 'penny drop' when the reason behind a change has been re-explained, often in a different way to the first time that it was previously explained. How many times have you re-read something, or re-heard something and had the lights come on?

It could be the same for our colleagues and our team. We might just need to spend a little more time with them, to make sure that they understand the rationale behind a change as well as the mechanics of the change in order for it to stick as an idea worth following.

As I said, there could be a million reasons, but this particular one - not understanding the meaning behind the change - might be a biggie!

When I wrote the book Losing the Cape I was partially talking to this crowd. The section on breaking down the business' improvement vision into meaningful chunks that people could buy into was part of this. This strategy works, could it work for you?

If you get time to reflect on the changes / improvements you have started but watched fall over in recent times ask yourself 'did the people involved understand the why of the change as well as the what?'

It is a common phrase that 'the reason makes all of the difference' and perhaps we can look at using this more effectively within our own improvement endeavours.

Food for thought!


Giles


About the author Giles Johnston is a Chartered Engineer who specialises in helping businesses to grow and improve through better business processes. Giles is also the author of Business Process Re-Engineering and creator of the 'Making It Happen' continuous improvement toolkit.

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!'.

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

Free Continuous Improvement Guide

I have recently published a new free guide, with the title:
Six Quick Tips to Help Continuous Improvement Deliver Results Faster In the guide I share how to:
Use the continuous improvement cycle properly.Get projects moving, if they are slow to start or have stalled.Identify the 'biggest bang for your buck' when reviewing opportunities.Determine the level of change you need to achieve through your improvements.Flip staff grumbles and concerns into positive improvement actions.Increase the overall rate of progress on your projects. All of the tips are highly practical and are no-cost strategies.
To get your copy, just click on the button below and access the guide in just a few moments from now.



Enjoy reading,

Giles
About the author Giles Johnston is a Chartered Engineer who specialises in helping businesses to grow and improve through better business processes. Giles is also the author of Business Process Re-Engineering and creator of the 'Making It Happen' continuous i…