Kanban Board: Columns, Examples & Setup [2026]

The kanban board is one of those tools so simple it's easy to underrate — columns, cards, and a rule about how much work fits in each column. Yet a well-designed board does something powerful: it makes a team's entire workflow, and every bottleneck in it, visible at a glance. This guide explains the kanban board in full — its elements, how to design the columns, real examples, physical versus digital boards, how to build and use one, and how it appears on the PMP and CAPM exams.

What is a kanban board?

A kanban board is the visual tool at the heart of Kanban — a board that maps a team's workflow into columns and displays each piece of work as a card that moves through those columns from left to right as it progresses. Its job is to make work visible: at any moment, anyone can look at the board and see what's waiting, what's being worked on, and what's finished.

That visibility is the whole point. Instead of work hiding in inboxes, task lists, and people's heads, a kanban board puts it all in one shared, physical or digital space — an "information radiator" that keeps the team aligned without status meetings. But a kanban board is more than a to-do list on a wall. What makes it a kanban board specifically is that it mirrors the real workflow, limits how much work is in progress, and is used to manage the flow of work through the system. Get the design right and the board doesn't just track work — it actively surfaces where work is getting stuck.

The elements of a kanban board

A kanban board is made of a few simple parts that combine into a complete picture of the work. Understanding each one is the key to designing a board that actually helps.

The building blocks are straightforward:

• Columns represent the stages of the workflow — the steps work passes through, such as To Do, In Progress, Review, and Done.
• Cards represent individual work items, one per task, usually holding a title, an assignee, and any relevant details.
• WIP limits cap how many cards a column can hold at once (the "WIP 3" and "WIP 2" above), forcing the team to finish work before starting more.
• Swimlanes are horizontal lanes that group work by type, priority, or team — for example, an "expedite" lane for urgent items that need to jump the queue.
• Commitment and delivery points mark where an item is committed to (pulled into active work) and where it's delivered (done). The time between the two is the item's lead time.

Together, these turn a blank board into a live map of the work — and, crucially, of where it's flowing smoothly and where it's stuck.

Ready to take the next step in project management?

200,000+ Learners Trust Our Instructors

Get PMP® Certified

The gold-standard credential for experienced PMs

PMP Training →

Get CAPM® Certified

The entry-level PM credential — no experience required

CAPM Training →

Learn Project Management

Master PM from beginner to project manager

PM Course →

Kanban board columns

The columns are the most important design decision on a kanban board, because they define what the board can show you. The golden rule is that columns should mirror your team's actual workflow — the real stages work passes through — not a generic template. A board whose columns match reality reveals bottlenecks; one that oversimplifies hides them.

The classic starting point is three columns — To Do, In Progress, Done — which is fine for very simple work. But most real workflows have more steps, and the board should reflect them. A software team's board might read Backlog → Ready → In Development → Code Review → Testing → Done; a content team's might be Ideas → Writing → Editing → Design → Published. The key is that any stage where work can pile up deserves its own column, because that's the only way a delay there becomes visible. Some teams also split a column into "doing" and "done" sub-columns to make handoffs between stages explicit. The temptation is to keep the board simple with just three columns, but if work really flows through five stages, three columns will hide the two where it gets stuck. Design the columns around the work, and the board earns its keep.

Kanban board examples

Kanban boards adapt to almost any kind of work, and seeing a few examples makes the pattern concrete. The columns change to fit the process, but the left-to-right flow stays the same.

• Software development board: Backlog → Ready → In Development → Code Review → Testing → Done. WIP limits on development and review keep the team from starting more than it can finish, and the review column quickly reveals when work is stacking up waiting for a reviewer.
• Marketing / content board: Ideas → Writing → Editing → Design → Scheduled → Published. Each piece of content flows through the stages, and a glance shows whether the bottleneck is in writing, editing, or design.
• Personal / to-do board: To Do → Doing → Done, with a strict WIP limit of one or two on "Doing." Even a simple personal board benefits from the core discipline: finish what you started before picking up something new.

Across all of these, the board does the same job — it visualizes the flow of work through a real process. The columns are tailored to the team, but the principles (visualize, limit WIP, watch the flow) are identical whether the work is code, content, or errands.

Physical vs. digital kanban boards

Kanban boards come in two forms, and the right choice depends mostly on where and how the team works. A physical board is a whiteboard or wall with sticky-note cards. It's simple, tactile, and highly visible to anyone walking past, which makes it excellent for co-located teams — the act of physically moving a sticky note across the board is surprisingly satisfying and keeps the board top of mind.

A digital (online) board lives in software and is the norm for remote or distributed teams. Beyond simply being accessible from anywhere, digital boards add capabilities a whiteboard can't: they store history, automatically calculate flow metrics like cycle time and throughput, enforce WIP limits, and integrate with other tools. Many project and work-management tools offer kanban boards, and simple standalone options exist too. The trade-off is that a digital board can become "out of sight, out of mind" if the team doesn't keep it open and current. For a co-located team, a physical board's constant visibility is a real advantage; for anyone distributed, a digital board is the practical choice — and the metrics it captures are a genuine bonus.

How to create a kanban board

