Kanban: A Complete Guide to Visual Project Management

Kanban is a visual workflow management method that originated in Toyota’s manufacturing system. Unlike Scrum, which works in fixed timeboxes (sprints), Kanban is continuous — work flows through the system as capacity allows. Kanban is ideal for teams with unpredictable workloads, ongoing maintenance tasks, and a need for flexibility.

The Kanban Board

A Kanban board visualizes work as cards moving through columns. Each column represents a stage in your workflow:

Backlog → To Do → In Progress → Review → Done

Physical Boards

A whiteboard with sticky notes. Simple, visible, and effective for co-located teams. Each sticky note is a task, and different colors can represent different types of work.

Digital Boards

• Trello — simplest option, free, good for individuals and small teams
• Jira — enterprise Kanban with reporting and integration
• Linear — modern issue tracker with Kanban view
• Notion — customizable Kanban databases
• GitHub Projects — free, integrated with repositories

Core Principles

Visualize the Workflow

Make every piece of work visible on the board. Hidden work cannot be managed. Every card should represent a unit of value — a feature, a bug fix, a task, a user story.

Limit Work in Progress (WIP)

WIP limits are the most important Kanban practice. Each column has a maximum number of cards allowed at one time:

Backlog:    No limit
To Do:      5 cards
In Progress: 3 cards
Review:      2 cards
Done:        No limit

When a column reaches its WIP limit, the team must finish something in that column before starting new work. This reveals bottlenecks. If “In Progress” is always at its limit while “Review” is empty, the team knows they need to focus on completing work rather than starting new work.

Manage Flow

Track how work moves through the system. Are cards piling up in one column? That is your bottleneck. The goal is smooth, predictable flow from left to right.

Make Process Policies Explicit

Define what each column means and what is required to move a card:

To Do:        Ready for someone to start working on
In Progress:  Someone is actively working on this
Review:       Work is complete, needs peer review
Done:         Reviewed, merged, and deployed

Improve Collaboratively

Use the board as a diagnostic tool. In regular retrospectives, look for patterns, bottlenecks, and process improvements.

Setting Up Your Kanban Board

Step 1: Map Your Workflow

Start with the simple three-column setup and add columns as needed:

Personal Kanban:
  Backlog → Today → Doing → Done

Development Team Kanban:
  Backlog → Design → Development → Review → Staging → Deployed

Content Team Kanban:
  Ideas → Research → Writing → Editing → Published

Step 2: Add WIP Limits

Personal:
  Today:    3 (do not start more than 3 things in a day)
  Doing:    1 (focus on one thing at a time)
  Review:   2 (batch reviews)

Team:
  Design:       2
  Development:  3
  Review:       3
  Staging:      2

Step 3: Define Card Types

Use labels or card colors to distinguish work types:

• Feature — new functionality
• Bug — defect fix
• Chore — maintenance, refactoring
• Research — investigation, prototyping

Step 4: Start Using It

Put every piece of work on the board. Move cards when work changes state. Review the board daily.

Key Metrics

Cycle Time

The time a card spends from “started” to “done.” Shorter cycle times mean faster delivery. Track average and percentile cycle times (50th, 85th, 95th).

Throughput

How many cards the team completes per week. Predictable throughput helps stakeholders plan. Track a rolling average over 4-6 weeks.

WIP Aging

How long a card has been in its current column. Cards that are “stale” (in the same column for too long) signal blocked work. Flag any card that exceeds the team’s average cycle time.

Cumulative Flow Diagram

A chart showing the number of cards in each column over time. The distance between lines reveals bottlenecks. When lines spread apart, cards are piling up somewhere.

Personal Kanban

Kanban works for individual productivity too:

Backlog → Today (3) → Doing (1) → Done

Daily routine:

1. Each morning, move up to 3 items from Backlog to Today
2. Choose one item to work on and move it to Doing
3. Focus on that item until it is done
4. Move it to Done and choose the next item

Common Mistakes

No WIP limits. Without limits, the board fills up with “In Progress” items that nobody is actually working on. WIP limits force completion.

Too many columns. Start with 3-5 columns. More columns = more overhead. Add columns only when the team agrees they are necessary.

Cards that never move. If cards stay in “In Progress” for weeks, they are too large or blocked. Break them into smaller cards.

Ignoring the board. The board must be the single source of truth. If work happens without being updated on the board, the board loses its value.

Digital vs Physical Kanban

