Written by: Nigel Richardson
Once you start to scope, define and deliver improvement you turn to address how the improvement is managed through an appropriate level of structure to ensure you are delivering the right improvement in the right way to give you sustainable results.
The two main factors to consider when forming a judgement on the appropriate level of structure are:
1) The stakes
How impactful is this business problem, what are the stakes of failure and how large is the performance challenge?
2) The urgency
When does this need delivering by?
There is no point delaying your improvement due to layers on unnecessary tool application.
Done is mostly better than perfect.
Below are some suggested levels of improvement that I have seen built it in a variety of functions and industries.
Make it happen and capture it is done.
A simple log of what was done, why, and the expected benefit to the business performance is all you need.
If you collate these, they can become something more powerful.
Action lists, Concern and Countermeasure Sheets, any form of log is a powerful reminder of the steps being taken over time no matter how small.
If you invest in the basics from the section above to ensure business performance is the data driven focus you will reap the rewards.
These are a base level structure that can be applied to any gap in operational performance or issue resolution.
They are often a blend of items A and C in this list in the following logic:
The goal here is to stop the problem getting worse and take the pain away from the customer.
In this context ‘sticking plaster’ solutions are completely valid.
With the above in place you now can investigate through your appropriate root cause approach to define and implement your corrective actions.
Once the problem is fixed there is a further round of review for preventative actions to prevent this happening again either in the same part of the business or other related parts of the business where this situation could occur.
It is often the case that the continuous improvement community within a business truly earn their credibility when they step up to lead this type of exercise.
In my experience a well-run Investigation of an impactful quality or customer issue can often create the focus of your continuous improvement deployment for the next couple of years.
That is truly continuous improvement.
Where the operational conversations do not yield a quick fix, a level of structure is needed to investigate the problem, define the root causes and define and deliver the required improvements in a sustainable way.
To ensure this level of improvement works there needs to be investment in the structure behind:
What is the problem? Why is it bad? When and where does it occur?
How do you detect it? Who is involved?
A team of people with the relevant breadth and depth of knowledge of the business have a joint conversation or workshop to map out the relationships between the observed effects and contributing causes.
The root causes that you choose to define improvements around will be based on a mixture of:
Root cause analysis can tend to create a perception that a problem is insurmountable, a huge organizational effort even.
My guidance has always been to design improvements around what is within your ability to influence.
If others see you are doing what you can then you are more likely to get additional support or budget to push harder.
My absolute favorite facilitation tool in this context.
It gives you the freedom to ensure that the resulting activity is not just to a satisfactory depth (i.e. somewhere close to the 5th why level), but it also covers an appropriate breadth.
No cause effect relationship is a single straight line. A single cause can influence multiple effects and the more you can view this as an overall landscape the more powerful it is.
Other favored tools to visualize cause and effect include Fishbone analysis or the Affinity diagram.
Generally, running in a structured set of phases my go to standard in this space for many, many years is DMAIC.
DMAIC has been covered in our chronicle of Six Sigma’s history but, from my experience working in companies that applied both Lean and Six Sigma approaches, DMAIC served as a base set of phases for any form of improvement.
The headings may change, but the goals of each stage are roughly the same so I will use DMAIC as a core frame of reference.
It is vital that you have some form of framework for your improvement delivery to ensure that outcomes are actually delivered having invested so heavily in the up-front activity and engagement of teams.
The tools and techniques that exist are successful due to one single point of reality that I have faced after 20 years of applying this:
However, most of the time they serve as a very effective facilitation tool by visualizing the thought process you are going through, and establishing a logical story, allowing you to:
Regardless of the improvement method definition in my experience the tools and techniques can be grouped around three categories:
Taking your activity to a logical conclusion from the initial discussion to closing the improvement as sustainably implemented as part of business as usual.
A level of project management keeps you and your stakeholders honest and focused.
This is the competency that ensures that the people you rely on for improvement deliver an improvement rather than act as a facilitation support function.
Helping you define the problem and the current state reality in your business. The output will be highly specialized to your industry and your reality.
The standard and structure comes from how to collect, manipulate, analyze and visualize information that you learn either from a data collection or process observation perspective.
Most of the Six Sigma derived tools and techniques are of this nature.
These are a proven predefined set of principles and ways of working that you can apply to improve your business.
Most of the Lean toolbox is comprised of these predefined improvement tools or playbooks for you to follow to add value in your business.
When you consider the plethora or opportunities in these categories it becomes a lot clearer as to how companies successfully combine Lean and Six Sigma in a single integrated end to end improvement method.
Click here to learn more about continuous improvement, or take a look at these content recommendations:
Nigel Richardson is a continuous improvement expert. His background spans 20 years in business transformation and continuous improvement across retail, pharma, aviation and IT supply chain. He is passionate about supporting organizations to achieve their strategic, transformational and improvement goals, and outperform their peers year after year.
If you’d like to talk more about your strategic challenges, reach out to him on nigel.richardson@i-nexus.com or connect with Nigel on LinkedIn for the latest Strategy Execution insights.