Kanban board columns: how to design your stages
In this article
Columns are the backbone of a Kanban board. Each one represents a stage work goes through, from the moment someone proposes it until it is done. When columns match your process, the board shows where tasks pile up. When they do not, the team stops using it.
This guide covers how to define your board's columns, how many to use and a few examples you can adapt.
The three basic columns
Every Kanban board starts from three states:
- To do: agreed tasks nobody has started yet.
- In progress: tasks someone is working on.
- Done: finished tasks.
For a team that is just starting, or for a personal project, these three are enough. If this is your first board, read what a Kanban board is first.
How to define the columns for your process
Columns should describe how your team works today, not how it should work in theory. These steps help you find them.
- Follow a recent task from start to finish. Note each moment it changed hands or status: someone wrote it, someone reviewed it, a client approved it.
- Group similar steps. If design review and copy review are done by the same person, a single "In review" column may be enough.
- Make waiting visible. If a task spends days waiting for approval, a "Waiting for approval" column exposes that time.
- Define when a task is done. Agree on what "Done" means for your team: published, delivered to the client or deployed.
How many columns to use
Three to six columns work for most small teams. Past six, the board gets hard to read and cards spend too little time in each stage for the column to tell you much.
A practical rule: add a column only when many tasks sit in a state the board does not show. And remove columns that are almost always empty.
Column examples by team
Marketing and content
Ideas, Writing, Review, Scheduled and Published. The review column shows how many drafts are waiting for a second read, which is usually where content gets stuck.
Software development
Backlog, To do, In development, In review and Done. If the team deploys separately, a "Ready to deploy" column shows what is finished but not in production yet.
Hiring
Applicants, First interview, Technical test, Offer and Hired. Each card is a candidate and the description keeps the notes from every interview.
Support and bugs
Reported, Investigating, In progress, Waiting on customer and Resolved. The waiting column separates what depends on the team from what depends on someone else.
Best practices for columns
- Use names that describe a state. "In review" is clearer than "John" or "Misc".
- Give each stage a color. It helps people recognize columns at a glance, especially on busy boards.
- Set work in progress limits on active columns. That way you spot the stage where work piles up. We explain how in our guide to Kanban WIP limits.
- Review your columns every few months. Processes change and the board should keep up.
How to create columns in Onion
In Onion you can create, rename and reorder columns by dragging them, and pick one of nine colors for each. Cards move between columns with drag and drop or from the Status property inside each card. If you prefer a table, list view groups cards by column. See all board and view features or create your board at app.getonion.app.