Most small teams do not fail for lack of effort. They fail because nobody can see all the work at once. Tasks hide in inboxes, chat threads and people's heads, and priorities shift with whoever shouted last. A Kanban board fixes this by putting every piece of work on one shared surface. This guide answers the practical questions: how to set one up, how to limit work in progress, and how to keep the board useful week after week.
What is a Kanban board and why use it for operations?
A Kanban board is a visual map of your work. Each task is a card, and each column is a stage it passes through, from left to right. It suits operations because day-to-day work is a flow of many small items, not one big project. The board shows what is waiting, what is moving and what is stuck, without a status meeting.
Which columns should you start with?
Keep it simple. Four to five columns are enough for most teams:
- Backlog. Everything that has been agreed but not started, loosely ordered by priority.
- Ready. The next few items, clear enough that someone can pick one up today.
- Doing. Work someone is actively moving forward right now.
- Waiting or Blocked. Work that cannot progress until someone outside the team responds.
- Done. Finished work, kept visible for a week or so, then archived.
Add columns such as Review or Approval only when work really does pause there. Every extra column is one more place for cards to sit.
What is a WIP limit and how do you set one?
A work-in-progress (WIP) limit is a cap on how many cards may be in a column at once. It matters because starting is easy and finishing is hard. Without a cap, people begin new items whenever they are blocked or bored, and everything takes longer.
A practical starting point for the Doing column is the number of people on the team, or one card per person plus one. A team of five might set a limit of six. When the column is full, nobody pulls a new card. They help finish one instead. If the limit feels painful, that is the point: it shows where work is really getting stuck. Adjust it after a few weeks, but do not remove it.
What makes a good card?
A card should be small enough to finish in a few days and clear enough that anyone could understand it. A useful card includes:
- A short title that starts with a verb, such as “Send renewal quote to Acme”.
- One named owner, not a group.
- A due date only if there is a real deadline.
- A short definition of done, so everyone agrees when it can move to Done.
- A link to the details, rather than pasting them in.
If a card sits in Doing for more than a week, it is usually two or three tasks in disguise. Split it.
How do you handle recurring work and one-off requests?
Operations teams carry two kinds of work that behave differently. Recurring tasks, such as month-end checks, weekly reports or equipment audits, are predictable. Requests from colleagues are not. Separate them with swimlanes, which are horizontal rows across the board:
- Routine lane. Recurring tasks, created from a template on their schedule, so they never depend on someone remembering.
- Requests lane. Incoming asks from other people or teams.
- Urgent lane (optional). One slot for genuine emergencies, with its own limit of one or two cards.
Swimlanes also make trade-offs visible. If the Requests lane is full, you can see that the routine work is quietly suffering. How requests get into the board in the first place is a topic of its own, covered in our guide to request intake.
How do you run a weekly review?
Spend 20 to 30 minutes at the same time each week, standing in front of the board. Work through it from right to left, so you focus on finishing:
- Celebrate what reached Done, and archive old cards.
- Look at Waiting or Blocked. Who needs a nudge, and who can unblock it?
- Check Doing for cards that have not moved. Split, drop or help them along.
- Fill Ready from the Backlog with next week's priorities.
- Ask one question: what slowed us down this week?
Which metrics are worth tracking?
- Cycle time. How many days a card takes from Doing to Done. Track the median and watch the trend.
- Throughput. How many cards finish per week. It helps you judge what you can promise.
- Age of work in progress. How long open cards have been sitting. This is an early warning.
- Blocked time. How long cards wait on others.
If cycle time keeps growing and one column always has the longest queue, you have likely found your bottleneck. Our guide on finding bottlenecks shows how to dig into it.
Common Kanban mistakes
- An overloaded Doing column. Fifteen cards in progress means nothing is really in progress. Enforce the limit.
- Cards that are too big. Vague items like “Improve onboarding” never move. Break them down.
- A board nobody updates. If the board lags behind reality, people stop trusting it. Update it in the moment, or at a short daily stand-up.
- Too many columns and lanes. Complexity hides the picture you wanted to see.
- Ignoring blocked work. Waiting cards are still unfinished work. Give them an owner and a follow-up date.
- Using it as a dumping ground. A backlog of 200 old items is noise. Prune it monthly.
Start with a simple board, a firm limit and a weekly review. Change one thing at a time, and let the data tell you what to improve next. If you want the board connected to your projects and KPIs, FulcrumGrid Command Center can hold them together, but a whiteboard and sticky notes are enough to begin.
Frequently asked questions
How many columns should a Kanban board have?
Four or five are enough for most teams: Backlog, Ready, Doing, Waiting and Done. Add more only if work genuinely pauses at that stage.
What WIP limit should a small team use?
A common start is one card per person plus one in the Doing column. Review it after a few weeks, but keep some limit in place.
What is cycle time in Kanban?
Cycle time is the number of days a card takes from the moment work starts until it is done. The median across recent cards is the most useful figure.
Can I use Kanban for recurring tasks?
Yes. Put recurring tasks in their own swimlane and create the cards from a template on schedule, so they do not depend on memory.
How often should we review the board?
A short daily look at blocked cards and a 20 to 30 minute weekly review work well for most small teams.
FulcrumGrid Command Center
Keep your team's work in one clear view
FulcrumGrid Command Center helps you track projects, tasks and KPIs together, so what is moving and what is stuck stays visible all week.