3 best ways to wreck Kanban. Use vanity metrics

Avoiding Common Mistakes in Your Kanban Strategy

Introduction

One of the primary ways to fail in implementing your Kanban strategy and not achieve the value you expect is by not looking at the right data. Many teams think they are doing Kanban simply because they have a board with columns. However, without proper metrics and active management, this approach falls short.

The Importance of Proper Data Analysis

To truly benefit from Kanban, you need to go beyond having a simple board. You must leverage the right metrics and actively use the data to drive improvements. Here’s how to avoid common pitfalls:

Ditch Vanity Metrics:

Metrics like story points, velocity, and burn down charts do not provide actionable insights for improving your workflow.
These metrics often serve more as “vanity metrics” that give a false sense of progress without driving real value.

Focus on Key Kanban Metrics:

Work in Progress (WIP): Measure how many items are currently in progress. This helps to manage the flow and ensure that work does not pile up at any stage.
Cycle Time: Track the time it takes for an item to move through the system from start to finish. This provides insight into efficiency and potential bottlenecks.
Throughput: Measure the number of items completed in a given time period. This helps in understanding the capacity of the team.
Work Item Age: Monitor how long items have been in progress. This helps to identify items that may be stuck or delayed.

Collecting and Using the Right Data

Most digital tools like JIRA, Azure DevOps, and Trello automatically collect the necessary data. You only need two pieces of information for each work item: the start date/time and the end date/time. Here’s how to use this data effectively:

Work in Progress (WIP):

If an item has started but not finished, it’s part of your WIP. Track this to ensure your team is not overburdened.

Cycle Time:

Calculate the time taken from start to finish for each work item. This helps identify areas for improvement.

Throughput:

Count the number of completed items over a set period. This shows your team’s capacity and helps with forecasting.

Work Item Age:

Monitor how long each item has been in progress. This helps identify items that are at risk of becoming bottlenecks.

Taking Action Based on Data

The true power of Kanban comes from using the data to make informed decisions and drive continuous improvement:

Address Blockages:
Identify why items are getting stuck and take steps to remove these blockages.
Optimize Flow:
Use the data to adjust work in progress limits and ensure a smooth flow of work through the system.
Improve Predictability:
Analyze cycle time and throughput to make better forecasts and meet delivery commitments.

Conclusion

Avoiding common mistakes in Kanban involves focusing on the right metrics and actively using the data to drive improvements. By ditching vanity metrics and leveraging key Kanban metrics like WIP, cycle time, throughput, and work item age, you can create a transparent, efficient, and predictable workflow.

If you’re 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.

Avoiding Common Mistakes in Your Kanban Strategy

What to read next

3 best ways to wreck Kanban. Sweep problems under the rug

The Importance of Visualizing Your Work in a Kanban Strategy

3 core practices of Kanban. Actively managing work items in a workflow

Getting started with Kanban

My journey with Kanban and why I actively recommend it to clients

Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)

Detecting agile theatre with real delivery signals

Why Most Companies Operating Models Fail in Dynamic Markets

Don’t Manage Dependencies, Remove Them

The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery

Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?

Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team

Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?

Estimating Better in an Overloaded System Is a Poor Man’s Strategy

The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team

Kanban Guide

Why Measuring Individual Cycle Time Fails to Help Teams

Why Tracking Individual Cycle Time Distorts Team Behaviour

Why Most Companies Operating Models Fail in Dynamic Markets

Don’t Manage Dependencies, Remove Them

The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery

Kendall Guide - A System of Work for AI Adoption

Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?

Estimating Better in an Overloaded System Is a Poor Man’s Strategy

3 best ways to wreck Kanban. Use vanity metrics

Table of Contents

Avoiding Common Mistakes in Your Kanban Strategy

Smart Classifications

Table of Contents

What to read next