This is the first in what will be a series of short articles about some of the key aspects of Kanban and how it can help you.
Agree to pursue improvement through evolutionary change
There are many aspects of this statement that I really like, in particular the evolutionary change aspect. This is a clear differentiator between Kanban and many of the other agile methods / frameworks out there, many of which prescribe that you will first need a series of larger disruptive changes to structure and roles.
Improvements are often small and continual, but the cumulative effect of many small changes can move mountains. In some cases, however, you may require some help from management to remove larger systemic bottlenecks and problems from your process. I see both of these as evolutionary changes – some are by their nature small, but some evolutions will require a little more effort to manifest. Leadership here is a key component – sometimes these changes are hard and will require some courage to start to implement.
All improvements require a change, however not all changes are improvements. Thus, there is a notion that we have to be active in this activity, not passive. Additionally, there is a feedback loop here. Often, we are dealing with complex or at the very least complicated systems and our hypothesis on the effect of a change may not necessarily prove to be true. In this case, some of the evolutions will need to be reverted / dampened down whilst others will need to be solidified and / or amplified. A key part of evolutionary change is the feedback loop and understanding which changes are effective as improvements and which are not. Of course, one size will not fit all, so you will have to look for improvements that will work in your context.
Another key aspect of this statement is the first word – agree. It implies that a level of discussion and consensus needs to take place before we start down this path. Having these foundations in place can avoid a great deal of resistance to the change down the track. At a very basic level you’re letting people know about what the change is and what to expect so they can understand and be prepared for it. However, there’s also another aspect to this where we want people to actually be involved in the change – having the agreement up front about the direction and mechanism for the changes will assist with this. Some transformations rely on a tell approach, however if you try the alternative Kanban approach, you’ll no doubt find that your change will be more effective in the long term. Sometimes it’s just a simple conversation, but other times it can take some time – particularly if the changes are the larger management led ones.
Evolutionary change can be a wonderful enabler for your organisation to grow to provide products and services that are fit for your customer’s purpose. What’s really important is to start to weave into the culture of the organisation a sense and need of continuous improvement so your organisation will itself evolve to become truly adaptive, whilst not running the risk of over-reaching with change. One of the key aspects of Kanban is the evolutionary change approach and I hope you will agree that this can be a lower risk way of introducing the required improvements into your organisation.