Walk into most small businesses and ask, “What’s everyone working on right now?” You’ll get a pause, then a scramble through inboxes and sticky notes.
Kanban fixes that with a board.
Where kanban came from
Kanban — Japanese for something like “signboard” or “visual card” — grew out of Toyota’s production system, where cards signaled when to produce more parts. Later, practitioners such as David J. Anderson adapted the idea for knowledge work, and it spread to software, marketing, operations and service teams everywhere.
The core practices
- Visualize the work. Every piece of work is a card on a board with columns showing its stage.
- Limit work in progress. Cap how many cards can be in a column at once.
- Manage the flow. Watch how work moves and where it gets stuck.
- Make the rules explicit. What does each column mean? When can a card move?
- Review and improve. Regularly look at the board’s flow and fix the bottlenecks.
Setting up a board for a service business
Start simple. Here’s a board for a small home services or professional services company:
| New | Scheduled | In progress | Waiting on customer | Quality check | Done |
|---|---|---|---|---|---|
| Job cards land here | Date set, crew assigned | Work underway | Blocked on info, payment or access | Checked against the standard | Invoiced and closed |
Each card shows the customer, the owner and the due date. Anyone in the business can see the state of every job.
For a marketing team: Ideas → Ready → Writing/Building → Review → Scheduled → Live → Measured.
For an operations improvement team: Backlog → This month → Doing → Testing → Standardized.
WIP limits: the part that changes everything
The board makes work visible. WIP limits make it flow.
Without them, people start new work whenever they get stuck, and the “In progress” column fills with half-finished cards. Everything takes longer because everyone is juggling.
Set a limit on the In progress column — say, two cards per person. When the column is full, nobody starts anything new until something moves forward. People help each other finish instead.
Kanban vs scrum
| Kanban | Scrum | |
|---|---|---|
| Cadence | Continuous flow | Fixed sprints |
| Roles | None required | Product Owner, Scrum Master, Developers |
| Change | Add work anytime (within WIP limits) | Changes usually wait for the next sprint |
| Best for | Ongoing, interrupt-driven or service work | Project work that can be planned in short cycles |
| Key metric | Cycle time and flow | Sprint goal achieved |
Many teams use both: Scrum for project work, kanban for support and service work. See scrum for business teams.
Measuring flow
Two numbers tell you most of what you need:
- Cycle time: how long a card takes from start to done.
- Throughput: how many cards finish per week.
Put them on your weekly business scorecard. If cycle time rises, look at the board — the column where cards pile up is your bottleneck. See business bottlenecks.
Physical or digital?
A whiteboard and sticky notes work great for a team in one room. Digital boards work better for remote teams and for linking cards to files, checklists and customer records. Many CRMs and project tools have board views built in. The tool matters less than the habit of keeping the board current.
Common mistakes
- No WIP limits. The board just becomes a prettier to-do list.
- Too many columns. Five or six is plenty.
- Stale cards. If the board isn’t current, people stop trusting it.
- No review. Look at the board’s flow every week and fix what’s stuck.
- Hiding blocked work. Make a “Waiting” or “Blocked” column so problems are visible.
Kanban inside the operating rhythm
The board shows the work; the weekly meeting decides what to do about it. In the BOSS framework, project boards track the work behind Quarterly Goals, and stuck cards become issues in the weekly Momentum Meeting. See the weekly leadership meeting agenda.
A one-afternoon setup
Gather the team, list every active piece of work on cards, agree on five or six columns and what each means, place every card, and set a WIP limit for the In progress column. Then agree on one rule: the board is updated before the daily huddle. That’s it. By the end of the first week, you’ll see where work piles up — and that’s the first improvement to make.
Next steps
Set up one board this week. Add a WIP limit. Review it daily for two weeks. For the bigger picture, see agile for business. If you’d like help connecting boards to your weekly leadership rhythm, request a strategy call.
Keep it simple, keep it current, and let the board show you the next thing to fix.
The board will tell you the truth about your workload faster than any meeting can.
Questions people ask
What is kanban?
Kanban is a method for managing work by visualizing it on a board, limiting how much work is in progress at once, and improving the flow of work from start to finish. It originated in manufacturing at Toyota and was adapted for knowledge work.
What is a WIP limit?
A work-in-progress limit caps how many items can sit in a column, such as Doing, at one time. When the column is full, the team finishes something before starting something new, which reduces multitasking and speeds up delivery.
What is the difference between kanban and scrum?
Scrum organizes work into fixed-length sprints with defined roles and events. Kanban is continuous flow with no required sprints or roles; it focuses on visualizing work and limiting work in progress.