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.
Start with what you do now
This is one of my favourite aspects of Kanban – the “Start with what you do now” change management principle built into Kanban. It’s quite simple and it engenders a foundation of respect for the current organisation that some change initiatives ignore – particularly some of the agile frameworks / methods where it is noticeably missing. I guess this is one of the distinguishing points of the Kanban method – it has an aspect of change management built into it.
There are a couple of additional points worth mentioning that expand on this:
“Understand current processes as they are practiced”
“Respect existing roles and job titles”
One of the key benefits of this kind of approach is that you acknowledge the current organisation and the people in it. “What you do now” has in some way been successful up until now – if not your organisation would likely have gone out of business. The purpose and customers may have changed over time and we can start to make adjustments towards this new purpose, but for now we need to acknowledge the present state. By making such an acknowledgement up front, you’re not going to get people within the organisation off-side when you encourage them to start to make incremental improvements (more on this in a later post). I often get feedback during my Kanban courses that people really love the idea of starting where they are right now.
By respecting the roles and job titles as they currently exist in the organisation, Kanban changes tend to have a low aspect of resistance. People are less threatened and often open to conversation as to how they can be a part of making their system of work better for all involved. That is, it’s often not just the customers that will benefit from this, but the teams involved in doing the work. I find as a coach going in to an organisation, that by using this kind of approach, I avoid a lot of problems before they arise.
Furthermore, with the aspect that we understand current processes as they are practiced tends to be very investigative and requires a curious mind. It should preclude jumping to conclusions as to what the cause(s) of the key issues really are (often this involves symptoms rather than causes of problems). Rather, this will allow us to get a better understanding into the why the problems really exist and to come up with appropriate solutions to those problems based on the specific needs of the contextual domain. Thus, your journey is unique and you’d be doing your organisation a disservice if you just “follow a pattern” to a “standard” end goal. Indeed, how are you competitive if you’re just doing what everyone else is doing?
The bar for change using Kanban has intentionally been set quite low – it allows you to get started rapidly without the large reorganisations and disruptions that other methods often require. That’s not to say you can start to make changes – evolutionary change is a central part to this and will be covered in a subsequent post.