Both approaches have tradeoffs. Physical boards on whiteboards or corkboards provide a tangible, visible system that builds team awareness — they work well for co-located teams and personal use. Digital tools (Trello, Jira, Notion, Linear) offer remote collaboration, automated workflows, analytics, and integrations. For personal productivity, a physical board is often more effective because it avoids the distractions of digital tools. For team use, digital is essential.

WIP Limits in Practice

Work-in-progress limits prevent multitasking and bottleneck buildup. Start by limiting “In Progress” to 2-3 items per person. When a lane is full, no new work enters until something finishes. This surfaces bottlenecks immediately — if the “Review” lane is full, production stops. Adjust WIP limits based on workflow observation. Lower limits increase focus and throughput. Higher limits hide inefficiencies.

Kanban vs. Scrum

Kanban and Scrum are often compared, but they serve different needs. Scrum uses fixed-length sprints (usually 2 weeks) with a defined set of work committed at the sprint start. Kanban is continuous — work flows as capacity permits. Scrum works best for teams with predictable work cycles and clear project boundaries. Kanban excels for teams with unpredictable work (support, maintenance, operations) or where continuous delivery is the goal. Many teams use both: Scrum for project work and Kanban for operational work. You can also run Kanban within a Scrum sprint to visualize workflow.

Advanced Kanban: Classes of Service

At scale, teams use classes of service to handle different types of work with different priorities:

• Expedite: Critical work that jumps the queue (security patches, production outages). Limit to 1-2 items in the system.
• Fixed Date: Work with a hard deadline. Plan backwards from the deadline to determine when it needs to start.
• Standard: Regular work in the normal workflow. No special handling.
• Intangible: Work with no clear ROI but long-term value (refactoring, documentation, learning). Schedule during slack periods.

Each class has different WIP limits, review cadences, and escalation paths. Classes of service prevent emergencies from derailing all other work.

Kanban Metrics for Continuous Improvement

Beyond the basic Kanban board, several metrics drive continuous improvement. Cycle time measures how long a card takes from start to finish. Tracking average cycle time and its standard deviation helps teams predict delivery dates more accurately. Throughput measures how many cards the team completes per week. A rolling average over four to six weeks smooths out weekly variation and reveals trends. Work-in-progress aging shows how long each card has been in its current column — cards that exceed the team’s average cycle time signal blockers that need attention. The cumulative flow diagram visualizes all these metrics in one chart, showing the number of cards in each column over time. When the colored bands spread apart, work is piling up somewhere. When they converge, flow is smooth. Regular metric reviews — typically biweekly — transform Kanban from a visual management tool into a true process improvement system.

Scaling Kanban Across Teams

When multiple teams adopt Kanban, coordination becomes essential. The scaled approach involves creating a shared services board for dependencies between teams, a portfolio Kanban for strategic initiatives, and cross-team service level agreements (SLAs) for handoffs. Each team maintains its own board while contributing to the larger system. Key practices for scaling: standardize card formats across teams, align on common definitions of done at each workflow stage, and hold joint retrospectives to address systemic bottlenecks. Metrics should be normalized (e.g., cycle time per story point) to allow meaningful comparison between teams. The most successful scaled Kanban implementations prioritize flow efficiency over resource utilization — keeping work moving smoothly matters more than keeping every person busy.

FAQ

How do I handle urgent items that need to jump the queue? Kanban handles urgent items through a class of service called Expedite. Create an Expedite lane with a strict WIP limit of one or two items. Expedite items bypass normal WIP limits and flow through the system as fast as possible. The trade-off is that Expedite items disrupt normal flow, so they should be reserved for genuinely critical work like production outages or security patches. Track Expedite items separately in your metrics so they do not distort your cycle time averages.

What is the ideal WIP limit for a team? A common starting point is two to three items per person in the In Progress column. So a five-person team would set an In Progress WIP limit of 10 to 15. The exact number depends on your workflow, the complexity of your work, and how much context switching your team tolerates. Start with a generous limit and reduce it weekly until you find the sweet spot where work flows smoothly without people feeling starved for tasks.

Can Kanban work alongside Scrum? Many teams use both — a practice often called Scrumban. The team operates in Scrum sprints but uses a Kanban board with WIP limits to visualize and manage workflow within the sprint. This hybrid approach works well for teams that need the structure of time-boxed iterations but also want the flow optimization of Kanban.

For a comprehensive overview, read our article on Bullet Journal Guide.

For a comprehensive overview, read our article on Deep Work Guide.