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

Stop firefighting, start performing!

Another weeks passes and another example of unnecessary fire fighting demonstrated by a business I have been to help. If you have this taking place in your business, let me ask you a few questions: 1. What keeps on happening? Regain control with this practical book Can you pin down what it is that you keep having to do, to get out of trouble? If you can't, is there a pattern you can observe? 2. Do you want it to stop? Is it causing you enough of a problem that you want it to stop? If the answer is yes, keep reading, if not park it for another day. 3. Find out what is going on Do you know why you are having this issue? If you aren't sure where the issue is arising from, then take a few minutes to have a look around. When you have some idea, go to the next step. 4. Cause and effect Do you know what is truly causing the fire fighting situation? If you spend the time to get to the root cause of the situation , you have a good chance of permanently eliminating this situation. Most p

Kaizen improvements need to be specific

Do you find that your Kaizen improvements don't always go to plan? If you do, then you're with the majority! Whilst there is great deal of 'trial and error' there is a simple approach that can help. Available from Amazon Being specific about critical parts of your improvement can uplift your results. So, how do you go about doing this? The most direct route is to be clear about which parts of your improvement are critical. From here you can explain, in detail, what you want for those items. This might take some practice as many of us have become lazy in this regard. We take it for granted that our team 'get us' and will know what they need to do. If you ever feel that something basic is missing from an improvement ask this question: "What does good look like?" The answer should put you back on track. About the author: Giles Johnston is a Chartered Engineer who specialises in helping businesses to grow and improve through better business processes and

Are your teams clear?

I have recently finished working with a team that were struggling. They were struggling to meet their production schedules. They were struggling to respond to customer enquiries on time. They were burnt out and frazzled. After some prodding and poking it became clear what their issues were. In particular, it became obvious that expectations of the team weren't clear or defined. Defining what you expect from teams is a standard management approach. The problem with most teams is that leadership describe the standards in vague terms . So, what happens if you get the standards crystal clear? You should expect to see the team produce the right outputs. They should produce the outputs at the right time. And, they should produce them in an agreed way. Be clear with your teams. Ask the question: What does good look like? If you want to get some more ideas on how to define effective standards and visions, get your copy of my book today . What does good look like? is a practical guide to h