methodatlas

Engineering Operating practice

Kanban

Makes work visible, limits it, and guides it through the workflow.

Kanban makes the actual workflow visible, connects it to explicit policies, and actively manages started work. Observations and flow data provide the basis for targeted improvements.

Core question
What helps us finish started work promptly and more predictably within our agreed workflow?
Plan Kanban practiceMethod guide
Start comparison
Give feedbackIs this method useful to you?
Participants
2-12
Time
Ongoing practice

These working sections combine initial setup with ongoing practice. Adapt columns and policies to the actual workflow.

Paper illustration of a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.

  1. Setup

    Define the workflow

    Expose real work and its boundaries.

  2. Policies

    Agree on WIP and policies

    Explicitly control intake and transitions.

  3. Active work

    Manage started work

    Review completion, age and blockers together.

  4. Observe

    Understand flow data

    Review inventory, completions and time together.

  5. Improve

    Try one improvement

    Turn an observation into a testable experiment.

Review started work regularly. Derive one change from waiting and flow data, observe its effects and update policies.

A good fit when

A team or service handles recurring work and can make the shared workflow visible and change it.

Ideal for

  • Operations work
  • Support queues
  • Continuous delivery teams

Not good for

  • Teams without WIP discipline
  • Pure milestone planning

Outputs

  • Agreed workflow

    Board, clear boundaries, WIP policies and SLE.

  • Visible active work

    Current items, age, blockers and next actions.

  • Flow improvement

    Observations, a small experiment and evaluated effects.

Manage the workflow together

Fictional board · 3 started items

Fictional booking app board. Boundaries and limits are example policies; adapt them to your actual workflow.

Ready

Improve search hint

Not started

In progress

WIP limit: 2

Simplify booking

Started 3 days ago

Clarify error message

Started 1 day ago

Review

WIP limit: 1

Check reminders

Blocked

Access missing; started 5 days ago

Done

Update help text

Completed; outside WIP

WIP boundary
WIP starts in “In progress” and ends at “Done”. Currently 3 items; blocked work still counts.
Pull and completion
A full column takes no more work. Available capacity first supports completion and unblocking.
Blocker
Record reason, next action and ownership on the card; keep the item in the workflow.
SLE and learning
State elapsed time and probability transparently, then review against completed Cycle Times. An SLE is not a guarantee.

The Kanban Guide · original educational rendering

First step

Bound one workflow and its purpose. Define when an item starts and when it finishes.

Open the method guide

Good to do first

A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF

Supplies the economically reasoned order for the work flow.

Where to go next?

Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping

Investigates a visible bottleneck as part of the larger value stream.

Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management

Extends the board with visible standards and deviation signals.

Deep dive

Purpose

When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable.

How it works

Work is viewed as an ongoing flow, not a stack of finished tasks. Visible limits and a clear view of wait times direct attention to friction, blockages, and bottlenecks. This creates an operating mode that improves flow instead of just working through lists.

In detail

Kanban has an effect once work is not just visible but the flow is actively steered. Clear policies, WIP limits taken seriously, and regular review of blockages, wait time, and throughput are decisive. Maintaining the board alone changes little; Kanban becomes valuable when overload and bottlenecks are treated as system signals.

Facilitation

Start with real types of work, current bottlenecks, and a board that makes wait zones visible instead of just parking tickets. The tipping point usually lies where WIP limits are used not as policy text but as a daily boundary for intervention. Close with exactly one flow rule the team will consistently watch and track from now on.

The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics
FlowVisual managementDelivery
Sources
The Kanban Guide · May 2025kanbanguides.orgReference for Definition of Workflow, WIP control, active work management, improvement and four flow metrics. Example and working steps are original educational guidance.
In playbooks
Systematically Improve Engineering QualityMove from a vague quality goal through visible flow and tested hypotheses to a durably anchored standard path.
Artifact templates
Kanban: WorksheetPlan setup, initial trials and regular reviews. Select one step to prepare a specific appointment.
markdown

