# How to design kanban columns (and why fewer is better)

> The columns on your board are your process, written down. Get them right and the board explains itself. Get them wrong and cards sit in limbo.

Source: https://cbse.club/guides/how-to-design-kanban-columns · Updated 2026-11-03

### The one rule: columns are stages where work changes hands or state

A column should exist when a card in it needs a *different kind of attention* than a card in the next column: someone different looks at it, or something different has to happen. “Writing” and “Editing” are different stages. “Writing (part 1)” and “Writing (part 2)” are not.

### How many columns?

For most teams: **three or four** between the inbox and Done. Every extra column is another place for cards to get stuck and another drag to make. If you have more than six, look for columns that can be merged or turned into tags.

### A five-step method

1. **Follow one real piece of work.** Write down every stage it went through, from idea to finished.
2. **Merge stages done by the same person in one sitting.** They don’t need separate columns.
3. **Keep stages where work waits.** “Waiting for review” is worth a column because it reveals queues.
4. **Write a one-line definition** for each column. When can a card enter? When is it ready to leave?
5. **Run it for two weeks** and then change it. Columns are cheap.

### Columns vs tags

Use a **column** for a *stage* (where in the process). Use a **tag** for a *property* (what kind of work, which area, what priority). “Bug” is a tag, not a column. “Urgent” is a tag (or, in CBSE.CLUB, a [golden card](https://cbse.club/features/golden-cards)), not a column.

### What CBSE.CLUB adds for you

Every board already has **Maybe?** (the inbox), **Not Now** (parked work) and **Done**. So you only design the middle: the stages where real work happens. That is why most of our [templates](https://cbse.club/templates) have three or four columns.

### Examples

- **Software:** Ready → In progress → Code review → QA ([sprint board](https://cbse.club/templates/sprint-board))
- **Content:** Writing → Editing → Design → Scheduled ([content calendar](https://cbse.club/templates/content-calendar))
- **Sales:** Contacted → Proposal sent → Negotiating ([sales pipeline](https://cbse.club/templates/sales-pipeline))
- **Studying:** To learn → Revising → Practice papers → Mastered ([study planner](https://cbse.club/templates/study-planner))

### Signs your columns need work

- Cards skip a column most of the time → remove it.
- Cards sit in one column for weeks → it is a queue or a bottleneck; make it visible and fix it.
- People argue about which column a card is in → write clearer definitions.

## Frequently asked questions

### How many columns should a kanban board have?

Usually three to five stages between the backlog and Done. More columns create more places for work to get stuck.

### Should I have a Blocked column?

Usually not. A blocked card is still in its stage; mark it with a tag or comment instead, so it keeps counting toward that stage’s WIP limit.