Building a kanban board is quick, and the steps are the same whether it's physical or digital:

1. Map your workflow into columns. Identify the real stages your work passes through and make each one a column. Resist the urge to oversimplify.
2. Create a card for each work item. Add the tasks currently in flight and those waiting, one card each, with enough detail to be understood at a glance.
3. Set WIP limits. Decide how many items each stage can hold at once, based on team size and capacity, and mark the limits on the columns.
4. Define your commitment and delivery points. Clarify where work is committed to (pulled into active progress) and where it's considered delivered.
5. Make your policies explicit. Write down the rules — what "done" means for each column, how items are prioritized — so everyone shares the same understanding.
6. Start pulling work, then improve. Begin moving cards, respect the WIP limits, and adjust the columns and limits as you learn what your flow actually needs.

The first version doesn't have to be perfect. Start with your best guess at the workflow, and let the board itself show you where the columns or limits need adjusting.

How to use a kanban board

Using a kanban board well is a matter of a few daily habits. Work is pulled, not pushed: when a person or a stage has capacity, they pull the next item from the column to their left, rather than having work assigned to them regardless of load. As work progresses, cards move across the board to reflect their real status, so the board always shows the truth.

The two disciplines that make the board work are respecting the WIP limits — never starting more than a column allows — and watching for bottlenecks, which show up as cards piling up in one column while the next stays empty. When that happens, the team's job is to help clear the blockage before pulling in new work. Over time, the board's flow can be analyzed with a cumulative flow diagram to spot trends in cycle time and throughput. Used this way, the board isn't just a place to track tasks; it's a live instrument for managing and improving how work flows.

Scrum board vs. kanban board

A scrum board and a kanban board look similar — both use columns and cards — but they work differently because the frameworks behind them differ. A scrum board is tied to a sprint: it holds only the work committed for the current sprint, and it's reset at the start of each new sprint when a fresh batch of work is pulled in. Its purpose is to track progress toward the sprint goal over a fixed timebox.

A kanban board is persistent and continuous: work flows onto and off the board constantly, with no sprint boundaries or resets, and its defining feature is WIP limits rather than a sprint commitment. Where a scrum board answers "how are we doing against this sprint?", a kanban board answers "how is work flowing right now?" The two also differ in cadence — a scrum board follows the sprint rhythm, while a kanban board runs continuously. Teams that blend the two approaches, as in scrumban, often use a persistent, WIP-limited board while keeping some of Scrum's structure. The board is a reflection of the method: sprint-based for Scrum, flow-based for Kanban.

Kanban Boards on the PMP® and CAPM® Exams

Because the current PMP exam covers agile and hybrid delivery heavily, the kanban board appears as a way to visualize work and manage flow — an example of an information radiator that makes the state of work transparent to the whole team. You're expected to understand that the board mirrors the workflow, that WIP limits cap work in progress, and that the board is used to spot and clear bottlenecks.

Situational questions tend to test the board's purpose rather than its mechanics. Watch for scenarios where work is invisible or bottlenecks are hidden, where a board doesn't reflect the real workflow, or where WIP isn't limited — the right answers favor making work visible, mirroring the actual process, and limiting WIP to improve flow. The distinction between a persistent kanban board and a sprint-based scrum board is another common test point. Our PMP Complete Study Guide, the most complete on the market, covers Kanban and visual work management as the exam frames them.

PMP Practice Question: Kanban Board

A team's kanban board has three columns: To Do, In Progress, and Done, but its work actually flows through development, code review, and testing before completion. Items have been taking longer and longer to finish, and the team suspects code review is the constraint — though every active item sits lumped together in the single In Progress column, so nobody can point to where work is piling up. The team lead wants to act on the suspicion this week.

What should the team do first?

a) Record each item's real stage in its card description and produce a weekly report of where items are sitting.

b) Split the In Progress column into columns that mirror the real workflow stages, each with its own work-in-progress limit.

c) Move a second reviewer onto code review now, since the team already has a good idea where the constraint is.

d) Set a work-in-progress limit on the existing In Progress column so fewer items are in flight overall.

Correct answer: B.

Rationale: A kanban board earns its keep by visualizing the actual workflow, and the buried problem in this scenario is visibility: the suspected pile-up is invisible because three real stages share one column. Splitting the columns to mirror the true stages makes the constraint show up on the board itself as cards stacking in Code Review, confirms or corrects the team's suspicion, and gives each stage a WIP limit that manages flow from then on. The close alternatives each miss part of that: a blanket limit on the merged column improves flow arithmetic but still cannot show where work piles up; assigning a second reviewer acts on an unconfirmed guess and builds no lasting visibility even if the guess happens to be right; and stage notes in card descriptions record the same information in a form nobody can see at a glance, which is the reason a board exists. To drill this kind of visual-workflow judgment, work through our PMP practice exams or, at the entry level, our CAPM practice exams.

Ready to take the next step in project management?

200,000+ Learners Trust Our Instructors

Get PMP® Certified

The gold-standard credential for experienced PMs

PMP Training →

Get CAPM® Certified

The entry-level PM credential — no experience required

CAPM Training →

Learn Project Management

Master PM from beginner to project manager

PM Course →

Frequently asked questions