Why is Kanban Right for Product Development?

Kanban is a mean of facilitating getting things done, meaning it provides a working and verified way to run processes, but it will not, however, give tips on what to build. Keeping that in mind, it’s still safe to say, that knowing the right way to get somewhere is a crucial part of achieving anything.
So, once you have a product idea, applying Kanban makes sense.

This is how this should work:

From an overview to details

This one will have a variation of the following steps (depending on the specific organization standards):
— gathering requirements plus their verification
— drafting a strategy and assigning resources
— building the product
— preparing a marketing strategy (if different from usual)
— testing and verifying the initial result
— broader group testing, troubleshooting and defining requested changes
— second build and verification
— release
— feedback analysis and planning of future improvements.

Benefits of Kanban for product development

Further benefits of applying Kanban to product development include:
— a sense of being in a flow of a process, hence of getting somewhere
— clear indication of what to focus on next
— seeing the big picture gives a sense of contributing to a broader goal, fuelling job satisfaction
— the ability to always take a look what’s been recently done — and in what amount — helps to motivate the team, whereas in a single task assignment system, both the sense of accomplishment and the notion of being a part of a larger thing are lost
— a Kanban -based system is possible to scale, it may require a trained professional to do this for large teams, but is definitely achievable. You can either go with expanding the process to oversee multiple projects or with duplicating processes for different projects and managing them separately.
— it empowers the team by letting them pull work items themselves
— improved reliability, release planning and predictability, thanks to the available board analysis and an overview of the progress
— last, but not least — no more wasteful multi-tasking, thanks to WIP limits.


The point is to allow teams to focus on the work and product, and leave the process system in the background. With the little maintenance that Kanban requires this is not difficult to achieve.

First published on the Kanban Tool Blog.