Kanban for Small Teams: A Practical Guide and WIP Limits

Key takeaways

Kanban is a way to make work visible on a board and to limit how much of it is in progress at once. It starts from the work you already do and changes it slowly, which is why small teams adopt it without a revolution.
A board needs only three columns to begin: To do, Doing and Done. The magic is not the columns. It is the limit on the middle one.
Limiting work in progress makes things finish sooner. When fewer items are open, each one spends less time waiting. The arithmetic behind it is simple and the effect is immediate.
Three habits keep a board honest: write what "done" means, mark blocked items in red and review the board for fifteen minutes every week.
Kanban is not right for everything. When tasks must follow a fixed sequence, as in construction, a schedule with dependencies does a better job, and the two can live side by side.

Every small team has the same secret enemy, and it does not wear a villain's cape. It is the half-finished thing. The proposal that is "almost ready." The website page that needs "just one more look." The client reply that has been in a draft since Tuesday, and the invoice that three people believe somebody else sent. Individually, they are small. Together, they are why a busy team looks productive and delivers surprisingly little.

Kanban is a cheerful, low-tech weapon against that enemy. It has no certification you must buy and no vocabulary you must learn. It is a board with columns, a few rules and one strongly worded request: finish things.

In this guide I will explain what kanban is in plain English, where it comes from, how to set up a useful board in 30 minutes, the one rule that gives it power, the numbers worth watching and the situations in which you should use something else. I will use examples from small teams: a workshop, an agency, a clinic office. Where examples are invented, they are labeled illustrative.

Where kanban comes from, in sixty seconds

The word kanban is Japanese and roughly means "signboard" or "card." The idea began in manufacturing at Toyota in the decades after the Second World War, where it was part of a system for making only what was needed, when it was needed. A card traveling with parts told the next station that more was required: work was pulled by demand, instead of being pushed onto the next station whether or not it could cope.

Much later, in the 2000s, consultant David J. Anderson adapted the idea for knowledge work such as software, services and marketing, where the "parts" are tasks and projects. The Kanban method that came out of it has a short list of practices: visualize the work, limit work in progress, manage the flow, make the rules explicit, create feedback loops and improve together, in small steps.

That is the full theory. Everything else is habit.

The simplest board in the world

Take a wall, a whiteboard or a free online board and make three columns:

To do: work that has been agreed but not started.
Doing: work somebody is actively working on today.
Done: work that is finished according to your definition of done (more on that in a moment).

Each piece of work is a card. A card should be small enough to finish in a few days. "Redo the website" is not a card. "Rewrite the Services page" is.

Write every piece of current work on a card and place it in the right column. Do it honestly. When a team does this for the first time, a ritual repeats: the Doing column gets very crowded, and someone says, "Wait, we have that many things open?" That reaction is the first benefit. You cannot manage what you cannot see.

A small craft workshop with handwritten order cards pinned in rows on a wooden board above a workbench, a maker working in the background — Kanban is older than software: a board of cards above a workbench has been running small shops for decades.

Make the board match your real work

Once the basic board works, you can add columns that reflect the real steps of your work. A small design agency might use: Backlog, Briefing, Design, Client review, Revisions, Done. A clinic's administrative team might use: Requested, In progress, Waiting for patient or insurer, Done. A workshop might use: Quoted, Materials ordered, In production, Ready for pickup, Delivered.

A good test of a column: someone should be able to look at a card and know, without asking, what has to happen next and who has to do it. If the answer is "it depends," the column is too vague.

The rule that makes it work: limit work in progress

A board without limits is a to-do list with better lighting. The feature that turns it into a system is the work-in-progress limit (WIP limit): a number written at the top of a column that says how many cards may be in it at the same time.

If the limit on Doing is six, the seventh card cannot enter until one of the six leaves. This feels restrictive at first, and it is, on purpose. Here is why it works.

The restaurant analogy

Picture a kitchen where the chef accepts twenty orders at the same time and begins all of them. Every table has something on the stove. Nobody has a complete meal. Everyone waits longer, the food gets cold and the cooks forget which sauce goes with which plate. Now picture a kitchen that starts a new order only when a plate goes out. Each meal takes about the same time to cook, but the waiting disappears, and the diners are served sooner.

