Kanban Basics: Visual Work Management

What is Kanban?

Kanban is a visual system for managing work as it flows through a process. The word comes from Japanese ("kan" = visual, "ban" = board or card).

Unlike waterfall or sprint-based approaches, Kanban is continuous: work moves through stages as capacity allows, rather than being batched into time-boxed iterations.

---

The Three Core Principles

1. Visualize the Workflow

Make all work visible on a board:

┌─────────┬──────────┬────────────┬─────────┬────────┐
│Backlog  │ Ready    │ In Progress│ Review  │ Done   │
├─────────┼──────────┼────────────┼─────────┼────────┤
│ Card 1  │ Card 3   │ Card 5     │ Card 7  │ Card 9 │
│ Card 2  │ Card 4   │ Card 6     │ Card 8  │        │
└─────────┴──────────┴────────────┴─────────┴────────┘

Benefits:

• Transparency — everyone sees current status
• Bottleneck identification — columns with too many cards show problems
• Communication — no "what are we working on?" questions

2. Limit Work in Progress (WIP)

Set maximum limits on how many items can be in each column simultaneously.

Why this matters:

• Prevents context switching (which costs 20-40% productivity)
• Forces prioritization (finish work instead of starting new work)
• Reveals capacity problems early
• Speeds up cycle time

Example WIP limits:

Backlog (∞)  →  Ready (5)  →  In Progress (3)  →  Review (2)  →  Done (∞)

When "In Progress" is full, team members help finish existing work rather than starting new tasks.

3. Manage Flow

Flow is the speed at which work moves through the system.

Improve flow by:

• Reducing batch size — move smaller items faster
• Eliminating blockers — fix dependencies immediately
• Avoiding interruptions — respect WIP limits
• Matching pace — all team members work toward the same sprint goal

---

Key Metrics

Lead Time

Time from request to delivery. Want: Low and predictable.

[\text{Lead Time} = \text{Delivery Date} - \text{Request Date}]

Cycle Time

Time from work starts to completion. Want: Low and predictable.

[\text{Cycle Time} = \text{Completion Date} - \text{Start Date}]

Throughput

Number of items completed per time period. Want: High and consistent.

---

Kanban vs. Scrum vs. Waterfall

---

Getting Started with Your Team

Week 1: Set Up the Board

1. Define your workflow stages (typically 4-6 columns)
2. Set WIP limits (start conservative: 1-2 per person per stage)
3. Move all current work onto the board
4. Daily standup: walk the board right-to-left (prioritize finishing over starting)

Week 2: Monitor Metrics

• Track lead time daily
• Identify cards stuck in one column (blockers)
• Adjust WIP limits if queuing appears
• Celebrate completed work

Week 3: Optimize

• Remove or merge columns that don't add value
• Reduce WIP limits further (if sustainable)
• Establish policy: "Blocked = immediate escalation"
• Plan improvements for next week

---

Common Kanban Anti-Patterns

❌ No WIP limits → Work piles up, multitasking explodes, cycle time increases

❌ Columns with no criteria → Cards stuck, unclear when to move forward

❌ No daily standup → Blockers undetected for days

❌ Completion = shipping → Bugs escape to production

❌ Different board per team → System thinking breaks down

---

Pro Tips

✅ Make blockers visible — Red card = blocked. Stop and unblock immediately.

✅ Automate the metrics — Track cycle time in your board tool, not spreadsheets.

✅ Distinguish 'done' from 'shipped' — Add a 'Ready for Production' column before terminal.

✅ Start small — Better to have 3 columns with discipline than 10 columns with chaos.

✅ Involve the whole team — Kanban works best when everyone owns the board.

---

Next Steps

• Read Agile Fundamentals for philosophy
• Explore Workflow Best Practices for team patterns
• Set up your first board using Agile Workflow Template