How to Set Up a Kanban Board
A step-by-step guide to setting up a Kanban board that your team actually uses: defining workflow stages, setting WIP limits, adding current work, establishing a pull system, and tracking your first flow metric.
Key Insight
Start with four columns and WIP limits on In Progress. A Kanban board with four columns that the team uses every day outperforms an elaborate nine-column board that no one updates. Add complexity only when the simpler version reveals a bottleneck that a new stage would resolve.
Before building the board, confirm that the team agrees on what Done means for the types of work you are tracking. A Kanban board without a shared Definition of Done produces Done columns full of tasks that still need client approval, QA, or deployment. Define it once as a team rule before the first card moves, and write it somewhere visible: in the column header description, in a team channel, or in the board’s shared documentation.
How to Set Up a Kanban Board in 8 Steps
1
Define Your Actual Workflow Stages
Before opening any tool, write down every distinct stage that work passes through in your team from the moment it is requested to the moment it is delivered. Common stages: Request received, Ready to start, In progress, Under review, Done. Add only stages that represent a genuine handoff or waiting state. If work flows directly from one step to the next without waiting, those two steps belong in the same column.
Avoid creating columns for stages that rarely occur. A Legal Review column that holds two cards per year adds noise rather than signal. If that stage is relevant, add it when you actually have work in it. Start lean.
2
Create Board Columns for Each Stage
Build the board in your chosen tool with one column per workflow stage. Order them left to right in the direction work flows. The leftmost column is your input queue (Backlog or Inbox). The rightmost is Done. Everything in between represents active work.
In ClickUp, create a Board view and add custom statuses matching your stages. Each status maps to a column. Name them to match the language your team actually uses: if your team says 'Under Review' rather than 'Review,' use that term. Boards fail when the labels do not match how people talk about the work.
3
Set WIP Limits on Active Stages
Set a numeric cap on how many tasks can be in each active column simultaneously. A WIP limit of three on In Progress means no new work starts until a current task moves to the next column. Start with a limit of one to two items per team member for In Progress. For Review, start at half the In Progress limit.
Do not skip this step. A Kanban board without WIP limits is a task list with columns. WIP limits are what make bottlenecks visible: if Review is always at its limit while In Progress stays empty, the bottleneck is in review, not in execution. That insight is only visible when limits are in place.
In ClickUp, set WIP limits per column in Board view settings. Choose between a warning (shows a badge) or a hard block (prevents cards from entering the column) depending on your team's maturity with the process.
4
Transfer All In-Flight Work to the Board
The most important rule of Kanban setup: make all work visible. Do not only add new work. Add every task currently in progress, waiting for review, waiting for a client response, or blocked. Tasks that exist only in someone's head or email inbox are invisible to the rest of the team and cannot be managed.
For each task you add, place it in the column that reflects its current actual stage, not the stage where you wish it were. A task under client review goes in Review, not Done. A task waiting on a dependency goes in Blocked or In Progress with a flag. The initial board state should be an honest picture of where work stands today.
5
Define Your Pull Trigger
Kanban is a pull system: downstream stages pull work from upstream stages rather than upstream stages pushing work forward. For this to work in practice, the team needs an explicit rule about what makes work ready to move from one stage to the next.
Write one sentence for each stage transition: what does In Progress → Review require? What does Review → Done require? These are your entry criteria per column. They do not need to be elaborate: 'A task moves to Review when the assignee has completed the work and written a one-line test summary' is sufficient. Without explicit pull criteria, tasks drift forward based on optimism rather than evidence.
6
Add Swim Lanes If Managing Multiple Work Types
If your team handles fundamentally different types of work (features, bugs, support tickets, operational tasks), add swim lanes to separate them visually within the same board. Each swim lane represents a category that has its own priority, flow, and WIP budget.
Do not add swim lanes by default. Add them when the board becomes hard to read because different work types are competing for the same WIP limit attention. A board with four lanes for a five-person team often creates more overhead than it removes. In ClickUp, enable swim lanes from the Board view settings using any custom field as the grouping dimension.
7
Schedule a Weekly Board Review
Kanban has no sprint ceremonies, but it benefits from a weekly rhythm. Schedule a 30-minute weekly board review at the same time each week. The agenda: walk the board from right to left (Done to Backlog), identify tasks that have been in the same column for longer than your expected cycle time, review any blocked tasks and confirm the person responsible for unblocking them, and replenish the Backlog or Ready column with the next highest-priority items.
This meeting replaces the sprint review and retrospective in a single lighter-weight session. It keeps the board current and the team aligned without the ceremony overhead of Scrum events.
8
Track One Metric from Day One
Start measuring cycle time immediately: the number of calendar days from when a task moves to In Progress to when it moves to Done. Record it in a simple log or a custom field. After four weeks, calculate the average and the variance. High variance (some tasks take three days, others take three weeks) points to systemic inconsistency that the board will help you investigate.
In ClickUp, use the Cycle Time custom field included in the Kanban board template or create your own using the Date Started and Date Completed fields with a formula. Review the data at your weekly board meeting and use it to calibrate your WIP limits after the first month.
Common Questions About How to Set Up a Kanban Board
How many columns should a Kanban board have?
Four to six columns covers most teams well: Backlog, Ready, In Progress, Review, and Done. Add a Blocked column if blocked tasks are common and need to be visually distinct. Add additional columns for stages that represent genuine handoffs where work waits for an external party. Avoid adding columns for stages that are part of a single person's work without a true handoff. More columns create more overhead without proportional insight.
What is a good starting WIP limit for In Progress?
A reasonable starting point is one task per person on the team plus one buffer. For a five-person team, start with a WIP limit of six on In Progress. If work flows smoothly at that limit, tighten it by one each week until you find the point where the limit creates productive pressure to finish before starting. If the team constantly bumps against the limit immediately, the tasks are too large and need to be broken down further.
How is Kanban setup different from setting up a Scrum board?
A Scrum board is set up for a specific sprint: you plan which tasks go in, run the sprint, and reset at the end. A Kanban board is persistent: work flows in continuously and exits continuously without a reset boundary. Kanban setup focuses on defining stages and WIP limits that work for an ongoing flow. Scrum setup focuses on sprint planning mechanics, velocity tracking, and ceremony facilitation. The board views look similar, but the management logic behind them is different.