What Is a Kanban Chart? A Plain-English Guide

A kanban chart is a picture of work in progress: vertical columns for the stages work passes through, and cards for the individual tasks, moving left to right as they get done. Most people who use one daily call it a kanban board — "chart" and "board" mean the same thing here, and if you've seen Trello, a whiteboard covered in sticky notes, or the board view in almost any modern tool, you've seen one.

That's the short answer. The longer answer is worth five minutes, because the kanban chart is deceptively simple: three columns and some cards, hiding a couple of genuinely good ideas — and a couple of hard limits that catch teams by surprise.

The anatomy of a kanban chart

Every kanban chart is built from the same four parts:

Columns represent the stages of your workflow. The classic minimum is To Do → In Progress → Done, but real boards map real processes: a support team might run Inbox → Investigating → Waiting on Customer → Resolved; a hiring pipeline might run Applied → Screen → Interview → Offer. The columns are your process, made visible.

Cards are the units of work — one task, ticket, or job per card. A card carries just enough to act on: a title, an owner, maybe a due date. The card's position is its status; nobody has to ask.

Work-in-progress (WIP) limits are the idea that makes Kanban more than sticky notes. Each column gets a maximum — say, no more than three cards in In Progress. When the column is full, nobody starts new work; they help finish what's already moving. This is the mechanism that turns "everything is 80% done" into "things actually finish."

Swimlanes (optional) are horizontal rows that split the board — by person, by client, by job. Useful once one board serves several streams of work.

How work moves: the pull system

On a kanban chart, work is pulled, not pushed. Nobody assigns tasks downstream; when someone finishes a card, they pull the next one from the column to the left. Combined with WIP limits, this does something subtle: bottlenecks become visible as pile-ups. If cards stack up in Waiting for Review, you don't need a status meeting to find the constraint — it's the tallest column.

The name comes from Toyota's factories: kanban is Japanese for "signboard" or "signal card." A physical card moving upstream told the previous station to produce more — the original pull signal. The software world borrowed the card and the pull idea in the 2000s, and the kanban chart is its visible form.

"Kanban chart," "kanban board," "Kanban method" — which is which

Three terms get tangled together:

• Kanban chart / kanban board — the artifact: columns and cards. Same thing, two names.
• The Kanban method — the management approach built around the board: visualize the work, limit WIP, measure flow, improve continuously. You can use a board without the method (most teams do), and it still helps.
• Kanban's measurement charts — the method also produces real charts in the graph sense. The cumulative flow diagram stacks the count of cards in each column over time, showing where work accumulates. Lead time and cycle time charts show how long cards take from entry to done. If you searched "kanban chart" expecting a graph with axes, these are the ones — but in everyday speech, "kanban chart" almost always means the board.

What a kanban chart shows brilliantly — and what it can't show

The board answers one question better than any other tool: "what is happening right now, and where is it stuck?" Current state, at a glance, always up to date because moving a card is the status update.

But three things are structurally missing, and no amount of configuration adds them:

Time. A kanban chart has no time axis. It cannot show when something will happen, only what stage it's in now. A card can sit in In Progress for a day or a month and look identical.

Deadlines. Because there's no timeline, there's no way to see whether you're on track for a date — the board doesn't know the date exists.

Dependencies. Cards look independent, but real tasks often aren't — one can't start until another finishes. A kanban chart has no way to draw that. If your work has real sequencing in it, that's dependency territory, and it's the main reason teams pair the board with a timeline.

When a kanban chart is the right tool

• Continuous, arriving work — support queues, maintenance, content pipelines, sales follow-ups. Work flows in forever; there's no "project end" to plan toward.
• Small teams that need shared state, not a plan — the board replaces the "what are you on?" conversation.
• Work with little hard sequencing — when tasks are mostly independent, nothing is lost by not drawing dependencies.
• As the execution layer under a plan — many teams run the day-to-day on a board while the commitments live on a timeline. That layering — and where Scrum's sprints fit into it — is covered in Gantt chart vs Scrum.

When the work is a finite project with a promised end date and a real sequence — a renovation, a launch, a client deliverable — the board alone starts to strain, for the reasons above.

Setting one up in ten minutes

1. Draw your real stages as columns. Not the ideal process — the actual one, including the embarrassing Waiting column. Start with four or five.
2. Write one card per piece of work. If a card would sit in In Progress for weeks, split it.
3. Set a WIP limit on In Progress. A good starting rule: number of people, plus one. Tighten later.
4. Work right to left. Finish and pull before starting new. When a column jams, fix the jam instead of stacking more cards behind it.
5. Prune weekly. A board where cards go to age quietly stops being trusted, and an untrusted board is decoration.

Conclusion

A kanban chart is the simplest useful picture of work there is: columns for stages, cards for tasks, a limit on how much runs at once. It shows the present tense of your work perfectly, and it shows the future not at all. Use it where flow matters and dates don't — and pair it with a timeline the moment someone asks when.