methodatlas
Engineering

Kanban

Turns technical problems, assumptions, and next steps into a tangible result through mapping the workflow, making work visible, and improving bottlenecks.

Core question
How does work flow through the stages, where does it queue up, and which policy keeps WIP limits intact?
MediumWorkshop + asyncOngoing
Open runsheetPlan adoptionStart comparison
Purpose

The method helps clarify technical problems, hypotheses, and next steps concretely. It decomposes technical problems into testable parts. The outcome is captured as a Kanban board, WIP policies, and flow metrics.

How it works

The team follows the steps: map the workflow, make work visible, set WIP limits, measure flow, and improve bottlenecks. Each step is captured visibly. At the end, a Kanban board, WIP policies, and flow metrics are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

Kanban · Flow BoardMake work visible, limit WIP, detect blockers, and regularly review flow metrics
KanbanThe visual shows a Kanban board with columns, WIP limits, blockers, flow metrics, and policies.Make work visible and limit flowThe board shows status, WIP limits, and blockers so the team actively pulls work through the flow.pullcheckdoneReviewBacklogStory AStory BStory CDoingWIP 2Feature XBug YReviewWIP 1PR #42DoneReleaseDocsBlockerdependent APIMeasure flowReview lead time,throughput, and agingPoliciesKeep pull rules andDefinition of Done visible

Flow

  1. 1Map workflow
  2. 2Make work visible
  3. 3Set WIP limits
  4. 4Measure flow
  5. 5Improve bottlenecks

The runsheet guides execution with 5 phases, timeboxes, 6 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Operations work
  • Support queues
  • Continuous delivery teams

Not good for

  • Teams without WIP discipline
  • Pure milestone planning

Deep dive

In detail

Kanban follows a clear working logic: map the workflow, make work visible, set WIP limits, measure flow, and improve bottlenecks. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. The result is a Kanban board, WIP policies, and flow metrics that makes decisions, learning, or further planning actionable.

Facilitation

Prepare a clear focus question, the right information, and a visible workspace. Plan ongoing with 2-12 people and use the format in a workshop or asynchronously. The method needs structure and preparation; short timeboxes, visible intermediate results, and a parking lot for open questions help.

Output artifacts
Kanban boardWIP policiesFlow metrics
Tags
flowwipvisual managementdelivery

Sources

What is Kanban in Project Management?atlassian.com
Artifact templates
Kanban Working TemplateCompact working template for Kanban with context, input, output artifacts, and next step.
canvas

kanban-working-template.md

Compact working template for Kanban with context, input, output artifacts, and next step.

Kanban Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Kanban Board:
  • WIP Policies:
  • Flow Metrics:

Open questions

  • ...

Next step

Owner, date, success signal.

When to choose differently

Short decision aid for existing alternatives.

Scrum

Statt Kanban, wenn du in festen Iterationen mit klaren Rollen und Ritualen liefern willst.

Similar methods

All methods
Delivery
Value Stream Mapping

Turns scope, sequence, and delivery flow into a tangible result through selecting a value stream, mapping current state, and designing a future state.

Operations
Bottleneck Analysis

Turns workflows, data, causes, and improvements into a tangible result by mapping the process flow, measuring waiting time and WIP, and re-evaluating the bottleneck after changes.

Operations
Theory of Constraints

Turns workflows, data, causes, and improvements into a tangible result by clarifying the system goal, identifying the bottleneck, and repeating the cycle after expansion.

Operations
Visual Management

Turns workflows, data, causes, and improvements into a tangible result by selecting important information, making status visible, and adjusting signals.

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".

Engineering
Failure Scenario Analysis

Turns technical problems, hypotheses, and next steps into a tangible result by defining the system or process, collecting plausible failure scenarios, and deriving tests, prevention, and response.