Teams work the same way. Starting too many things means each one spends most of its life waiting: waiting for you to come back to it, waiting for someone's reply, waiting for your attention while you switch between five tasks. Switching also costs time, because every return to a task begins with "where was I?"

The arithmetic

There is a neat piece of arithmetic behind this, known as Little's law. For a steady flow of work, the average time an item spends in progress equals the number of items in progress divided by the number of items you finish per week. If your team finishes 6 items a week and has 18 in progress, the average item takes about 3 weeks from start to done. If you limit work in progress to 8 items, and the team still finishes 6 a week, the average falls to about 1.3 weeks. Same people, same speed, and items finish in less than half the time, because less work is waiting in line.

That does not happen by magic, and real teams are messier than the formula. But the direction is reliable, and it is the reason many teams find that, after setting limits, they deliver faster without anyone working harder. The tool at the end of this article lets you run the numbers with your own team.

How to choose a limit

Start with a number close to the number of people, or a little more. A team of four might begin with a limit of six in Doing. Run for two weeks. If cards often sit blocked and the limit is constantly hit, either the limit is too low or something is blocking the flow, and you should find out which. If the limit is never reached, lower it. Limits are an experiment, not a law.

When the limit is reached and someone has free time, the right behavior is not "start something new." It is "help finish something that is already open." This single change in habit is worth the whole system.

Three rules that keep the board honest

1. Write down what "done" means

Done should mean the same thing to everyone. For a proposal, done might be "sent to the client and logged." For a blog post, "published and linked from two other pages." For an invoice, "sent and in the accounting system." Put the definition at the top of the Done column, in plain words. It ends the daily argument about whether a thing is finished.

2. Mark blocked cards in red

Any card that cannot move because it is waiting for something (a reply, a delivery, a decision) gets a red dot or a red card. Blocked work is the most expensive kind of work, since it looks active and is not. Review the red cards first in every meeting and ask only one question: who can unblock this, and by when? This is the same discipline as the "waiting" list in a construction schedule, where the real delays come from things nobody noticed were waiting.

3. Take fifteen minutes a week to look at the board

Do not wait for a crisis. Once a week, stand in front of the board with the team for fifteen minutes. Ask four questions: what finished, what is blocked, what is stuck too long and what comes next? Move cards and move on. This small ritual is a close cousin of the weekly review and of the weekly rhythm of Project Focus.

Four numbers worth watching

You can run a perfectly good board without any numbers. After a month, adding a few makes it much smarter. Keep them simple.

Throughput: how many cards finish per week. It tells you what your team really delivers, which is usually less than what it believes.
Cycle time: the days between a card starting and finishing. Track the average and the slowest items. Long cycle times point to waiting.
Work in progress: how many cards are open now. It should stay under the limit.
Aging: how long each open card has been in progress. A card that is far older than the others is a stuck card, even if it looks fine on the board.

You do not need software for these. Write the start date on a card when it enters Doing and the finish date when it moves to Done. A spreadsheet at the end of the week is enough. In line with the idea in data-driven project management, measure the few numbers that change decisions, and ignore the rest.

Set it up in 30 minutes

You can start on Monday. Here is the plan, with an illustrative small team of four people.

Minute 0 to 5: agree on the purpose. "We want to see all our work and finish more of it." One sentence.
Minute 5 to 15: put every current job on a card. Include the small ones. Ask everyone to empty their heads onto the board.
Minute 15 to 20: place the cards. To do, Doing, Done. Be strict about Doing: if nobody touched it this week, it is not Doing.
Minute 20 to 25: set the first limit. Count the cards in Doing. If there are twelve and the team is four, set the limit at six and decide which cards go back to To do.
Minute 25 to 30: agree the three rules. Definition of done, red cards for blocked items and a fifteen-minute review each week.

Then run it for two weeks without changing anything big. Adjust one thing at a time: a column, a limit, a rule.

