Skip to main content

It Might Not Be That Bad

When a change project looms on the horizon it may look pretty daunting.

It may look like something of a big deal to handle and that alone may put people off.

It may of course be a lot simpler and a lot faster / simpler to implement than originally thought.

I see numerous projects that have stalled because the people tasked with implementing the change have decided it was way too big to handle. And so it goes 'on hold'.

There are two remedies that I like in this instance, and both attempt to do the same thing in slightly different ways.

Scope and plan

When you confirm the scope of the changes required and plan out the necessary steps you can quickly estimate the amount of time each step will require. In many cases the time is less that you thought it was, and you can now get on with it (with a general feeling of relief!). Alternatively, as you have now broken the plan down into smaller steps, you will be more likely to be able to fit these quantified chunks into your diary. Any larger steps can also be broken down again until the whole thing feels comfortable and progress gets underway.

Nibble away

Slightly less organised than the first option, but great if you are unsure of the overall plan is to nibble away at the first step. Take the first step that you think needs to be completed and then break it down into tiny little chunks. You may have come across this method as the 'Kaizen' approach, and it works wonderfully if projects are getting stuck due to inaction. Who can say 'no' to a tiny task?

Both of the above suggestions are aimed at understanding that change projects are usually made up of several smaller components. I hope that you can use either strategy to get your stuck projects moving once more.

Giles Johnston
Author of 'Business Process Re-Engineering', a practical plan to improve business performance.

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…