A kanban board for a small team: how to set it up without turning it into a dumping ground

In a team of two or three, tasks live in chats and in the manager's head, and that works. With five to seven people the questions start: "Who is doing this?", "What happened to that report?" Each one costs a few minutes. A full project management system is overkill at this size. A board with columns and a few rules is enough.
Kanban in plain words
Kanban is a board where every task is a card and every column is a stage. A card moves from left to right, from "Inbox" to "Done". Unlike a to-do list, the board shows not only what has to be done but also where each task stands and who is working on it.
The method rests on three ideas:
- Work is visible: anyone can see in a second what is in progress, what waits for review and what is done.
- Little is left unfinished: you don't start the next task until you finish the current one.
- Work flows: if cards pile up in one column, you can see the bottleneck and deal with it instead of adding people and pushing deadlines.
The clips in this article use test data. The iTasker interface is real, and the Telegram chat is recreated from the bot’s real replies.
Which columns to choose
Four or five columns are enough for a team of 3–10 people. Every extra column is one more place where a task can get lost and one more drag.
| Column | What's in it | A card lands here when |
|---|---|---|
| Inbox | Tasks nobody has started | a new task or idea comes up |
| In progress | What the assignee is working on now | the assignee starts |
| In review | The result is ready and waits for approval | the assignee finishes and waits for the manager or a colleague |
| On pause | Paused tasks | you need someone's reply, data or a decision |
| Done | Accepted tasks | the result is checked and accepted |
The "On pause" column keeps blockers from hiding in "In progress". If a card sits there for a week, that's a reason to talk: what exactly are we waiting for, and from whom?
For the first weeks, three columns are enough: "Inbox", "In progress", "Done". Add "In review" and "On pause" when you see tasks getting stuck waiting.
The work-in-progress limit
Without a limit, kanban is a list laid out in columns. The limit caps the number of cards the team works on at the same time.
When someone has five tasks "in progress", they keep switching between them and none gets finished. It feels busy, but nothing ships.
For a small team, "no more than two tasks in progress per person" works well. A new task is taken only when one of the current ones is finished. If a task is stuck waiting for someone else, it moves to "On pause" and the next one takes its place.
The same applies to "In review". If cards pile up there, nobody has time to review them, and it's too early to take on new work until the queue is cleared.
How to keep the board current every day
- Every task is a card. An agreement that lives in direct messages and isn't on the board doesn't exist.
- A card has one assignee and a due date. With two assignees, nobody actually owns it. We cover how to write a task so it doesn't need follow-up questions in "How to assign a task to an employee".
- Whoever works on the task moves the card. If the manager rearranges everything, the board becomes their personal tool instead of a shared picture of the work.
- A five-minute check-in every day. Walk the board from right to left, from "Done" to "Inbox", and start with what's closest to completion: what is stopping it from being finished?
- Once a week, clean up. Archive finished cards, review "Inbox" and throw out whatever no longer makes sense.
Example: a board on a Tuesday
Say the team has five people: a manager, two marketers, a designer and a developer.
| Inbox | In progress | In review | On pause | Done |
|---|---|---|---|---|
| Update the deck for partners | September ad report (Anna) | Newsletter banner (Igor) | Contractor agreement (waiting for the lawyer) | Promo landing page |
| Blog topics for October | Email customers about the changes (Max) | Quarterly budget spreadsheet | ||
| Check the site analytics | Fix the signup form (Oleg) |
What stands out at a glance: nobody has more than one task in progress, the review queue isn't growing, and the contractor agreement isn't lost. It sits on pause, and the reason is written on the card itself.
Where a board stops working
People usually stop trusting a board for one of two reasons. The first: work happens in chats while the board is updated once a week at a status meeting. Then it lags behind reality, and there is no point opening it. Move a card at the moment its state changes: started, finished, stuck.
The second: every card is marked urgent. A priority that everyone has means nothing. Decide what goes first and order the cards in each column from top to bottom by importance.
When kanban doesn't fit
Kanban works well where tasks come in continuously and at different times: support, marketing, small-scale development, client work. It fits worse in two cases.
If a project has fixed stages where the second task can't start until the first is done and deadlines shift in a chain, you need a schedule such as a Gantt chart. For small projects, a board plus due dates on the cards is often enough.
If the team works in sprints planned two weeks ahead, Scrum is a closer fit, although the board and limits work inside it too.
How to set up a board in iTasker
In the web version of iTasker, every project has a "Board" view with five columns: "Inbox", "In progress", "In review", "On pause" and "Done". The columns map to task statuses and can't be customized, so starting with three columns is a matter of agreement: until you need "In review" and "On pause", simply don't use them.
You can drag a card to another column or change the status inside the task itself. A card has an assignee, a due date, a description and a checklist of subtasks. In a group project the board is shared: when one member changes a status, the others see it, and the assignee filter shows who has what and where the overload is.
iTasker doesn't count the work-in-progress limit for you. That limit is a team agreement: before taking a new task, look at how many cards you already have in "In progress".
If your team talks in Telegram, you don't need to retype a task. Reply to a message in the linked group with /new and the card appears in "Inbox".





