Improving Your Workflow in a Kanban Strategy
Introduction
The third core practice in Kanban is improving your workflow. It’s essential to not only visualize your work and actively manage it but also to make continuous improvements to the workflow itself. Without ongoing improvements, inefficiencies and blockages will persist, hindering the overall effectiveness of your system.
The Importance of Improving Your Workflow
It’s not enough to just see what’s happening in your system and manage the work actively. If your system is flawed or inefficient, those issues need to be addressed. Improving your workflow involves making changes to maximize the flow of value through your system. Here’s how to approach this:
- Identify and Address Blockages:
-
Understand why blockages occur and take steps to eliminate them.
-
If work is getting stuck in a particular stage, investigate the cause and adjust the process to prevent future blockages.
- Reduce Waiting Times:
-
Minimize delays in the workflow by addressing approval processes or other bottlenecks.
-
Implement strategies to ensure work moves smoothly through the system without unnecessary waiting.
A Real-Life Example of Workflow Improvement
Let me share a real-life example to illustrate how improving the workflow can significantly enhance efficiency:
I worked with a team in the US that had a Kanban board on the wall in a central corridor of their office. They faced a challenge with an approval process that created a bottleneck. The approval person only reviewed items once a week, leading to significant delays.
The Problem:
-
Items finished on Monday afternoon would sit for almost a week before being approved the following Monday.
-
This delay was costly, causing unnecessary waiting times and hindering the flow of work.
The Solution:
-
The team calculated the cost of items sitting and waiting for approval and displayed these financial figures on the Kanban board.
-
They used Post-its to highlight these costs, which increased as the week progressed.
-
They also created a graph to show the bad flow of work and the accumulating costs.
The Result:
-
The person responsible for approvals noticed the escalating costs displayed on the board and immediately understood the impact.
-
This visibility prompted them to change their behavior, checking for approvals every morning and evening.
-
This change significantly reduced the waiting times, leading to a major cost benefit for the team.
Taking Action to Improve Workflow
Improving your workflow involves more than just identifying problems. It requires taking concrete steps to address those issues:
-
Visualize Costs and Delays:
-
Use visual aids to highlight the impact of delays and blockages.
-
Make the costs of inefficiencies visible to everyone involved.
-
Encourage Proactive Behavior:
-
Foster a culture where team members actively look for ways to improve the workflow.
-
Regularly review and adjust processes to ensure they remain efficient.
-
Engage Stakeholders:
-
Involve key stakeholders in the process of identifying and addressing workflow issues.
-
Ensure everyone understands the impact of delays and the importance of timely approvals and actions.
Conclusion
Improving your workflow is a critical practice in Kanban that ensures your system remains efficient and effective. By identifying blockages, reducing waiting times, and making continuous improvements, you can maximize the flow of value through your system.
If you are struggling to implement a Kanban strategy, we can help or connect you with someone who can. Click the link below to get in touch and start optimizing your workflow today.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
3 core practices of Kanban. Actively managing work items in a workflow
Explains how to actively manage Kanban workflows by monitoring work in progress, resolving bottlenecks, and optimising flow for greater …
Mastering Kanban: The Essential Guide to Defining and Visualising Your Workflow for Maximum Efficiency
Learn how to define and visualise workflows in Kanban to boost team clarity, alignment, and efficiency, with practical steps for stable …
Mastering Kanban: A Simple Guide to Its Core Principles
Learn the three core Kanban principles, visualising workflow, actively managing tasks, and continuous improvement, to boost team efficiency, …
At the end of the day, Kanban is about improving flow
Kanban focuses on improving workflow by removing bottlenecks and constraints, reducing work in progress, and increasing process efficiency, …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team
Unlock better flow and real value with the Open Guide to Kanban, a practical, community-driven resource for teams in any industry. Join the …
Why Measuring Individual Cycle Time Fails to Help Teams
Measuring individual cycle time overlooks team performance and system bottlenecks. Focus on lead time, throughput, and process efficiency to …
Why Tracking Individual Cycle Time Distorts Team Behaviour
Tracking individual cycle time can harm team performance by encouraging task cherry-picking, reduced collaboration, and lower quality, …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …