Kanban Methodology: Visualizing the Flow of Work

Stop multitasking and start delivering. Learn how to use Kanban boards, set WIP (Work In Progress) limits, and optimize your workflow for continuous delivery.

On this page
Set up Space

What Is Kanban in Simple Terms?

Kanban is a visual workflow management method that helps teams see their work, limit how much they're working on simultaneously, and continuously improve their process. Think of a board with columns (To Do, Doing, Done) and sticky notes (tasks) that move across. The key insight: by limiting work-in-progress, teams actually deliver faster because they finish tasks before starting new ones.

Kanban answers the question: 'How do we improve our existing workflow and deliver continuously without fixed iterations?'

The Philosophy: Stop Starting, Start Finishing

Kanban (看板) means 'signboard' or 'visual signal' in Japanese. It originated in Toyota's manufacturing system in the 1940s as a scheduling system for just-in-time production. The core insight: upstream processes should only produce what downstream processes need, signaled by visual cards. David J. Anderson later adapted Kanban for knowledge work in the 2000s.

Kanban can improve an existing workflow and can complement Scrum or other approaches. It does not prescribe sprints, but teams can use flow practices within them. Start by making work and policies visible, controlling work in progress, and inspecting how work moves.

The Kanban Board: Visualizing Your Workflow

The Kanban board is the heart of the method. It makes invisible work visible, showing everyone what's being worked on, where bottlenecks exist, and what's completed.

Typical Board Structure

Backlog / To Do

Work waiting to be started. Items are prioritized—team members pull from the top.

In Progress / Doing

Work actively being done. This column often has WIP limits to prevent overload.

Review / Testing

Work waiting for or undergoing review, approval, or testing.

Done

Completed work that meets the Definition of Done.

Boards should reflect your actual workflow. A software team might have columns like: Backlog → Analysis → Development → Code Review → Testing → Deployment → Done. A content team might have: Ideas → Writing → Editing → Design → Published.

The 6 Core Practices of Kanban

These practices, defined by David J. Anderson, form the foundation of Kanban. Implementing all six creates a system for continuous improvement.

1

Visualize the Workflow

Make all work visible using a board with columns representing stages. Every work item is a card that moves from left to right. Include everything—not just planned work, but interruptions, support requests, and technical debt. Visualization exposes hidden work and competing priorities.

2

Limit Work in Progress (WIP)

This is Kanban's most powerful and counterintuitive practice. Set a maximum number of items allowed in each column. When a column hits its limit, no new work can enter until something moves out. This sounds like it would slow you down, but it actually speeds delivery because: (1) Team members focus on finishing rather than starting, (2) Bottlenecks become immediately visible, (3) Multitasking is eliminated—context-switching is expensive.

3

Manage Flow

Observe how work moves through the system. Identify where items get stuck (bottlenecks). Smooth flow is the goal—work should move steadily without long waits. Track metrics like Lead Time and Cycle Time to measure and improve. A blockeditem is a signal that something needs attention.

4

Make Policies Explicit

Document and share the rules governing your process: What does 'Ready' mean? What does 'Done' mean? Who can pull work into which columns? What's the priority logic? When is it okay to expedite? Ambiguity causes confusion; explicit policies enable self-organization and consistent decisions.

5

Implement Feedback Loops

Create regular opportunities to inspect and adapt. Kanban suggests several cadences: Daily Standup (synchronize on flow), Replenishment Meeting (decide what enters the system), Service Delivery Review (discuss completed work), Operations Review (analyze system performance), Strategy Review (align with business goals).

6

Improve Collaboratively, Evolve Experimentally

Use models and the scientific method to propose and test improvements. Make hypotheses: 'If we reduce the WIP limit in Development, we'll reduce Cycle Time.' Run experiments. Measure results. Adjust based on evidence, not opinions. Small, incremental changes are safer than big-bang transformations.

Understanding WIP Limits: The Power of Saying 'Not Yet'

WIP limits are the defining characteristic that separates Kanban from just having a task board. Without WIP limits, you have a to-do list; with them, you have a flow management system.

Imagine a 'Development' column with a WIP limit of 3. When 3 items are in progress, no one can start a fourth item—even if they're free. Instead, they must help clear the bottleneck: pair with a colleague, help with testing, or fix a blocked item. This is uncomfortable at first but transformative.

