Kanban board

A Kanban board is a visual management tool that represents work flowing through a process. Cards (representing work items) move across columns (representing workflow stages) from left to right as work progresses. The board provides immediate visibility into what's being worked on, what's waiting, and where work is accumulating - enabling teams to manage flow and identify problems before they escalate.

Why it matters

Without visualization, work becomes invisible. Tasks hide in email threads, spreadsheets, and people's heads. Nobody knows the true state of progress. Bottlenecks go unnoticed until deadlines approach. Teams make commitments they can't keep because they can't see their actual capacity.

A Kanban board makes work visible. At a glance, anyone can see what the team is working on, what's blocked, and where queues are forming. This transparency enables better decisions about what to start, what to prioritize, and where to focus improvement efforts. It transforms work from an abstract concept into something tangible that can be discussed and managed.

For product managers, the Kanban board is both a planning tool and a communication device. It shows stakeholders where their requests are without requiring status meetings. It reveals when the team is overloaded. It provides data for conversations about capacity and priorities.

Anatomy of a kanban board

A basic Kanban board consists of columns, cards, and optional work-in-progress limits.

Columns represent stages in your workflow. The simplest board has three columns: To Do, Doing, Done. Most teams customize columns to reflect their actual process - perhaps adding stages for review, testing, or deployment.

Cards represent individual work items. Each card typically shows a title, brief description, assignee, and any relevant tags or indicators. Cards move from left to right as work progresses through stages.

Work-in-progress (WIP) limits cap how many cards can occupy a column simultaneously. When a column reaches its limit, no new cards can enter until something moves out. WIP limits prevent overload and create the productive tension that drives continuous improvement.

Swimlanes divide the board horizontally to separate different types of work, teams, or priorities. A board might have swimlanes for urgent work, regular work, and technical debt - each flowing through the same columns but tracked separately.

Designing your board

Effective boards reflect how work actually flows, not how you wish it flowed.

Map your current process. Before creating columns, understand your real workflow. How does work actually move from request to completion? What handoffs occur? Where does work wait? Design the board to mirror reality.

Start simple. Begin with fewer columns and add complexity only when needed. A board with twelve columns often reflects wishful thinking about process control rather than actual value. Each column should represent a meaningfully different state.

Include waiting states explicitly. Work often waits between active stages - waiting for review, waiting for deployment, waiting for external response. Making these waiting states visible as columns reveals where time is spent.

Consider done criteria. Define what it means for a card to move between columns. When is something "ready for review"? When is it "done"? Clear criteria prevent cards from moving prematurely or getting stuck at boundaries.

Common board structures

Different teams need different board structures.

Development team boards often include: Backlog → Ready → In Development → In Review → Testing → Done. Some teams add columns for deployment or release stages.

Support team boards might include: Incoming → Triaged → In Progress → Awaiting Customer → Resolved. The workflow differs because support work involves external dependencies.

Content team boards often include: Ideas → Research → Writing → Editing → Design → Approved → Published. Creative workflows have different stages than technical ones.

Personal boards can be as simple as: To Do → Doing → Done. Individual productivity doesn't require elaborate process stages.

The right structure is the one that accurately represents your workflow and reveals useful information about flow.

Using the board effectively

Creating a board is easy; using it effectively requires discipline.

Keep it current. The board's value depends on accuracy. Cards should reflect actual status. Daily updates - or better, real-time updates - maintain trust in the board as the source of truth.

Discuss the board, not status. Stand-ups and check-ins should focus on the board itself. Walk through the columns from right to left (done first, then in progress, then waiting). Identify blockers visible on the board. Discuss flow, not individual status reports.

Respect WIP limits. When a column is full, don't cheat by adding more cards. Instead, help clear the bottleneck. WIP limits lose their power if they're routinely violated.

Move blocked items explicitly. When work is blocked, make it visible. Some teams use a blocked tag; others have an explicit Blocked column. Either way, blocked items should be obvious and receive attention.

Review regularly. Periodically examine whether the board structure still serves the team. As processes evolve, boards should evolve too. Add columns that provide useful visibility; remove those that don't.

Physical vs. digital boards

Teams choose between physical boards (sticky notes on whiteboards) and digital tools (Jira, Trello, Asana, Linear, etc.). Each has advantages.

Physical boards provide tangible interaction that many teams find satisfying. Moving a sticky note to "Done" feels like accomplishment. Physical boards are always visible - you can't minimize a whiteboard. They're simple to set up and modify.

Digital boards work for distributed teams who can't share a physical space. They integrate with other systems, provide historical data, and enable sophisticated filtering and reporting. They're accessible from anywhere.

Many co-located teams use both: a physical board for daily work and a digital mirror for remote team members and historical tracking. The key is having one source of truth - if you maintain both, they must stay synchronized.

Common mistakes

Several patterns undermine board effectiveness.

Too many columns create confusion and slow movement. If cards rarely spend meaningful time in a column, it probably shouldn't exist. Optimize for clarity, not comprehensive process documentation.

No WIP limits removes the mechanism that reveals bottlenecks. Without limits, work accumulates everywhere, and the board becomes a colorful but useless display of chaos.

Stale boards lose trust. When cards don't move for days or show statuses everyone knows are wrong, the board becomes decoration rather than management tool. Stale boards get ignored.

Using the board for surveillance rather than management creates resentment. The board should help the team manage their own work, not enable managers to monitor individual productivity. Focus on flow, not utilization.

Confusing the board with the process leads to cargo-cult behavior. Moving cards doesn't make work happen. If the actual process differs from what the board shows, fix the disconnect - either change the process or change the board.

Metrics from the board

Kanban boards generate valuable metrics.

Cycle time measures how long cards take to traverse the board - from entering "In Progress" to reaching "Done." Tracking cycle time reveals process performance and enables delivery predictions.

Lead time measures total time from request to completion, including time spent waiting in the backlog. Lead time is what customers experience.

Throughput counts how many cards complete in a given period. Consistent throughput enables capacity planning.

Cumulative flow diagrams visualize how cards accumulate in each column over time. The shape reveals bottlenecks, variability, and trends that spot checks might miss.

These metrics emerge naturally from disciplined board use. They don't require additional tracking - just honest card movement through well-defined columns.

The board as communication

Beyond process management, the Kanban board serves as a communication tool.

For team members, it answers "what should I work on next?" without requiring coordination meetings. The next card in the highest-priority ready column is the next thing to pull.

For stakeholders, it answers "where is my request?" without requiring status emails. They can look at the board and see exactly where items stand.

For leaders, it answers "how is the team doing?" without interrupting work for updates. The board's shape tells the story - smooth flow or accumulating congestion.

This self-service visibility reduces coordination overhead and increases trust. When work is visible, explanations become unnecessary. The board speaks for itself.