Kanban Basics for Office Work

Office work has a visibility problem. On a factory floor, overload announces itself — pallets stack up, queues snake down the aisle, everyone can see the bottleneck. In an office, forty in-progress tasks look exactly like four: a quiet person at a screen. Work piles up invisibly in inboxes and ticket queues, priorities collide without anyone noticing, and the honest answer to “what is the team working on right now?” is a shrug. Kanban exists to fix that.

The method began at Toyota, where kanban — the Japanese word for a signal card — was the mechanism that made pull production work. A card attached to a bin of parts traveled back upstream when the bin ran empty, authorizing the previous station to make more. No card, no production. The card turned demand into a visible, physical signal, and it capped how much material could be in motion at once.

Office kanban keeps both ideas — visible signals and a cap on work in motion — and trades the cards for a board. It is the lightest process change in the Lean toolkit: no reorganization, no software mandate, no new roles. Start with what you do now, make it visible, and let the board tell you what to fix.

The board: making work visible

A kanban board is a set of columns representing the stages work passes through, with each work item written on a card that moves left to right. The simplest board — To Do, Doing, Done — works for a personal desk. A team board earns more columns by mapping the actual flow: perhaps Requested, In Analysis, Waiting on Client, In Review, Done. The columns should describe the process you have, not the process you wish you had; the board is a mirror before it is a lever.

The effect of simply seeing the work is hard to overstate. Piles that lived in individual inboxes become a shared picture. The overloaded column is obvious to everyone, including the manager who has been assigning into it. The card stuck in Waiting on Client for three weeks stops being one person’s private frustration and becomes a visible fact the team can act on.

WIP limits: the part that makes it kanban

A board alone is a status display. Kanban begins when you add work-in-progress limits — a maximum number of cards allowed in a column at once, written at the top of the column and enforced. Three in In Review means three: when a fourth is ready, it waits, and the team’s job becomes finishing something before starting something.

WIP limits feel wrong at first, and the objection is always the same: surely starting sooner means finishing sooner. It does not, and the reason is queueing, not effort. Items in progress compete for the same people, so each new start stretches every other item’s finish. Ten items in flight means constant switching, aging handoffs, and everything arriving late together; three in flight means attention, fast feedback, and a steady stream of completions. Limiting WIP converts the hidden cost of multitasking into a visible queue at the edge of the board — where it can finally be managed.

Pull, not push

With limits in place, the system starts to pull. Nobody assigns work into a full column; instead, a person who finishes an item reaches back and pulls the next highest-priority card when — and only when — capacity opens. The distinction sounds small and changes everything. Push systems overload quietly and blame individuals for the backlog. Pull systems surface overload instantly as a full column, and turn it into a process question: why is this stage the constraint, and what would relieve it?

Reading the board: flow over busyness

A kanban board rewards a different question than traditional management. Instead of asking whether everyone is busy — they always are — ask whether work is flowing. Watch where cards accumulate: a column that is always full marks the bottleneck, and improving anywhere else is cosmetic. Watch the age of cards: an item untouched for two weeks is a flag no status meeting would have raised. Some teams also track how long cards take from start to finish and how many finish per week; the vocabulary for those measures — cycle time, lead time, and their cousins — is a topic of its own, and worth learning precisely.

Starting a board this week

1. 01List the stages your work actually passes through, and draw a column for each — resist designing the ideal flow
2. 02Write every current work item on a card and place it honestly; expect the In Progress column to shock you
3. 03Set a WIP limit on the busiest column — a starting point is slightly fewer cards than people feeding it
4. 04Agree on one rule: finish before starting, and pull only when a slot opens
5. 05Stand up at the board twice a week and discuss the cards, not the people — oldest and stuck items first
6. 06After two weeks, adjust the columns and limits to match what the board has taught you

The pitfalls

• A board with no WIP limits — a status wall, not a kanban system
• Columns that mirror the org chart instead of the flow of work, so cards teleport instead of travel
• Cards written so vaguely that nobody can tell what Done would mean
• A private board per person, which hides the shared queues kanban exists to reveal
• Treating a full column as a staffing insult rather than the most useful data the team owns

A busy team tells you nothing; a visible queue tells you everything.

From a board to a method

Kanban is often a team’s first Lean success because it asks so little and shows so much. It is also a doorway: the questions a board raises — where is the constraint, why do items wait, what is our real capacity — are exactly the questions the broader Lean and Six Sigma toolkit answers. Our free White Belt program covers that foundation in about six hours, with a 30-question exam and a verifiable certificate; Yellow Belt extends it across 14 hours of applied material for $129. Put up the board this week. When it starts asking questions you cannot yet answer, you will know what to learn next.