The story of Kanban begins in an unexpected place: a Japanese supermarket in the 1940s. Toyota engineers noticed how stores would only restock items once they were nearly sold out. This "just-in-time" approach prevented them from wasting money and space on inventory they didn't need yet. They applied this idea to their car manufacturing process, creating a system to signal when new parts were needed.

The Japanese word for these signals is kanban (看板).

Decades later, software developers adapted this manufacturing concept for managing their own work. Instead of physical parts, their inventory was tasks. The core idea remained the same: make the workflow visible and only pull in new work when there's capacity to handle it.

Kanban is guided by a few simple but powerful principles. Understanding them is key to understanding why it's so effective.

First, visualize the workflow. This is the most recognizable part of Kanban. Teams create a board with columns that represent the stages of their work. A simple board might have columns like "To Do," "In Progress," and "Done." Each task is a card that moves from left to right across the board.

This visual map makes it instantly clear where every piece of work is. Nothing gets lost, and everyone can see bottlenecks at a glance. Is the "In Progress" column overflowing with cards? That's a sign the team is overloaded.

Second, limit Work in Progress (WIP). This is the crucial step. Each column representing an active stage of work (like "In Progress") gets a limit on how many cards it can hold at one time. For example, a team might set a WIP limit of three for their "In Progress" column.

Once there are three tasks in that column, no one can pull a new task from "To Do." Team members must first collaborate to finish one of the current tasks and move it to "Done." This forces the team to focus on finishing work, not just starting it. Limiting WIP reduces multitasking, improves quality, and gets individual tasks done faster.

Finally, manage the flow. By visualizing the work and limiting WIP, the team can now focus on making the flow of work smooth and predictable. They watch the board for cards that get stuck or for columns that are consistently empty or overloaded. The goal is to identify and resolve these blockages to create a steady, efficient process.

This is different from a system like Scrum, which uses fixed-length sprints (like two-week cycles) to get work done. Kanban is a continuous flow system. There are no prescribed sprints. Instead, the focus is on pulling work through the system as capacity becomes available.

Kanban isn't about rigid rules. It's about making your process visible and then continuously improving it. It can be applied to almost any kind of workflow, from software development to marketing campaigns to personal to-do lists.

Ready to check your understanding?

By visualizing work and focusing on flow, teams can stop starting and start finishing.