# What Is a Kanban Board? Columns, WIP Limits and an Example > A kanban board shows work as cards moving through columns. Learn the parts, WIP limits, a real kanban board example, kanban vs scrum and common mistakes. _Source: https://professionalstoolkit.com/articles/what-is-a-kanban-board — The Professional's Toolkit · updated October 2026_ --- A kanban board is a visual board that shows work as cards moving through columns, one column per stage, from *to do* to *done*. Its real job is not the picture. It limits how much work is in progress at once, so the team finishes things before starting new ones. The method in one line: map your real workflow into columns, put every piece of work on a card, cap each active column, and pull new work only when a slot opens. That cap, the WIP limit, turns a wall of tasks into a system. **4** — flow measures the Kanban Guide asks teams to watch: WIP, throughput, item age, cycle time - **3** — core practices: visualize, manage, improve the workflow - **2006** — modern knowledge-work Kanban begins, at Corbis - **0** — sprints or required roles in Kanban ## What a kanban board is and where it comes from Kanban is a Japanese word for a signboard or signal card, and the method grew up on factory floors. The Kanban Guide traces it to the Toyota Production System and to Taiichi Ohno and W. Edwards Deming, and dates modern Kanban for knowledge work to 2006 at Corbis [1]. Today the same idea runs software teams, content calendars, support queues and hiring pipelines. Anything with repeatable stages fits. The guide defines Kanban as a strategy for optimizing the flow of value through a visual, pull-based system. Pull is the key word. In a push system, a manager hands out work whenever it arrives, and people juggle it. In a pull system, a person takes the next card only when they have room for it. The board makes that room visible. Anyone can see at a glance where work is waiting and who is overloaded. ## The parts of a kanban board: columns, cards and WIP limits Every working board has the same few parts. The guide calls the agreement behind them the Definition of Workflow: what counts as a work item, where work starts and finishes, the states in between, how work in progress is controlled, the explicit rules for moving items, and a service level expectation for how long an item should take. The board is simply the picture of that agreement. There is no required layout. ### Columns Each column is a state the work really passes through. A starter board has To do, Doing and Done. Most teams soon split Doing into the steps that actually differ, such as Drafting, Review and Approved. Add a column only when work waits there or changes hands. If nobody ever waits in a column, it is decoration. ### Cards One card is one deliverable a single person can finish. It carries a title and an owner, and usually a due date, a short checklist or a link to the file. Keep cards small enough to move within days. If a card takes a month, it is a project, not a card. ### WIP limits A WIP limit is the maximum number of cards allowed in a column at once. When Review holds three cards and its limit is three, nobody starts new drafts; the team helps clear Review first. **This is the part most teams skip, and it is the part that makes kanban work.** The guide is blunt about it: work in progress must be explicitly controlled, often with limits or tokens, so items are pulled only when capacity is available. ### Swimlanes Optional horizontal rows split the board by person, client or priority. They keep a busy board readable without adding columns. > 💡 **Limit the column, not people:** Put the WIP limit on the column where work queues, usually review or approval. When it is full, the team helps clear it instead of starting something new. ## How to set up a kanban board in six steps 1. **Map the real workflow.** Trace the stages one recent piece of work went through, including the waiting. Those become your columns. 2. **Define done.** Agree what finished means for the last column, and what a card needs before it can leave each stage. 3. **Fill the backlog.** Put every open piece of work on a card in the first column. Hidden work breaks the picture. 4. **Set WIP limits.** Start with about one card in progress per person on each active column, then adjust. A single reviewer can carry two, so one item waits ready while the other is in work. A limit that never bites is too high. 5. **Pull, don't push.** When a slot opens, the person pulls the highest-priority card from the column to the left. 6. **Review every week.** Look at where cards pile up and how long they sit, then change one rule at a time. The guide asks teams to watch four flow measures: work in progress, throughput (items finished per unit of time), work item age, and cycle time from start to finish. You do not need charts on day one. Writing the start date on each card is enough. Within two weeks you can see which cards are aging and how long a typical item really takes. > ⚠ **Waiting columns still count:** A column like Waiting for client is still work in progress. If it has no limit, half-finished work parks there and the board looks healthier than it is. ## A kanban board example: a five-person content team Here is a kanban board example for a small marketing team that publishes blog posts. It has three writers, one editor and a lead. The columns follow the real path of a post. Ideas and Ready carry no limit, because nobody is working on them yet. Writing is capped at three, one per writer. Editing is capped at two, because one person edits everything. | Column | WIP limit | A card leaves when | |---|---|---| | Ideas | none | A brief and a target keyword exist | | Ready | none | The lead approves the brief | | Writing | 3 | The draft is complete with sources | | Editing | 2 | Edits are accepted and images added | | Scheduled | none | A publish date is set | | Published | none | The post is live and shared | Within two weeks the board tells a story. Editing is always full, and writers finish drafts they cannot hand over. Without the limit they would keep starting new posts, and the pile in front of the editor would grow out of sight. With it, the problem is on the wall. The fix is not more writing. It is a second reviewer on Fridays, or shorter drafts. > 💡 **Date every card on start:** Write the start date on each card when it enters a working column. Two weeks of dates show your real cycle time and which cards are quietly aging. ## Kanban vs scrum: which fits your team Kanban and Scrum both come from agile practice and both use boards, which is why people mix them up. The difference is rhythm. Scrum works in Sprints, fixed-length events of one month or less, and a Scrum Team consists of one Scrum Master, one Product Owner and Developers [2]. Kanban has no sprints and no required roles. Work flows continuously, and the WIP limit, not the sprint, controls the load. Kanban board project management suits work that arrives unpredictably: support tickets, content, marketing requests, operations and client service. Scrum suits a team building a product in planned increments that benefits from a fixed review cycle. Many teams blend the two. A Scrum team adds WIP limits to its sprint board, or a kanban team holds a short planning meeting every two weeks. Pick the rhythm your work actually has, not the one with the better reputation. ## Common kanban board mistakes, and when it gets hard 1. **No WIP limits.** The board becomes a decorated to-do list. Everything is in progress and nothing finishes. 2. **Too many columns.** Twelve stages for a three-person team adds dragging without adding information. Merge stages nobody waits in. 3. **Cards that are too big.** A card that sits in Doing for three weeks hides its own progress. Split it into pieces that move. 4. **A stale board.** If people update it only before the meeting, it shows last week. Moving the card has to be part of doing the work. 5. **Ignoring blocked work.** Mark blocked cards clearly, with the reason, so they get attention instead of aging quietly. The method itself scales well. The paper or spreadsheet version does not. Trouble starts when several teams share work, when one card depends on another, or when a manager wants status across ten boards. Sticky notes cannot notify an owner, and a shared sheet cannot move a card when its status changes. If you want to try the method by hand first, our guide on [how to make a kanban board](/articles/how-to-make-a-kanban-board) covers a physical board and a spreadsheet version, and where each one breaks. ## Tools that run a kanban board for you Every project management tool we checked offers a board view, and on several the board sits on the free plan. Three common starting points: ### Asana — solves this Switch a project to board view and drag each task, shown as a card, from stage to stage. Board view is on the free plan, next to list and calendar views of the same tasks. - Where it stops: The free Personal plan is for 2 users, and each task has a single assignee. - Plan: Personal (Free) - How Asana does it: [Set up Asana boards](https://professionalstoolkit.com/articles/getting-started-with-asana) - More: [Asana](https://professionalstoolkit.com/tools/asana) ### ClickUp — solves this Show a list of tasks as a Kanban board and drag cards across stages; sprint management and a calendar view sit on the same tasks. Kanban boards and unlimited free members are on Free Forever. - Where it stops: Free Forever caps storage at 60MB and 5 Spaces. - Plan: Free Forever - How ClickUp does it: [Set up ClickUp boards](https://professionalstoolkit.com/articles/how-to-get-started-with-clickup) - More: [ClickUp](https://professionalstoolkit.com/tools/clickup) ### Notion — solves this Build a task database and display it as a board view; the same records can also render as a timeline. Databases with subtasks, dependencies and custom properties are on the free plan. - Plan: Free - How Notion does it: [Build a Kanban board in Notion](https://professionalstoolkit.com/articles/notion-project-management) - More: [Notion](https://professionalstoolkit.com/tools/notion) For the full field, grouped by the kind of team each one fits, see our comparison of [kanban board software](/articles/kanban-board-apps). ## FAQ **Can one person use a kanban board?** Yes. Personal kanban uses the same columns with a small limit on Doing, a few cards at most. It works well for freelancers and anyone juggling many small tasks. **What is the difference between a kanban board and a to-do list?** A to-do list only records tasks. A kanban board shows the stage each task is in and caps how many can be in progress, so it exposes bottlenecks a list hides. **How many columns should a kanban board have?** Start with three to six. Add a column only where work waits or changes hands, and merge any column where cards never sit. **Is a digital kanban board better than a physical one?** A physical board is faster to start and very visible for a team in one room. A digital board wins once people work remotely, cards need files and owners need notifications. ## The bottom line A kanban board is worth having only if it changes how work moves. Columns and cards make the work visible; WIP limits make it finish. Start with your real stages, keep cards small, cap the busy columns, and review where cards pile up every week. Run it on paper or a spreadsheet while the team is small. Move to a tool once owners need notifications, cards depend on each other, or someone needs status across several boards. ## Sources [1] kanbanguides.org — https://kanbanguides.org/the-kanban-guide/2020.12 (Oct 2026) [2] scrumguides.org — https://scrumguides.org/scrum-guide.html (Oct 2026)