On this page
Definition
Kanban is a visual workflow management method that represents tasks as cards moving through columns on a board, with limits placed on work-in-progress to expose bottlenecks and keep flow steady.
Simple explanation
Picture a whiteboard split into three columns: To Do, Doing and Done. Each task gets a sticky note. As work progresses, you move the note across. That is the entire idea behind Kanban — nothing more complex is required to get started.
The method originated in Toyota's manufacturing lines in the 1940s, where physical cards signalled when a station needed more parts. Software teams adopted the same logic decades later: a card signals the state of a task, and the board makes the whole team's workload visible at a glance.
Why it matters
Most work stalls invisibly — a task sits waiting for review, or one person is quietly overloaded, and nobody notices until a deadline slips. A Kanban board surfaces this instantly: if a column is overflowing, that is where the bottleneck is.
Because it imposes limits on how much can be 'in progress' at once, Kanban discourages the common habit of starting many things and finishing few. Teams that adopt it typically see fewer half-done tasks and clearer accountability for what is actually moving.
How it works
- 1Visualise the workflowMap your process into columns representing each stage a task passes through.
- 2Add cardsEvery task, ticket or request becomes a card placed in the relevant column.
- 3Limit work in progressCap how many cards can sit in each 'active' column at once.
- 4Pull, don't pushTeam members pull the next card only when they have capacity, rather than being assigned a queue.
- 5Review and adjustRegularly inspect where cards pile up and adjust limits or process to fix it.
Real examples
Products named for illustration only. Inclusion is not an endorsement.
- TrelloSimple drag-and-drop Kanban boards for individuals and small teams.
- JiraKanban boards built into software development workflows.
- AsanaBoard view alongside list and timeline views for the same tasks.
- Physical whiteboardSticky notes on a wall — the original, still widely used format.
Advantages
- Makes bottlenecks and overload visible at a glance.
- Low barrier to entry — no special training required.
- Flexible enough for software teams, marketing, hiring or personal tasks.
- Encourages finishing work over starting new work.
Limitations
- Offers little structure for time-based planning or deadlines.
- Can become cluttered without discipline about archiving finished cards.
- Work-in-progress limits are easy to ignore if not enforced.
- Doesn't inherently prioritise tasks — that requires an additional convention.
Common misunderstandings
- ClaimKanban and Scrum are the same thing.RealityScrum works in fixed time-boxed sprints with defined roles; Kanban is a continuous flow with no mandatory sprints or roles.
- ClaimA Kanban board alone makes a team more productive.RealityThe board only reveals problems — someone still has to act on the bottlenecks it exposes.
Frequently asked questions
Is Kanban only for software teams?
No. It originated in manufacturing and now suits any workflow with distinct stages, including marketing, HR and personal task management.
What does 'work in progress limit' mean?
It's a cap on how many tasks can be actively worked on in a column at once, forcing focus and exposing overload.
Do I need software to use Kanban?
No — a whiteboard and sticky notes work fine. Software adds automation, reporting and remote collaboration.
How is Kanban different from a to-do list?
A to-do list only shows what's left; a Kanban board shows what stage every task is at and where the process is stuck.
Can Kanban work for one person?
Yes — many people use a personal three-column board to manage their own workload.
The Tool Money Lab perspective
Kanban's appeal is that it costs almost nothing to try and tells you something true about your process within days: where work actually gets stuck. That diagnostic value is often more useful than the board itself.
We see the most value when teams actually enforce work-in-progress limits rather than treating the board as a static status report. Without that discipline, a Kanban board is just a prettier to-do list.
Conclusion
Kanban turns an invisible flow of work into something you can see and manage: cards moving across columns, with limits that force attention onto bottlenecks rather than new starts.
It works well precisely because it is simple — any team can adopt the core idea in an afternoon, then refine the columns and limits as they learn where their real constraints lie.