Well executed continuous improvement initiatives are proven to deliver sustainable competitive advantage. How do you make sure they stick?

Process improvement methods such as Lean, Kaizen, Six Sigma and Agile are methods that are proven to result in increased efficiency and costs. However, applying these methods and having them result in continuous improvement is often rare. Out of a study of 204 improvement projects completed, about half of them had regressed. After two years, it reduces to one in three. Why is that the case? I don't think the answer is simple, but I do believe that there are crucial aspects that need to be considered and maintained long term for the change to stick which include:
1. Employee Involvement:
This is an essential aspect. Frontline workers are the closest to the work and often have the most fruitful insights into how details can be improved that senior level employees normally wouldn't see. Capturing these details is incredibly important in maintaining a positive customer journey.
For example, let's imagine a call center agent was having difficulty inputting key details into a CRM platform pertinent to an order. This might impact other workers dealing with the client resulting in disorganized delivery of the service or order, poor customer experience and potential loss in revenue long term. The small details matter.
2. Maintaining Senior Leadership Support and Buy In:
At times, process improvement is seen as finite. Meaning, momentum and enthusiasm dissipates when leadership focus is shifted to other projects. Although a new process change may be regarded as a project with an initial start and end date, it doesn't mean that we regard it as finished when implemented.
Process Improvement should be considered as a “habit” and having senior leadership dedicate time and support ignites fellow employees to maintain ongoing support. One way to help build a culture of improvement is having senior leaders regularly immersed into the project. For instance, holding “accountability” meetings. What this might look like is the partnership of both senior leaders and others presenting wins, failures, challenges with supporting data. Oftentimes, this results in people opening up and having an honest dialogue about where they stand on the project, which inevitably ignites accountability and buy in.
3. Transparency and Knowledge Sharing:
Departments across large scale companies can often work in silos. They may have their own set of internal processes on their team that works for them. But, it is crucial that teams understand the challenges and initiatives that their fellow departments are working on. Perhaps one team has knowledge of a critical piece that would vastly improve a new project or process change.
One way to improve cross departmental transparency is to make your project goals and intentions public. Tailor the content to all individuals including project justification and data. One example of how I have effectively managed to involve other departments is by communicating my strategy, holding a “kick off” meeting and explaining what is in it for each department. “Continuous Improvement” is a universal term, however ensuring that all departments included understand how this impacts their role and internal processes is essential.
4. Standardize the work:
Perhaps one of the most under utilized “Lean” tactics is standardization. In order for the process improvements to last, they must be standardized and repeatable. This will ultimately create a baseline for improvement. The benefits of standardized work include documentation of the current state, future state, easier training for new hires and reduction in variability. What I enjoy about standardizing work is the ability to problem solve with my fellow co-workers.
An example of standardization that has worked for me is ensuring I have clearly documented best practices. These best practices can then be utilized by frontline workers, senior leadership members and for training new hires. Once you have these best practices, you can iterate on them and re assess if they are still relevant and need to change.
5. Focus on Negative Neutral and Positive Cases:
When you're trying to understand where to apply “Continuous Improvement” I find it helpful to examine not only negative processes within your business but also neutral and positive cases.
1. Neutral
Neutral cases are processes that don't seem to be causing obvious negative results but are processes that have remained the same for long periods of time. Perhaps you haven't focused on them because it is hard to pinpoint obvious improvements. It is easier to let these remain the same, but honing in on these often results in powerful brainstorming.
2. Positive
Positive cases can be helpful in understanding what you did right and how to replicate that among other processes. Can you take certain best practices from other departments and replicate that in your own? Can we iterate on this and take it to the next level? Is there someone in the office that has fostered positive process change that we can learn from?
As you can see completing a project related to process improvement is often the easiest aspect, however maintaining continuous improvement is both rare and complex. It takes inventiveness, fortitude, dedication and support. It is often easier to let our current processes remain the same without question then it is to change, re-asses and re-invent. The outcome of utilizing the tactics I have outlined in this blog often result in knowledge sharing, best practice creation while fostering a culture of Continuous Improvement.





