Skip to main content

A strategy to improve the flow of improvements

Do you have a long list of improvement opportunities that never seems to change?

Do you feel that the whole list is stuck and not delivering the benefits that are possible?

…if you feel the same then you are not alone!


When we have either large projects, or too many projects, the close out of the improvements can seem to be sluggish.

So, how about a strategy you can try out and see if you can get some traction with your improvements?

Split up the improvements into ‘packets’ that are no longer than two hours and then work on one packet at a time (as a team).

So:

  • If you have a bigger project there will be lots of packets.
  • Small projects might just be one packet.
  • You can mix in small projects between a larger project’s packets.
  • The team has one focus at any one time.


Our ability to handle, and deliver, multiple improvements at any one time on top of our normal day to day responsibilities is limited. When we go past this limit we often find that instead of making some progress we just get confused and make no progress.

A side benefit of the small packets approach I mention above is that your team will get the taste for closing out improvement projects because you will be winning on such a regular basis that it can become addictive!

And, why two hours? It is small enough to lose in the week (amongst your other obligations) and long enough to make a difference. This isn’t prescriptive though, experiment with different packet durations if you wish.

If your projects are stagnating then have fun with this approach and let me know how you get on with accelerating the rate of change in your business.

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.


Do you want more strategies like this?
Find out more here

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…