TaskMgmtSoftware.net Find my tool →

Glossary

Kanban

A pull-system workflow method visualised as columns of cards — originated at Toyota in the 1940s

Kanban is a workflow management system where work is visualised as cards on a board of columns — typically “To Do,” “In Progress,” and “Done” — and pulled from one column to the next as capacity allows. It originated in Toyota’s manufacturing plants in the 1940s as a way to control production without overproduction.

The word “kanban” (看板) means “signboard” or “visual signal” in Japanese. The original system used physical cards to signal when a production stage needed more work. Software adapted this into the card-and-column boards that tools like Trello, monday.com, and ClickUp use today.

How it works in practice

A 6-person development team might run kanban with four columns: Backlog, In Progress, Code Review, and Done. Each developer pulls cards from Backlog into In Progress only when they have capacity — not when tasks are pushed by a manager. The pull-system is the fundamental difference from traditional assignment-based scheduling.

The most important control mechanism that most teams skip: WIP limits (work-in-progress limits). A WIP limit on “In Progress” of 2 per developer means no developer can have more than 2 active tasks at once. This forces serial focus over parallel thrashing and surfaces bottlenecks (a column fills up, work stops, the constraint is visible).

Most “task management” apps default to kanban boards — but most teams use them without WIP limits, which is like driving with no speed limit signs and being surprised when productivity crashes. The pull-system only works if limits are enforced.

Why kanban (not scrum)

Kanban is a better fit for teams with:

  • Continuous flow work (support, ops, content) rather than fixed-duration sprints
  • Variable team capacity (contractors, shared resources)
  • Projects without clear sprint boundaries
  • Teams just starting with structured workflow — lower ceremony than scrum

Scrum is a better fit for teams running 2-week sprints with sprint planning, standups, reviews, and retrospectives. Most small B2B ops teams are better served by kanban’s simpler model.

Why it matters for choosing a task management tool

Your choice of tool affects how well kanban works:

  • Trello: Purpose-built for kanban. The card-and-column model is the product, not a view option. WIP limits require a Power-Up (Limited WIP).
  • ClickUp: Multi-view — kanban is one of 15 views. Switching back to list view mid-project is common and can undermine the kanban discipline.
  • monday.com: Visual-first, similar to kanban but with more column types (status, dates, people, numbers). The board metaphor is well-executed.
  • Asana: Board view is solid but Asana is list-first. The kanban discipline is harder to maintain when the UI encourages switching to list view.

For teams committed to kanban as their primary workflow, Trello Standard ($6/seat) is the most disciplined implementation. For teams that want kanban as one view among many, ClickUp or monday are better fits.

Go deeper