Boards and Bottlenecks

Two boards. Board one: To Do, Doing, Done — tidy, colorful, updated daily. Board two looks messier: it has a column called "Waiting for approval," and that column is embarrassingly full. Here's the uncomfortable truth: the messy board is the better board. Because a board's job isn't to look organized. Its job is to tell the truth.

By the end of this video, you'll be able to design board columns that mirror how work actually flows — including the waiting — write the explicit policies that make a board trustworthy, and spot a bottleneck at a glance, plus the one correct response when you find it.

A board is your workflow made honest. So the columns must be the real stages work passes through — not the stages you wish it passed through. If every item in your world sits three days waiting for a manager's sign-off, then "Waiting for approval" belongs on the board as its own column. Not because you like it. Because you can't fix a queue you refuse to look at. A visible queue is a diagnosable queue; an invisible one just becomes "why is everything slow?"

This is Kanban's first practice from Module 2 — visualize the work — grown up. Visualizing doesn't mean decorating. It means confessing.

Second ingredient: explicit policies — Kanban's practice of writing down what the columns actually mean. What does it take for a card to enter "Doing"? What must be true before it moves to "Done"? Write it on the board itself: "Doing means actively touched today." "Review means a named reviewer has it." Without written policies, every column means something different to every person, cards drift on vibes, and the board quietly starts lying. With them, anyone can look at the board and trust what they see — that's the transparency leg of empiricism, from all the way back in Module 2. And per-column WIP limits, from last lesson, live here too: a number in each column header, enforced without apology.

Now the payoff skill. A bottleneck is the stage where work piles up — and it sets the pace for the entire system, the way the narrowest point of an hourglass sets the pace of the sand. On an honest board, you don't need analytics to find it: it's the column where cards accumulate while columns after it sit hungry.

Run the non-software example: a hiring pipeline. Columns: Screening, Interview, Offer. Screening moves fast — recruiters clear it daily. Offers go out same-day once decisions land. But Interview has fourteen candidates parked, because only two managers conduct interviews and both are booked solid. That swollen middle column is the hiring speed of the whole company. Adding recruiters — feeding the bottleneck faster — makes the pile bigger, not the hiring faster.

The correct response you already know from last lesson: swarm the bottleneck. Add interviewers, simplify the interview, batch the slots — put effort where the pile is, because an hour saved at the bottleneck is an hour saved for the whole system, and an hour saved anywhere else is usually an illusion.

One glance-tool to file away: if you ever chart how many cards sit in each stage over time — a cumulative flow diagram — trouble looks like one band steadily widening. Widening band, growing queue, found bottleneck. That's all the chart-reading this course needs.

You might think a Kanban board is basically a to-do list with columns — plenty of teams use it exactly that way, so the confusion is earned. Actually, the list is the least of it. The board becomes a system the moment it has three things a to-do list never has: honest columns including the waiting, written policies, and WIP limits. Remove those and yes — it's sticky-note decoration. Add them and the board starts doing your diagnosis for you.

Three things to keep. One: columns are a confession — model the real flow, waiting included, because visible queues are diagnosable queues. Two: explicit policies plus WIP limits make a board trustworthy instead of decorative. Three: the bottleneck is where work piles; swarm it — never feed it.

Boards improve the work. But who improves the team? Next lesson: the meeting that — done right — is the engine of everything, and — done wrong — is the most-skipped half hour in modern work.