How to Use Kanban Boards for Project Management (Past 3 Columns)

Last updated: September 10, 2026

Almost every team that adopts a board sets up the same three columns, uses it happily for a month, and then quietly stops looking at it. The cards are still there. Somebody drags one occasionally. Nobody makes a decision because of it.

Most advice about kanban boards for project management stops right where that problem starts. A board with to-do, doing and done is a list rotated ninety degrees: the same information a list already showed you, in a shape that takes more room.

That is not a discipline problem, and a stricter standup will not fix it.

What follows is the part most guides skip: how to name columns so they mean something, what a work-in-progress limit actually does to a team, the four signals a working board sends, and when a board is the wrong instrument entirely.

What makes kanban boards for project management work past three columns?

A board earns its keep when its columns match the places work genuinely waits, and when at least one of those columns has a limit on how much it can hold. Everything else is arrangement.

It helps to remember what the word originally meant. In the Toyota system where kanban started, the Lean Enterprise Institute defines a kanban as "a signaling device that gives authorization and instructions" in a pull system.

The card was never a status label. It was permission to start something, issued only when there was capacity downstream to receive it.

That is the idea most software boards lose. A digital board hands out unlimited permission: anyone can start anything at any time, and the board dutifully records it. Recording is not signaling. If your board can never tell you "not yet," it has become an inventory of intentions.

Why are your kanban board columns the problem?

Three column-naming mistakes account for most dead boards.

Columns named after people. "With Sam" reads as a stage but is actually an assignment. The moment a column belongs to a person, everyone else stops reading it, and the board fragments into private lists that share a screen.

Columns that hide a queue inside them. "In progress" usually contains two very different states: work someone is touching today, and work that finished a step and is sitting there waiting for the next person.

Those two look identical on the board and behave nothing alike. Splitting them into "in progress" and "ready for review" makes your slowest handoff visible for the first time.

Columns nobody ever waits in. If a card passes through a column in under an hour, every time, it is not a stage. Delete it. Columns are for places work rests, and a column that never holds anything is a label pretending to be a step.

The practical test takes one afternoon: take a piece of work that shipped last month and trace where it actually sat still. Those pauses are your columns. Most teams find two or three they never drew.

This is also the reason column design is worth doing inside the tool rather than on a whiteboard first. In Quire the columns on a board are your project's statuses, so adding "ready for review" as a status adds the column, and renaming it renames it everywhere the work is read.

For the underlying model those columns are meant to serve, read the four core kanban principles and five best practices.

What does a WIP limit actually do to a team?

A work-in-progress limit is a cap on how many cards a column may hold at once. It is the single feature that separates a board from a wall of sticky notes, and it is the one teams skip because it feels restrictive.

It is supposed to feel restrictive. Without a cap, starting something new is always free, so it always happens, and a team ends up with eleven things half-done and nothing shipped.

With a cap, the moment a column is full you cannot pull in more work. That leaves exactly one productive option: go help finish what is already sitting there.

The pattern is not unique to boards. Antonio Nieto-Rodriguez, writing in Harvard Business Review, found the same thing in almost every organization he has advised: far too many things running, and far too few that truly matter. A column is where that arrives on a Tuesday morning.

That is the whole mechanism. The limit does not make anyone work faster. It converts a vague shared preference for finishing things into a concrete constraint, felt by the person who wanted to start something and cannot.

Two practical notes. Set the first limit on whichever column piles up most, not on all of them at once, because one working limit teaches the habit and six simultaneous ones just get ignored.

And set it slightly below what the team currently carries, so it actually binds in week one rather than sitting comfortably above reality.

Most tools, Quire included, will not physically stop you from dragging a twelfth card into a column capped at eight. What makes the limit real is that the count sits in the column header, so a breach is visible to everyone the second it happens rather than at the next retro.

Want to know where your work actually piles up? Open a free Quire project, drop last month's finished work onto a board using the stages you think you have, and read the counts. The column that bulges is your constraint, and you found it in an afternoon rather than a quarter.

How do you read what a kanban board is telling you?

A board that is set up properly tells you things without anyone writing a status update. Here is how to read it.

Three of those four are visible from the column counts alone, which is why a board with honest columns replaces most of what a status meeting is for.

The aging card is the one a board hides. A card that has not moved looks exactly like a card that moved yesterday, so it is worth reading the same tasks as a list sorted by date once a week.

To put numbers behind those signals, see how to track key kanban metrics.

When do swimlanes help, and when do they cost you?

Swimlanes split the board horizontally, so each row is a category and each column still means a stage. They are useful and they are overused.

Three board shapes, and what each one buys you:

Quire's board does all three from the same tasks: columns come from your statuses, lanes come from pairing the column axis with a grouping, and Task Bundle is the toggle that keeps subtasks under their parent card.

They help when the row genuinely changes what you would do. Separating expedited work from normal work is the strongest case: an urgent row that visibly jumps the queue makes the cost of interruption obvious to everyone, including the person requesting it.

Separating clients or product areas works for the same reason, when the two streams really do compete for the same people.

They cost you when the row is just a filter someone could have applied. Every lane doubles the vertical reading effort, and a board that no longer fits on one screen stops being glanceable, which was its only advantage over a list.

Splitting by person is the most common version of this mistake, and it recreates exactly the private-list problem good column naming was meant to remove.

