Skip to main content

Posts

Showing posts from September, 2012

'Winning Ugly' with Process Improvement

When we start out on our improvement projects, whether we are 'going lean' or for another reason, we sometimes find that our grand plan of how the improvement is going to progress differs from what we actually experience. An approach often referred to as 'winning ugly' (achieving the result, but possibly not in the way you first envisioned, is a nice way of putting it) is a good one to keep in mind when you are faced with projects (and even individual meetings within those projects!) that aren't going to plan. An obvious point that I see on a regular basis is the amount of detail and planning that is put into the improvement project plans because of the fear of having to win ugly. Now, this is not to say that you should skimp on the details and start with a poorly thought out project, but the phrase 'fit for purpose' certainly comes to mind. Unnecessary polishing of project plans delays taking action. Get the plan fit for purpose and then start taking a

3 Ideas to Improve 'Process Improvement' - Slideshow

Earlier this week I gave a presentation around the subject of improving your process improvement projects. The embedded link below is the annotated version of this presentation. Smartspeed Consulting Limited Taking the frustration out of on time delivery.

Trust MRPII to assist your business (just like your Sat Nav!)

As I was finishing the 'go live' of a client's MRPII system, I found myself explaining to their members of staff that trusting the MRP suggestions is a lot like just trusting the Sat Nav you have in your car. I'm sure you've experienced the time when you're Sat Nav has told you to take the next left but you decided to carry on driving straight ahead. When you get to your destination you often have the insight that you're Sat Nav was in fact correct and had provided you with the best route. Your route was sub-optimal in this example. MRPII systems are very similar, we may not understand why they're telling us what to do, but with a bit of digging, and a little bit of understanding we can understand why it is doing what it is doing. Once this comfortable state has been achieved we can then follow the MRPII instructions and use our new found time savings to better effect, such as our continuous improvement projects (rather than running around like headles