How to set up a Kanban board for project management

When work lives in chat threads, documents, and inboxes, no one can answer the two questions that matter most: what is being worked on right now, and who owns it? A Kanban board fixes that by giving your team one shared, visual picture of every task and its status. This guide walks through setting up a board you will actually keep using, from workflow stages to accountable cards.

What a Kanban board is (and why it works)

A Kanban board represents a stream of work as cards that move left to right through stages. The board is the project, the lists (or columns) are the stages work passes through, and each card is a single task. Because status is expressed by position, anyone can glance at the board and see what is in progress, what is waiting, and where work is piling up. That visibility is the whole point: it replaces status meetings and “where are we on this?” messages with something everyone can read at a glance.

Step 1: Define your workflow stages first

Before creating anything, map how work actually moves through your team, not an idealized process. Start with four or five stages and add detail only when a stage is hiding too much. A dependable starting point is:

To Do → In Progress → Review → Done

Adjust the names to fit how your team really operates:

• Agency: Backlog → Briefed → In Progress → Client Review → Approved
• Software team: Backlog → In Development → Code Review → QA → Released
• Startup / product team: Ideas → This Week → In Progress → Review → Done

Step 2: Create the board and its lists

Create one board per project, product, or ongoing stream, rather than one giant board for everything. Separate boards stay readable and keep each project’s progress meaningful. When you create a board in Otper, you give it a name and can customize its key and slug to short, unique values: the key prefixes every card ID on the board (for example, WEB-12) and the slug helps form board links, so choosing clear values now keeps cards and URLs easier to recognize later. Then add or rename lists so the columns mirror the process you mapped in Step 1.

Step 3: Write cards that hold accountability

A good card describes one unit of work with a clear, specific title. What turns a card from a sticky note into an accountable record is the detail you attach to it:

• Owner — assign a responsible member so there is never a “who is doing this?” moment.
• Due date — set one wherever there is a real commitment, making deadlines visible.
• Labels — tag priority, workstream, or type so the board reads at a glance.
• Checklists — break the definition of done into steps the owner can tick off.
• Attachments and links — keep the files and references on the card, not buried in DMs.
• Comments and @mentions — keep questions and decisions attached to the work itself.

In Otper, each card holds all of this: assign members, add a due date, apply labels, add a checklist, attach files, and discuss in comments. The result is a task anyone can pick up without a handover meeting.

Step 4: Set a few simple team rules

A board only stays useful if the team agrees on how to use it. Three rules cover most situations:

• Limit work in progress. Cap how many cards sit in a stage at once so work finishes instead of piling up.
• Define “Done.” Agree what has to be true for a card to move to the final list, so it means the same thing to everyone.
• Decide who moves cards and when. Owners update their own cards; the board is reviewed together in a short standup or async check-in.

Step 5: Adapt views as the project grows

The same cards can be read in different ways depending on what you need. Use the board view for daily flow, a list view for dense triage, and a Gantt view when deadlines and scheduling come into play. Otper lets you switch between Board, List, and Gantt views of the same data, so planning a schedule never means rebuilding your work somewhere else.

Common setup mistakes to avoid

• Too many lists, so the board becomes noise instead of signal.
• Cards with no owner — the fastest way to lose accountability.
• One mega-board for every project, which hides each project’s real status.
• An inconsistent “Done,” where some cards mean delivered and others mean merely started.

From board to insight

Set up your stages, create the board, make every card accountable, and agree on a few rules, and you have a workspace the whole team can follow. Once the board is running, the data it produces becomes useful on its own: which stage work gets stuck in, what is overdue, and who is overloaded. That is the subject of the next article, using Kanban analytics to find bottlenecks, overdue work, and workload issues.

FAQ

Related guides

• How to set up a Kanban board
• Working with cards
• Project management with Otper