Why WIP Limits Work

  • •Forces finishing over starting—items get completed faster
  • •Exposes bottlenecks—if one column is always at its limit, that's where to focus improvement
  • •Reduces multitasking and context-switching costs
  • •Creates slack—team members have time to help others or improve the process
  • •Makes overload visible—you can't hide an unmanageable workload

Pull vs. Push: A Mindset Shift

In traditional management, work is 'pushed' onto teams by managers: 'Here are your assignments for the week.' Teams become overloaded, work piles up, and delivery slows. In Kanban, team members 'pull' work when they have capacity. When you finish a task, you pull the next highest-priority item from the upstream column. This respects the team's actual bandwidth and creates sustainable pace.

✓ The result: Less stress, fewer context switches, faster delivery of individual items, and a culture of ownership where team members choose their work rather than having it assigned.

Key Kanban Metrics

Track work in progress, throughput, work item age, and cycle time to understand flow. Define the start and finish points consistently. Lead time provides an additional view from request to delivery.

Lead Time

Total time from when a request is made (enters the backlog) to when it's delivered. Includes all waiting time. This is what customers care about—'How long from my request to delivery?'

Cycle Time

Elapsed time from the agreed start point to the finish point, including waiting or blocked time after work starts. If a task starts Monday at 09:00 and finishes Thursday at 09:00, its cycle time is 3 calendar days, even if only 6 hours were spent working on it.

Throughput

Count of items completed per time period. Historical throughput can support a delivery forecast, but an average does not guarantee a date. Consider variation in item size, capacity, and incoming work when communicating a range.

Work Item Age

How long an in-progress item has been in the system. Aging items signal problems—they might be blocked or more complex than expected.

Pros and Cons of Kanban

Advantages

  • Easy to start—overlay on existing processes without disruption
  • No fixed iterations—work flows continuously
  • Flexible—adapts to changing priorities instantly
  • Exposes bottlenecks and inefficiencies through visualization
  • Reduces overload with WIP limits
  • No prescribed roles—works with existing team structures

Challenges

  • •Less structure can feel chaotic for teams needing more guidance
  • •Without discipline, WIP limits are ignored or too high
  • •No prescribed cadence for planning and delivery
  • •Reliable forecasts require consistent flow data and explicit assumptions
  • •Can lead to endless refinement without regular retrospectives
  • •Requires mature teams capable of self-organization

When to Use Kanban

Kanban excels in environments where work arrives unpredictably and 'Sprints' feel artificial:

Use Kanban When:

  • •Support and maintenance teams handling tickets
  • •Operations and IT service management
  • •DevOps and continuous deployment environments
  • •Content production and editorial workflows
  • •Service desks and help desks
  • •Personal productivity and task management
  • •Teams that need to respond to emergent priorities
  • •Any team that wants to improve their existing process incrementally

When Kanban May Not Be Ideal

  • •Teams that benefit from the structure of fixed iterations
  • •New products needing the focus of Sprint Goals
  • •Teams expecting guaranteed dates without accounting for uncertainty in delivery forecasts
  • •Teams that struggle with self-organization and need more framework

Real-World Example: A DevOps Team

A DevOps team handles deployments, infrastructure requests, and incidents. Its board shows Backlog, Analysis, In Progress, Review, and Deployed. Explicit WIP limits make overload visible. An agreed expedite policy explains how urgent incidents are handled and how they affect other work. Flow metrics help the team discuss service expectations with internal customers. These practices can also complement sprint-based work; using sprints does not mean waiting to respond to an outage.

Key Takeaways

  • 1Kanban is about flow—work moves continuously without fixed iterations
  • 2Visualization makes all work visible; nothing is hidden
  • 3WIP limits are the key to faster delivery—stop starting, start finishing
  • 4Pull systems respect team capacity and prevent overload
  • 5Flow metrics (Lead Time, Cycle Time, Throughput) guide improvement
  • 6Kanban is evolutionary—start where you are and improve incrementally

Kanban

Choose What to Put into Practice

Pick the points that fit your idea or project. We’ll create a Space with those tasks so you can put this page into practice.

  1. 01Choose the tasks that matter to you.
  2. 02Set up a Space with your selected tasks.
  3. 03Add owners, dates and details in Edworking.
Include in my Space

0 tasks selected

Select at least one task to set up your Space.