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

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…