Improving Processes: Kanban Workflow
The Kanban Method focuses on making iterative, incremental changes to work processes to increase efficiency and productivity. How can you translate your project processes into Kanban workflows and make them more efficient?
What is a Kanban Workflow?
A Kanban workflow is made up of the step-by-step process states between starting and delivering a task. The simplest workflow could have just three process states – To Do, Doing and Done. Tasks move sequentially from the first state to the last.
In reality, most workflows will have more process states. This can look very different for different projects – the workflow for a retail environment will not have the same steps as one for software development.
During Kanban’s history, visualising the workflow has always been a key component. This keeps you whole team on the same page – everyone can see which tasks have been started and how work is progressing.
Is Kanban good for every work process?
Some activities translate well to this format – some do not. The activities which work best for Kanban workflows are:
- Repetitive: All tasks will move through the same process states
- Sequential: Tasks progress smoothly from one step to the next without unpredictable jumps
- Continuous: New tasks constantly enter the workflow as old ones are completed
For example, a process for publishing blog posts works very well as a Kanban workflow:
- All blog posts must go through the same steps – plan, write, review, edit, publish (repetitive)
- Posts always go from one step to the next in the same direction (sequential)
- The blog always needs new posts! (continuous)
Some activities do not work well with Kanban. Activities where decisions can have many different outcomes, or processes which rely on high levels of subjective judgement are not well suited for Kanban.
Mapping your workflow
Once you have chosen a workflow, it’s time to really break down each of its component steps. Think visually – drawing out the steps of your process with pen and paper is a great way to keep things clear.
We recommend involving the whole team while mapping out your workflow – more people available makes it less likely for important steps to be missed. Make sure to identify any actions that could potentially block the workflow – for example, verifications, stage gates and hand-offs to other team members.
Many teams choose to draw a process flowchart for their workflow, mapping out where the workflow path can split, when decisions need to be made and which team members are responsible for each action.
Hexagon: Start/End point
Preparing your Kanban board
Once your workflow has been mapped out, you can start translating it into a Kanban board. Many teams get started using Trello, a popular project management tool, for this purpose. Each process state is represented by a vertical column or list. You can add as many process state columns as your workflow requires.
Each task is represented by a card, with the highest priority cards ordered from top to bottom within a list. Cards are moved from one process state to the next as they are developed. The Kanban board clearly and visually represents your workflow. Team members can instantly see what tasks are being worked on, how close they are to being finished and if bottlenecks are forming.
Kanban workflow best practices
Once your board accurately represents your Kanban workflow, you can apply the other important aspects of Kanban. We recommend learning more about the six essential practices, here are the most important points when getting started:
Work in progress limits
In Kanban, each list has a work in progress limit, a cap on the amount of cards it can contain at any one time. This means that if the WIP limit has been reached, no new task are allowed to enter the process state until an outstanding task has been completed.
In practice, this stops tasks from being forgotten and ensures everything gets completed. Limiting the amount of work in progress also keeps your team focused and reduces time wasted to context-switching. Finally, WIP limits stop bottlenecks from getting out of hand – team members must focus on clearing existing tasks and resolving blockages to continue.
Kanban doesn’t just visualise workflows – it seeks to improve them. To get better, it’s important to know how you are performing. Kanban metrics like cycle time and throughput are used to measure your team productivity, track past performance and identify areas for improvement.
WE UNCOVER THE EFFICIENCY OF YOUR WORKFLOW
Optimise your performance with Kanban analyticsSee a dashboard with your data
Classes of Service and Swimlanes
Some projects are too complex to be accurately represented by a basic board. Classes of Service (CoS) and Swimlanes can be used to split up the process states. CoS classify tasks according to priority level – for example, having different policies in place for emergencies and maintenance tasks. Swimlanes, however, are often used to organise tasks according to department, stopping the Kanban board from getting cluttered during complex projects.
Transparency and efficiency go hand in hand. By having a clear view of your process – from mapping out the steps, to creating your Kanban board, to delivering results successfully – you remove uncertainty about what action comes next. By combining the visual Kanban workflow with in-depth analysis of performance metrics, you can incrementally increase workflow efficiency.
Tell us more about your Kanban workflow! How easy was it to convert your processes? Which best practice was most useful? Tell us about your experience in the comments!
Meet the Author
Sonya Siderova is an independent consultant who helps organizations manage their products more efficiently. She is a proud mother of a daughter and a son, and enjoys good food and heavyweight boxing championships. Sonya is a regular blogger and founder at Nave.
Businesses with higher levels of team motivation perform better for a simple reason: they appreciate their employee… https://t.co/YGQITHyjarFollow
Are you always short on time and on budget, even though your team is motivated and skilled? Learn how our team at N… https://t.co/X689iUIVVCFollow
Large teams and complex projects face a common issue – the Kanban board becomes cluttered and hard to read. Learn h… https://t.co/SrMVqGjvV1Follow
Have you felt like your team is always busy, but nothing is ever quite finished? WIP limits in Kanban stop tasks ge… https://t.co/1K2PxVupKOFollow
Explicit policies in Kanban reduce the risk of productivity breakdowns and escalations of tasks. Learn how to boost… https://t.co/95u0itdVGVFollow
Are long cycle times holding your business back? By following these tips and integrating data-driven analytics into… https://t.co/Z72iNrrzz2Follow
Project managers are constantly balancing short-term responsiveness and long-term strategic planning. TTo give your… https://t.co/b2ymjJbehiFollow
In the same way that Kanban uses analysis and feedback loops to improve workflow efficiency, Kanban meetings aim to… https://t.co/vQB3xtCrezFollow
How did supermarket restocking techniques revolutionize project management? Learn the history of Kanban and how it… https://t.co/mrAppr9R9GFollow
Kanban processes improve by continuously making incremental changes. Effective changes are built upon data. In this… https://t.co/PXcCNewcdnFollow
Kanban can help you run your business better, make your processes more efficient and empower your team to accomplis… https://t.co/ELat3VvCyZFollow
High flow efficiency is vital to sustaining a scalable, productive business. Learn how you can calculate, analyze a… https://t.co/b8S5pojnb8Follow
What makes the difference between an effective daily standup and one that just wastes your team’s time? Our short g… https://t.co/fKBYqdO6QDFollow
Two Kanban roles, Service Request Manager and Service Delivery Manager have emerged to equip teams with important d… https://t.co/LrWhFIKGDOFollow
Predicting how long a task will take plagues project managers everywhere. Cycle time is an easy way to work out you… https://t.co/ep2TSISPDdFollow