Kanban

What Is Kanban?

Kanban is a visual, pull-based workflow management method that helps people see work, limit work in progress, and complete tasks reliably. It uses cards on a board to show each item from request through completion.

The word kanban is Japanese for a visual sign or signal. At Toyota, physical cards signaled when a production station needed more parts. The modern Kanban Method applies this demand-and-capacity idea to knowledge work, including software, marketing, support, and operations. A board alone is not kanban. The method also needs clear policies, limits on active work, and regular flow improvement.

Kanban does not require fixed-length sprints, new job titles, or a complete process redesign. Teams begin with their current workflow and improve it gradually, making it useful when requests are unpredictable or priorities change often.

How Kanban Works

Kanban connects incoming demand to available capacity. Work moves forward only when the next stage can accept it.

1. Map the stages work passes through, such as Requested, Ready, In Progress, Review, and Done.
2. Create one card for each meaningful item with enough context to understand the request.
3. Define entry and exit policies for every stage.
4. Set a work-in-progress, or WIP, limit for active stages where congestion is likely.
5. Pull the highest-priority ready item only when capacity is available under the WIP limit.
6. Mark blocked work, identify the needed dependency or decision, and remove the blocker.
7. Deliver the completed item to its customer, user, or receiving team.
8. Review flow regularly, identify constraints, and test small changes.

For example, a content team may limit its writing column to three articles. If three drafts are underway, the team helps edit, approve, or unblock existing work instead of starting a fourth. The limit exposes choices hidden by multitasking.

Kanban Board Components and Working Agreements

A kanban board is a shared workflow view. Columns represent stages, and cards represent work items. A backlog or request queue holds possible work before commitment. The commitment point is where the team accepts responsibility for an item. The delivery point is where the customer can use or receive the result.

Boards may use swimlanes to separate work types, blocked-work markers to show delays, and service classes to define handling rules. For example, an urgent production incident may be expedited, while routine improvement work follows the normal queue. Expedited work should be rare, or it can overwhelm normal work.

Explicit policies make board movement dependable. A definition of ready might require a clear request, owner, and acceptance criteria. A definition of done might require review, testing, approval, or customer notification. These rules prevent cards from appearing complete when work remains. Teams managing digital products can apply the same clarity to app design and development, where review and release steps are often separate from coding.

Kanban Principles and Core Practices

The Kanban Method is evolutionary. Its principles are to start with the current process, pursue incremental change, respect existing roles and responsibilities, and encourage leadership at every level. This reduces disruption while allowing improvement through observation and collaboration.

Its recognized practices are to visualize work, limit WIP, manage flow, make policies explicit, use feedback loops, and improve collaboratively through experiments. Daily flow reviews, replenishment meetings, service-delivery reviews, and improvement sessions provide feedback at different levels. The Kanban Guide emphasizes managing services and flow, not merely organizing a task list.

Kanban Metrics That Measure Flow

Kanban metrics help teams understand their system rather than judge individual effort. Lead time is the elapsed time from a customer request or commitment point to delivery. Cycle time is the time from starting active work to delivery. Throughput is the number of completed items in a period. Work item age shows how long an unfinished item has been active and can reveal stuck work.

A cumulative flow diagram plots cards in each workflow stage over time. A widening band often signals a growing queue or bottleneck. These measures are most useful when teams study ranges, trends, and variation. An average can hide long delays, and employee targets can encourage gaming, such as splitting work into tiny cards or moving cards too early. Use measurements to improve the system, not rank people.

Benefits of Kanban

Kanban can improve service delivery without forcing a team into a fixed project rhythm.

• It makes commitments, queues, dependencies, and stalled work visible.
• WIP limits reduce context switching and encourage finishing work before starting more.
• It surfaces bottlenecks early, allowing teams to help where work accumulates.
• It can improve delivery predictability by using actual flow history instead of estimates alone.
• It allows priorities to change as capacity opens, which suits incoming requests.
• It supports continuous improvement through small, measurable experiments.
• It works across teams, including groups using AI tools for agencies to coordinate client requests, reviews, and handoffs.

Practical Limits and Common Kanban Pitfalls

Kanban is simple to begin, but disciplined use is harder than drawing columns on a screen.

• Broad columns such as “Doing” can conceal queues, reviews, and dependencies.
• Arbitrary WIP limits can frustrate teams if they are not adjusted using workflow evidence.
• Hidden work, meetings, rework, and approvals create misleading flow data when absent from the board.
• Treating every request as urgent defeats prioritization and makes expedited work normal.
• Bypassing the board removes visibility needed to manage capacity.
• Moving cards without meeting policy creates false progress and surprise rework.
• Ignoring blocked cards lets aging work accumulate and makes delivery unpredictable.
• Fixed-scope, fixed-date initiatives may need complementary forecasting, dependency planning, and milestone management.

What Is Kanban Used for in Business?

Kanban works best where work arrives continuously and demand must be balanced against real capacity.

• Software teams use it for defects, features, code review, testing, and releases.
• IT support teams use it for incidents, requests, maintenance, and urgent escalations.
• Marketing teams use it for briefs, drafting, design, legal review, publishing, and reporting.
• Recruiting teams use it to track applicants from sourcing through onboarding.
• Legal and finance operations use it for contract reviews, invoice exceptions, approvals, and close activities.
• Sales and customer success teams use it for handoffs and follow-up work after a deal closes.
• Manufacturers use replenishment signals to replace consumed inventory and coordinate production.
• Individuals use simple boards for household tasks, study plans, or job searches, provided the board reflects real capacity.

Kanban vs. Scrum

Kanban and Scrum are both Agile approaches, but they organize work differently. Neither is universally better. The choice depends on whether work is continuous and variable or can be planned in short, stable batches.

Some teams combine practices, such as using a Kanban board and WIP limits inside Scrum. This can work when the rules are clear and solve a specific flow problem.

How to Start Using Kanban

Start small, learn from actual work, and avoid designing an elaborate board before observing the process.

1. Choose one repeatable workflow with a clear customer or recipient.
2. Observe how work moves, including waiting, review, rework, and external dependencies.
3. Create only the columns needed to represent real stages.
4. Write simple policies for when cards may enter and leave each stage.
5. Set conservative WIP limits where work piles up most often.
6. Hold a brief daily flow review focused on blocked items, aging work, and capacity.
7. Record baseline lead time, throughput, and work in each stage before judging results.
8. Adjust one constraint or policy at a time, then observe whether flow improves.

A physical board, spreadsheet, or dedicated digital tool can support kanban. Kanban in Excel can be sufficient for a small workflow, especially when one person maintains it. As teams, dependencies, or reporting needs grow, a shared tool may be easier. The important factor is whether the board stays current and supports honest decisions about capacity.