Start with an outcome, not a pile of tasks
A project is a temporary effort that should produce a specific result. Write that result in language the whole team can test. Then add only the work needed for the next milestone. A board full of speculative tasks hides progress instead of clarifying it.
Use each column as a real agreement
Backlog means approved but not ready. To-do means ready to begin. Doing means active work. Review means the output is waiting for a defined quality check. Done means accepted, not merely submitted. When everyone uses the columns consistently, the board can replace a surprising amount of status reporting.
- Keep each card small enough to move in a few days, not a few months.
- Assign one accountable owner, even when several people contribute.
- Put acceptance details in the card so review is objective.
- Limit the number of cards in doing to expose blocked work quickly.
Document decisions where the team can recover them
Projects generate context that does not belong on a card: meeting decisions, procedures, client constraints and links to source documents. Keep that material in the team wiki, link it from the project and update it when a decision changes. The goal is an operational memory that survives beyond the current conversation.
A practical starting point
Put it into practice
- 1
Define done
Write one measurable project outcome and the evidence that will prove it is complete.
- 2
Create the next milestone
Break the outcome into small cards for the next meaningful stage, not the entire imagined future.
- 3
Assign and limit active work
Give each card one owner and keep only a few items in doing at once.
- 4
Review, accept and document
Check work against clear criteria, move accepted items to done and record durable decisions in the wiki.
Common questions
Clear answers
What columns should a small team kanban board use?
A practical starting workflow is backlog, to-do, doing, review and done. Add another stage only when it represents a real handoff or decision the team needs to see.
How many tasks should be in progress at once?
Keep the number low enough that blocked work is obvious and teammates can help finish before starting more. A useful starting limit is roughly one active item per person, adjusted for the work.
Should a kanban card have more than one owner?
Several people can contribute, but one person should remain accountable for moving the card forward and closing the loop.
Where should project decisions be documented?
Keep durable decisions, procedures and project context in a shared team wiki, then link that context from the relevant project or task.