kanban-working-template.md

Plan setup, initial trials and regular reviews. Select one step to prepare a specific appointment.

Kanban: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Set up and continue Kanban Time: Several setup steps, followed by ongoing management and improvement

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Shared board, representative work items, visible policies and start and finish dates. A simple physical board can support the initial work.
  • Roles: People in the workflow · ownership of policies and improvement · stakeholders as needed
  • Advance information: Gather real items, actual waiting and handover steps, known blockers and available time data.
  • Overall time needed: Setup and initial trials across several appointments; ongoing practice afterward.
  • Setup: Define work item types, start and finish points, relevant states, WIP control and transition policies. Establish a Service Level Expectation (SLE) with elapsed time and probability, initially a clearly labeled estimate and later based on historical Cycle Times. Limits fit your workflow and are reviewed; no fixed team-size formula is prescribed.

Prepare for the work steps

Setup: Define the workflow

  • Examples of started and completed work

Policies: Agree on WIP and policies

  • Defined workflow
  • Current started work

Active work: Manage started work

  • Current board
  • Age and blockers of open items

Observe: Understand flow data

  • Stable start and finish definitions
  • Dated work items

Improve: Try one improvement

  • Flow observations
  • Participant feedback

Manage the workflow together

Ready

...

In progress

WIP limit: ...

...

Review

WIP limit: ...

...

Done

...

Working policies

WIP boundary ...

Pull and completion ...

Blocker ...

SLE and learning ...

The Kanban Guide · original educational rendering

Setup: Define the workflow

Expected artifact: Definition of Workflow

Scope · items · start · finish · states

Entry:

...

  • Do columns represent actual states?
  • Are start and finish unambiguous?

Policies: Agree on WIP and policies

Expected artifact: Visible working policies

WIP · pull · blockers · SLE

Entry:

...

  • Do policies prevent uncontrolled starts?
  • Is the SLE labeled as a forecast?

Active work: Manage started work

Expected artifact: Actively managed work

Next action · ownership · blocker

Entry:

...

  • Does blocked work still count as WIP?
  • Does aging work have a next action?

Observe: Understand flow data

Expected artifact: Flow observations

WIP · Throughput · Work Item Age · Cycle Time

Entry:

...

  • Are measurement boundaries stable?
  • Are open and completed items distinguished?

Improve: Try one improvement

Expected artifact: Improvement experiment

Change · expected effect · review

Entry:

...

  • Is the expected effect observable?
  • Will the change be reviewed?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/kanban/run-sheet

Alternatives and neighbors

Fitting alternatives with decision guidance, followed by other related methods.

All methods
Paper illustration of Scrum with its method-specific working model.
Agile
Scrum

Instead of Kanban, when you want to deliver in fixed iterations with clear roles and rituals.

Paper illustration for Bottleneck Analysis.
Operations
Bottleneck Analysis

Measures flow, wait times, and WIP to find the bottleneck and derive relief options.

Paper illustration for Theory of Constraints.
Operations
Theory of Constraints

Finds a system's bottleneck, aligns work around it, and cyclically checks whether flow improves.

Paper illustration for Monte Carlo Forecasting.
Delivery
Monte Carlo Forecasting

Moves scope, sequence, and delivery flow toward a concrete result through "formulate the forecast question", "choose historical flow data", and "update the forecast regularly".

Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis

Thinks through failures in advance, assesses controls, and shows gaps in testing, prevention, and response.

Paper illustration for Fault Isolation.
Engineering
Fault Isolation

Narrows down the fault space and symptoms step by step until only a few hypotheses and targeted tests remain.

Constraints and origin
MediumWorkshop + asyncOngoing

Profile

Method form
Operating practice
Participants
2-12
Time
Ongoing
Maturity
Canonical
Origin
Toyota Production System
Value Stream Mapping workspace showing the question, observations, and next decision.
Next up: Value Stream Mapping