How to Use Kanban: A Step-by-Step Guide

By Theta PM Systems · Updated November 2026

Kanban looks like the easiest method in project management: three columns, some cards, move them right. That is also why most kanban boards stop working after a month — the columns are decoration, nobody enforces a limit, and the board becomes a picture of the backlog rather than a picture of the work.

Used properly, kanban is a flow system. It limits how much work is in progress, makes blockers visible, and produces two numbers that tell you whether you are getting faster. This guide walks through setting it up from scratch.

Step 1: Map the Workflow You Actually Have

Do not start from a tutorial's columns. Start from what literally happens to a piece of work between the moment someone asks for it and the moment it ships.

Ask the team to describe one recent finished item out loud. Write down each handoff as a stage: requested, specified, designed, built, reviewed, tested, deployed. Then delete the stages nobody ever waits in. A board with four honest columns beats a board with nine aspirational ones.

  • "To Do", "In Progress", and "Done" is a valid starting point — it is not a compromise.
  • Add a column only for a stage where work genuinely waits or changes hands.
  • Name columns after states of the work, not after people or teams.
  • Keep "Done" to a bounded recent window; archive older completed work so the column does not grow forever.

Step 2: Write Cards That Can Move

A card is a unit of work that one person can finish without coordinating a meeting. "Improve onboarding" will sit in the same column for six weeks. "Rewrite the sign-up confirmation email" will move.

A useful card carries four things: a concrete outcome, an owner, a done definition, and a date if a date genuinely exists. Everything else — the discussion, the linked pull request, the design file — attaches to the card instead of living in a chat thread.

  • Title the outcome, not the activity: "Ship CSV export" beats "Work on export".
  • One owner per card. Shared ownership means nobody is accountable.
  • Attach the artefact — pull request, design link, spec — to the card so the next person does not have to ask.
  • Split anything that has not moved in two weeks; it is either blocked or too big.

Step 3: Set WIP Limits

This is the step teams skip, and it is the step that makes kanban work. A work-in-progress limit caps how many cards may sit in a column at once. When the column is full, the team finishes something before starting something.

Start one card below your current average per person per column. If three developers routinely have four things in progress, set the limit to three. You are not banning multitasking; you are making its cost visible.

  • Set limits per column, not per person — the constraint is the team's flow, not an individual's.
  • A full column is a signal to help finish, not a reason to widen the limit.
  • Review limits monthly; they should rise only when the team is genuinely faster.
  • WIP limits plus a visible blocker column are what separate kanban from a to-do list.

Step 4: Define What Done Means in Each Column

Every column needs an exit rule both the author and reviewer agree on. Without one, "In Review" becomes the place work goes to be forgotten.

ColumnEntry ruleExit rule
To DoSomeone has described the outcome and it is prioritizedAn owner has started work on it
In ProgressAn owner is actively working on itThe artefact exists and is ready for a second pair of eyes
In ReviewA reviewer is assignedApproved, or sent back with written feedback
BlockedSomething outside the team's control is stopping itThe blocker is removed and the card returns to its column
DoneIt meets the definition of done and is deployed or deliveredArchived after the review window

Step 5: Run the Daily Pull, Not a Status Meeting

The daily conversation on a kanban team is about flow, not about reporting to a manager. Walk the board right to left, starting at Done: what finished, what is in review, who is blocked, and what can be pulled next.

Right-to-left matters. It focuses the team on finishing rather than starting, which is the entire point of a WIP limit. Fifteen minutes, standing, at the board — and anyone not needed for a specific card is free to leave.

  • Finished since yesterday — and does it meet the column's exit rule?
  • In review — who is reviewing, and by when?
  • Blocked — what is the specific blocker and who owns removing it?
  • Pull — what is the next card, given the WIP limit?

Step 6: Measure Two Numbers

Kanban improves through measurement, and two metrics carry most of the signal.

Cycle time is how long a card takes from start to finish. Lead time is how long it takes from request to delivery. Both are medians, not averages — one six-week outlier will distort a mean and hide a real improvement.

If you chart cycle time over a few weeks you get a cumulative flow picture: where cards pile up, which column is the bottleneck, and whether a WIP limit change actually helped.

  • Track cycle time per card from first pull to Done, using real start and completion timestamps.
  • Watch the median and the 85th percentile — the tail is what breaks commitments.
  • If one column consistently holds the most cards, that is your constraint. Fix it there, not everywhere.
  • Compare before and after any process change; otherwise you are guessing.

Common Mistakes

  • Using the board as a backlog dump, so nothing ever leaves To Do and everything feels late.
  • No WIP limit, which turns kanban into a list of everything in flight at once.
  • Columns that mirror org chart roles instead of states of work, which forces handoffs that do not exist.
  • Moving a card to Done before it is actually delivered, which poisons every later metric.
  • Card titles that describe activity, so nothing can be verified as finished.
  • Rewriting the board every quarter instead of tuning one constraint at a time.

Running Kanban in Theta PM

Theta PM's kanban board is one view of the tasks in a project, so the same cards appear on the timeline, the calendar, and the Gantt view without being copied. That makes the board a flow tool rather than a separate system.

  • Drag cards between columns, or let automation move them on status change.
  • Custom fields on the card hold size, priority, or client without a separate spreadsheet.
  • Task completion timestamps feed the reports view, so cycle time is measured rather than estimated.
  • Milestones on the timeline show which cards belong to the same release.
  • GitHub and Slack integrations keep the card aligned with the pull request and the channel.

Frequently Asked Questions

How many columns should a kanban board have?+

Start with three: To Do, In Progress, and Done. Add a column only when work genuinely waits or changes hands at that stage. Most teams land between four and six; anything beyond that is usually a workflow nobody follows.

What is a WIP limit, and is it required?+

A WIP limit caps how many cards may be in a column at once. It is not optional in practice — without one, kanban degenerates into a to-do list and the board stops reflecting capacity. Start one below your current average and tune from there.

What is the difference between kanban and scrum?+

Kanban is continuous: work flows through columns with no fixed iterations, and the constraint is a WIP limit. Scrum is time-boxed: work is planned into a sprint, committed to, and reviewed at the end. Kanban suits interrupt-driven and support work; scrum suits planned product development.

How do I measure whether kanban is working?+

Track cycle time from first pull to Done and watch the median. If it falls while WIP limits hold, flow is improving. If one column consistently holds the most cards, that column is your bottleneck and the next thing to fix.

Can I use kanban for a team that also runs sprints?+

Yes. Many teams run a kanban board for continuous operational work and sprints for planned product work. Theta PM supports sprints and boards on the same tasks, so the two views stay consistent.

Keep Reading

Start free in minutes

Create a workspace, invite your team, and plan your first project today.