Skip to main content

Finding The Parallel For Your CI Conversation

I was delivering some training on Lean Production methods yesterday. The team I was working with are based in a call centre and we found a number of interesting continuous improvement opportunities to work on.

Through our conversation I became particularly interested in how they could move their resources more dynamically (rules based) when call queues were extending.

I shared with them an account of when I was working as a Production Engineer in an automotive firm where we used several different Kan-Ban pull production systems to address this same issue.

Despite having already explained how these systems worked in principle, they were not convinced that it was a strategy that could work for them. It was the story, the parallel example, that convinced them.

I see this situation time and time again. The principles of an improvement may be sound and people may understand the improvement concept logically, but they haven't bought into the applicability to their business. A story can often get you past this issue.

What stories do you have that can help you to 'sell' your next improvement idea?


Giles Johnston
Author of Business Process Re-Engineering

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…