What is kanban?
Kanban is a workflow management method that visualizes work, limits work in progress, and optimizes the continuous flow of tasks through defined stages. Originating from Toyota's manufacturing system in the late 1940s, kanban (Japanese for "visual signal") used physical cards to track parts through an assembly line. Software teams adopted the model in the early 2000s because it maps naturally to how code moves through a development pipeline.
Unlike time-boxed frameworks such as scrum, kanban is continuous. There are no sprints, no planning ceremonies dictating what enters the pipeline, and no hard resets at the end of a cycle. Work flows through columns on a board at whatever pace the team can sustain. The system's power lies in making that flow visible and constraining it with work-in-progress limits so bottlenecks surface immediately.
Why kanban matters
Kanban solves the most common failure mode in knowledge work: starting more than you can finish. When teams pile up half-done tasks, context switching multiplies, cycle times balloon, and delivery becomes unpredictable. Kanban addresses this structurally, not culturally. By capping the number of items allowed in each stage, the method forces teams to finish work before starting new work. The result is shorter cycle times, fewer handoff delays, and a clearer picture of where work is actually stuck.
Kanban also requires very little process overhead to adopt. There are no prescribed roles, no mandatory meetings, and no estimation rituals. A team can start with their existing workflow, map it to columns on a board, and begin improving from there. This makes kanban the lowest-friction entry point for teams that want structure without bureaucracy.
Core principles
Kanban rests on a few foundational ideas. First, visualize the workflow: every piece of work should be represented as a card on a board, and every stage of the process should be represented as a column. Second, limit work in progress: set explicit caps on how many items can occupy each column at once. Third, manage flow: monitor how quickly cards move through the system and adjust processes to remove blockages. Fourth, make policies explicit: the rules for when a card can move between columns should be visible and agreed upon, not assumed.
How Flux implements kanban
Flux is built around kanban as its core workflow model. Every board is a kanban board with customizable columns, drag-and-drop card movement, and real-time sync powered by server-sent events. When one team member moves a card, every other viewer sees the change within seconds. The activity log records every state transition with before-and-after snapshots, giving teams a full audit trail of how work flowed. Labels, checklists, assignees, and due dates add structure to each card without adding process weight. For teams managing multiple projects, the multi-board view surfaces cards across all boards in a single screen.
Related terms
See also: Kanban Board, WIP Limit, Cycle Time.