Close-up of a hand moving a yellow sticky note from the middle column to the last column of a kanban board, shallow depth of field — The most motivating movement in project management: a card traveling to the last column.

Physical board or digital board?

Both work. A physical board on a wall has a big advantage: everyone sees it without logging in, and moving a card feels satisfying. A digital board is better when the team is remote, when work needs attachments or when you want automatic history. Many teams use a physical board for the weekly meeting and a digital one for details. The best tool is the one the team will really open on Wednesday afternoon, not the one with the most features.

When kanban is not enough

Kanban is wonderful for a flow of work that keeps arriving: requests, orders, content, support tickets, small projects. It is weaker in these cases:

Work with a fixed sequence and hard dates. Building a house, opening a clinic or installing a system have tasks that must follow each other. The right tool is a schedule with dependencies and a critical path, maybe shown in a Gantt chart. A kanban board can still manage the weekly detail inside each phase.
A project with a deadline and many connected parts. You need a plan with milestones. A board shows what is happening; a plan shows whether the date is safe.
Resource conflicts. If one specialist is needed on every card, no limit will fix that. The issue is capacity, and you will find the way to see it in capacity planning and bottlenecks.

I often combine them: a simple schedule for the dates that must not move, and a kanban board for the daily work. If you are choosing between methods, the article on agile, waterfall or hybrid helps you decide, and the list of seven workflows you could put on autopilot shows which repeating cards a machine could carry.

A short hall of fame of kanban mistakes

The Board That Became a Museum. Beautiful, colorful and untouched since March. A board is only alive if cards move at least weekly.
The Infinite Doing Column. No limit, forty cards, one tired team.
The Card Called "Marketing." Too big to finish, too vague to start.
The Hero Who Takes Everything. One person has all the cards, and the limit gets ignored because "it is just a quick one."
The Secret Work. Real work that never reaches the board, then everyone wonders why the numbers do not match what they feel.
Red Cards Nobody Reads. Blocked items that stay red for weeks. If a card is red for more than a week, escalate it to someone who can fix it.

Try the numbers on your own team

Use the tool below to see what a work-in-progress limit could do. Enter how many items your team has in progress, how many it finishes in a typical week, and a limit you would like to try. It will show the average time to finish an item today and with the limit. It is a simplified model, so take it as a direction and then test it on your board for two weeks.

What to do this week

Pick one team, even if it is just you and a colleague. Write every piece of current work on a card, put the cards in three columns, and set a limit on Doing. Do not buy anything and do not install anything. At the end of the week, count how many cards moved to Done, and write that number down. It is your first throughput, and it will be more honest than any guess.

If your team is drowning in half-finished work and you would like help setting up a rhythm that fits your business, that is what I do with Project Focus. You can see the services, or tell me about your team on the contact page. If you work in Utah, here is how I work as a business consultant in Utah.

How many things is your team working on right now, and how many of them could you finish by Friday if nothing new started? Tell me in the comments.

More tools. The decision log, the risk register and the weekly review pair well with a board and are free in the toolkit.

Frequently asked questions

What is kanban in simple terms?

Kanban is a way to see your work on a board with columns, such as To do, Doing and Done, and to limit how many items can be in progress at once. The limit helps work finish sooner, because fewer items wait in the queue.

How many columns should a kanban board have?

Start with three: To do, Doing and Done. Add columns only when your real work has distinct steps, such as review or waiting for a client, and each column has a clear meaning.

What is a WIP limit and how do I choose one?

A WIP, or work-in-progress, limit is the maximum number of cards allowed in a column at one time. A common starting point is close to the number of people on the team, or a little more, adjusted after two weeks of real use. If the limit is always reached and cards are blocked, find out what is blocking the flow before changing the number.

Is kanban better than Scrum or Gantt charts?

They solve different problems. Kanban suits a steady flow of requests and small tasks. Scrum organizes work in fixed cycles, and Gantt charts show dependencies and dates, which matters for projects like construction. Many teams combine a schedule for fixed dates with a board for daily work.

Kanban for Small Teams: Finish More by Starting Less

Where kanban comes from, in sixty seconds