Skip to main content

How to Set Up a Kanban Board That Your Team Will Actually Use

Share

Most Kanban boards die quietly. Week one, everybody drags cards around. By week four, half the cards sit in "In Progress" with no owner, "Done" holds a hundred items nobody looks at, and the real status lives in a chat thread again.

The board didn't fail because Kanban doesn't work. It failed because it was set up as a to-do list with columns. A Kanban board is a picture of how work flows through your team. Get that picture right and the board maintains itself. Get it wrong and no amount of discipline will save it.

Here is how to set one up properly, in about an hour.

Start From How Work Actually Moves

Before you create a single column, write down the last three pieces of work your team finished and the steps each one went through. Not the steps it should have gone through. The real ones.

You will usually find four to six stages. A small marketing team might see: idea, drafting, review, scheduled, published. A software team: ready, building, code review, testing, released. A construction office: quoted, approved, ordered, on site, signed off.

Those stages are your columns. If you start with the textbook "To Do / Doing / Done", you will end up with a "Doing" column that hides three different kinds of waiting, and waiting is exactly what Kanban exists to expose.

Two rules keep the column list honest:

  • Every column must mean a different person or activity is involved. If two columns are always handled by the same person in one sitting, merge them.
  • Make waiting visible. "On Hold" or "Waiting for client" is not an admission of failure. It is the most useful column on the board, because it shows you where work gets stuck.

Limit Work in Progress

This is the part teams skip, and it is the part that makes Kanban work.

A WIP limit is a cap on how many cards can sit in a column at once. When "In Review" is full, nobody starts new work; they help clear the review queue instead. It feels slow for about a week. Then cycle times drop, because half-finished work stops piling up and context switching falls off a cliff.

A reasonable starting point: the number of people working in that stage, plus one. A team of three developers might set "Building" to 4. Adjust after two weeks of watching the board.

If your tool doesn't enforce limits, write them into the column name, like "In Progress (4)", and treat the number as a team agreement. The visible number does most of the work; nobody wants to be the person who drags in card number five.

Keep Cards Small and Specific

A card should describe one piece of work that one person can finish in a few days. "Website" is not a card. "Write homepage hero copy" is.

Good cards answer three questions at a glance:

  • Who owns it? One name. Shared ownership on a card means nobody owns it.
  • When does it matter? A due date or a date range, if timing is real.
  • What does done mean? A short checklist is the simplest way to say it. "Draft, legal check, upload" turns a vague card into something nobody can argue is finished when it isn't.

If a card keeps sitting in the same column for more than a week, it is probably two or three cards pretending to be one. Split it.

Use Swimlanes for the Big Groupings

Swimlanes are horizontal rows across the board. They let one board hold several streams of work without turning into a wall of cards.

The most common groupings are by project phase, by client, or by type of work. Pick the grouping your team asks about most often in stand-ups. If people keep saying "where are we on the launch tasks?", group by phase so the launch row answers the question on its own.

Don't stack more than one grouping. A board split by client and phase and priority is a spreadsheet with extra steps.

Give the Board a Rhythm

A board nobody looks at goes stale in days. Two short rituals keep it alive:

  • A daily scan (5–10 minutes). Read the board right to left, starting with the column closest to done. Ask what is blocking each card, not what everyone did yesterday. Finishing beats starting.
  • A weekly cleanup (15 minutes). Archive or collapse done cards, split anything that has sat still for a week, and check whether your WIP limits still fit.

Reading right to left is the small trick that changes the conversation. It pulls attention to the work nearest the finish line instead of the shiny new card someone wants to start.

Common Mistakes

  • Too many columns. More than seven or eight and people stop knowing where a card belongs. Merge stages that are always done together.
  • Using the board as a parking lot. Ideas and someday items belong in a backlog, not in your first column. Keep the first column for work you have committed to.
  • Moving cards without updating them. If a card moves to "Done" but the dates and progress still say 20%, people stop trusting the board. Pick a tool that updates progress when cards move, or make it a team habit.
  • Kanban instead of a plan. A board shows flow. It does not show that the permit has to arrive before the foundation can start. When work has hard dependencies and a deadline, you need a timeline too. We wrote about when to use each in Gantt Chart vs Kanban Board.

Setting It Up in LoopGantt

LoopGantt's Kanban board shows the same tasks as your Gantt chart, calendar and table, so nothing has to be copied between tools. A card moved on the board is the same task that moves on the timeline.

  • Columns that fit your process. Every project starts with Not Started, In Progress, On Hold and Completed. You can rename, recolour, reorder, add and delete columns, from 2 up to 8. Deleting a column moves its cards to the neighbouring column instead of losing them.
  • Progress that keeps up. Each column can set progress automatically when a card lands in it, so "Done" means 100% everywhere, including the Gantt chart and exports. Moves can be undone.
  • Phase swimlanes. Turn on Phases to group cards by project phase, or switch it off for one flat board.
  • Cards that carry the plan. Cards can show dates, duration, a progress bar, checklist count, and tags for critical-path tasks, high priority and dependencies, so you can see which card actually threatens the deadline.
  • Focus from the card. Start a 25-minute focus session straight from a card; the time is logged on the task when the session ends.
  • On your phone. On small screens the board shows one column at a time, and you swipe between them.

The Kanban board is included on the free plan. If you want to try the setup above, create a project and open the Kanban tab. Or let the AI planner build the first version of your project, then reshape the columns to match how your team works.

The Short Version

Build columns from the way work really moves, cap work in progress, keep cards small with one owner, group with one kind of swimlane, and look at the board every day, right to left. That is the whole method. The board stays useful as long as it tells the truth, and these habits are what keep it truthful.

Ready to plan your project?

Create AI-powered Gantt charts, Kanban boards, and WBS diagrams — free.

Get Started Free
Loading comments…