Blog
What Is a Kanban Board? A Plain-Language Guide
Written by Georgii Garanin, Founder, Taskora
TL;DR: A kanban board is a visual board where every task is a card, every column is a stage of the workflow, and cards move left to right as the work moves. WIP limits cap how much work sits in each stage, so the team finishes work instead of starting more of it. This guide covers the parts of the board, how the pull system works, and how to set up your first board in Taskora.
What Is a Kanban Board?
A kanban board is a visual tool that shows work as cards moving across columns, where each column is one stage of the workflow. The board answers three questions at a glance: what work exists, what stage each item is in, and where the team is overloaded. The word kanban is Japanese for a card you can see. Toyota's factories used paper signal cards after World War II to run just-in-time production, and a card moving through a factory became a card moving across a board.
In the late 2000s David J. Anderson carried the idea into software and knowledge work, and the kanban method now runs on six practices: visualize the work, limit work in progress, manage flow, make policies explicit, use feedback loops, and improve through small experiments.
Free to start until November 1, no credit card. After that, a 14-day free trial.
The Parts of a Kanban Board
| Part | What it is | The question it answers |
|---|---|---|
| Column | One stage of the workflow, such as To Do, In Progress, or Done | Where is this work in its journey? |
| Card | One work item, with its owner, details, and history attached | What exactly is this piece of work? |
| WIP limit | A cap on how many cards a column may hold at once | Is the team starting more than it can finish? |
| Swimlane | A horizontal lane that separates urgent work from routine work | Which of these cards needs attention first? |
| Commitment point | The moment an item leaves the backlog and work begins | When did we promise this? |
The clock that matters on a kanban board is lead time, the time between the commitment point and delivery. A board where cards sit still for days is showing you exactly where the bottleneck lives.
How a Kanban Board Works
A kanban board runs on pull. A card moves to the next column only when someone has the capacity to take it, and a full column stays full until the work in it moves on. When a column reaches its WIP limit, the rule is simple: finish what is there before starting anything new. Teams call this swarming, and it is the difference between a board that looks busy and a team that ships.
The pull system exists because work usually arrives faster than any team can finish it, so the real decision is how much work sits in progress at once. The board makes that decision visible, and the limits make it enforceable.
A kanban board also keeps its history. Nothing is cleared at the end of a cycle, so months of cards turn into a long record of how work actually moves through the team.
What Is a WIP Limit?
A WIP limit is the maximum number of cards allowed in a single column at one time. A column with a WIP limit of 3 cannot hold a fourth card until someone finishes one and pulls it to the next stage.
The limit matters because work in progress is inventory. The more items a team holds open, the longer each one waits, and queueing theory names this trade directly: Little's Law says the average cycle time equals work in progress divided by throughput. Double the open items and each one takes about twice as long to finish.
There is no universal number. A workable starting method: count the cards sitting in your busiest column over one week, then set that column's limit at or just below the typical count. If work still piles up behind the limit, the queue is telling you the stage upstream runs faster than the stage downstream.
One honesty note before you set one up. Taskora gives you the board, the custom statuses, and the transitions, while WIP limits and swimlanes are habits from kanban practice rather than Taskora features, so treat them as advice for how you run any board.
Kanban Board vs Scrum Board
A scrum board states what one sprint promised, and it resets when the sprint ends. A kanban board reflects how the team works all year, and it never resets. Teams that plan in fixed cycles use a sprint board. Teams with continuous inflow, like support and operations, live on kanban boards. Working alone, skip the ceremonies and run one board with a WIP limit of 3. The setup is in personal kanban for remote work. For the full comparison, see scrum vs kanban.
How to Set Up Your First Kanban Board
Step 1: Write down the stages your work actually passes through today, from request to done.
Step 2: Make one column per stage. Start with 3 to 5. Every extra column is one more place for work to hide.
Step 3: Move your current work onto the board as cards. Each card should carry enough detail that someone else could pick it up cold.
Step 4: Decide the rules. A board needs a start status, a final status, and a set of allowed moves between the two. In Taskora, a stream is a project with its own board, and each stream defines its own statuses and allowed transitions, so a card cannot skip the review step.
Step 5: Run the board for a week, then set WIP limits using the busiest-column count from the section above.
Step 6: Review once a week. Move columns that no longer match, and retire statuses nobody uses.
The custom kanban status workflow guide walks Step 4 in detail. For finished boards from support to release, see kanban board examples for software teams.
Kanban Boards in Taskora
Taskora is task management software and a wiki for growing teams. Every stream carries its own kanban board, and docs with version history sit next to the boards, so specs and release notes stay close to the work. When your team wants sprint-like cycles, waves give each stream one that moves through plan, active, and completed, and unfinished tasks roll into the backlog when a wave closes.
Role-based permissions hold on every screen, and each workspace stays isolated from every other. Self-hosting on your own servers is available on request, and the data sovereignty page has the details.
Pricing is flat, one plan, every feature included: $13 per seat per month billed monthly or $10 per seat per month billed yearly. There are no tiers to compare, so nothing on the board is locked behind an upgrade. The teams page shows what a growing team pays and gets. Free to start until November 1, no credit card.
FAQ
What is kanban?
Kanban is Japanese for a card you can see. Toyota used paper signal cards to control just-in-time production, and the card became the unit of work on today's boards.
What is a WIP limit in kanban?
A WIP limit is the maximum number of cards a column may hold at once. When the column is full, the team finishes work in that column before pulling anything new in.
Do kanban boards need WIP limits?
A board works without them, and most teams start there. Limits turn the board from a picture into a control: they force finish-before-start and surface bottlenecks. Count the cards in your busiest column for a week to pick a first number.
What is lead time on a kanban board?
Lead time is the elapsed time between the commitment point, where work starts, and delivery to the customer. Short, steady lead times are the sign of healthy flow.
How many columns should a kanban board have?
Start with 3 to 5 columns, one per real stage of your workflow. Add columns only when the work demands a handoff the board does not show.
Is a kanban board the same as a scrum board?
No. A scrum board shows one sprint's committed work and resets when the sprint ends. A kanban board shows continuous flow and never resets. Some teams run both, and Scrumban is the name for the mix.
Related posts
- How to Choose a Task Management App for a Team of 5 to 20
How to choose a task management app for a team of 5 to 20. An 8-point checklist, what 10 and 20 seats really cost, and five contenders scored against it.
- Scrumban vs Scrum vs Kanban: Which to Pick and How to Switch
Scrumban vs Scrum vs Kanban with a plain answer up front. What you keep, what you drop, and how to move between them without losing your planning rhythm.
- What Is Project Management Software? A Plain-English Guide for Growing Teams
What project management software is, what it should include, and what it should cost a growing team, including why the advertised per-seat rate is rarely the one you pay.