The cheap way to test one before committing is to build it from two settings rather than a new board. Quire makes lanes by pairing the column axis with a grouping, so you can column by status and group by priority, look at it for a week, and drop the grouping if the extra row never changed a decision.

For the full treatment of when a second dimension earns its place, read the complete guide to kanban swimlanes.

When should a kanban board move into task management software?

When the board has to carry more than position. A wall of sticky notes teaches the method faster than any tool, and for a single stream of similar work it stays the better board for a long time.

You have outgrown the wall when you keep writing the same four things on every card: who owns it, when it is due, what the sub-steps are, and what happened to it last week. A sticky note holds one of those legibly. Task management software holds all four and remembers the fourth for you.

What you gain is a record. A card that carries its own history answers "why did this sit for three weeks" without anyone reconstructing it from memory, and that question is the one a wall can never answer.

What you lose is real too, and worth saying: the wall is ambient. It is in the room whether anyone opens it or not, and a board inside a tool is only seen by people who go looking. Teams that move a board into software and skip the habit of looking at it end up worse off than they were with paper.

If you are still choosing where the board should live, compare the options in the guide to task management software and task trackers.

How do you run a kanban board in Quire?

The board is one way of looking at tasks you already have, so setting it up is a matter of naming stages rather than building a second system.

Columns come from your project's statuses, which means a card carries the same identity everywhere: rename it on the board and the list already agrees, because there is one record rather than a board copy and a list copy.

That sounds like a small thing until you have watched a team reconcile two views of the same project every Monday.

Take one real card. "Promotion video" sits in Pending with Mei on it and a due date of August 31, tagged Design so it shows up in the design filter. Under it are its own sub-steps, "Prepare storyline" first, each with its own owner and date.

The whole thing moves through the columns as one card. Nobody had to promote "prepare storyline" into a top-level card just to see it, which is what turns a column into an unreadable stack of forty items.

That nesting is a toggle rather than a default. Turning on Task Bundle in the board menu groups subtasks under their parent card, and turning it off gives you a flat board where every task is a peer.

Task Bundle is available on the Professional, Premium, and Enterprise plans. The flat Kanban Board itself is free on every plan. Full details are on the pricing page.

Because the board is a view rather than a copy, the same cards read as a list when you want dates in order, or as a timeline when you want to see what blocks what. The board is where you run the week; it is not the only place the work exists.

For how nesting works on the board itself, see the nested kanban board and task bundles.

When are kanban boards for project management the wrong tool?

Boards are for work that moves through stages. They are actively misleading for two other shapes.

When sequence is the risk. If three cards cannot start until one specific thing finishes, the board shows three cards sitting in the same column looking equally available, and the dependency is invisible. A timeline shows it in one glance.

When the deadline matters more than the stage. A board is bad at dates by design; nothing about a card's position tells you it is due Thursday. Teams that run date-driven work off a board tend to discover the calendar problem late and loudly.

The honest version is that most projects need the board and something else, and the failure is not picking the board, it is picking only the board.

For which view fits which shape of work, read gantt chart vs kanban vs calendar.

Key takeaways

A kanban board becomes useful at the point where its columns stop describing a generic lifecycle and start describing your actual handoffs, including the ones where work sits waiting for someone.

Name the stages after the state of the work, delete the columns nothing ever waits in, and split the ones that are hiding a queue.

Then cap something. The WIP limit is the only part of kanban that forces a decision rather than describing one, and a board without one is an inventory of everything the team has started.

Set a single limit on the column that piles up most, keep it low enough to bite, and let the board tell you where to send help. Once the cards need owners, dates and sub-steps, that board belongs in task management software that treats it as one view of your real tasks.

Ready to see where your work actually piles up? Start free at quire.io/signup, build a board from your real stages, and cap the busiest column for one week.

Frequently Asked Questions

What should the columns on a kanban board be?

The real handoffs in your process, not a generic three-stage lifecycle. Each column should be a place work can wait. If nothing ever waits at a column it is not a stage, and if work waits somewhere you have no column for, your slowest step is invisible.

What is a WIP limit and do I really need one?

A cap on how many cards a column may hold. It is the part of kanban that changes behavior: when a column is full you cannot start something new, so the team has to finish what is already there. Without it, a board is a list arranged sideways.

How many columns should a kanban board have?

Enough to show every place work waits, few enough to fit on one screen, which usually lands between four and seven. Past that people read only their own column, which removes the shared picture that made the board worth having.

When should you use swimlanes?

When a second dimension changes how you would act, like separating expedited work from normal work. They cost reading effort every time, so they must earn it. Splitting by person usually turns a shared board into several private lists.

Do you need task management software to run a kanban board?

Not to start. A wall teaches the method faster. You need task management software once cards must carry owners, due dates, sub-steps and a history. In Quire the board is a view of your existing tasks, so a card keeps all four wherever you open it.

When is a kanban board the wrong tool?

When sequence is the risk. If three tasks wait on one thing finishing, the board shows three cards looking equally ready and hides the dependency. That is timeline work. Boards suit work that flows through stages, not fixed sequences.

Do kanban boards for project management actually make people more productive at work?

They do when the board caps work in progress, and very little when it does not. Teams get more productive at work by finishing rather than starting, and a capped column forces that choice. In Quire the board is one view of your existing tasks, so cards keep their subtasks, owners and dates.