What Kanban actually is
Kanban is a way to make work visible. You draw your process as columns (the stages a piece of work goes through), you put every piece of work on a card, and you move the card from left to right as it progresses. That is the whole idea.
It works because it answers three questions without a meeting: what are we working on, where is each thing stuck, and what is next.
Set it up in five steps
- List everything you are working on right now. Every request, ticket, job or task, including the ones that live only in someone's head or in an inbox. Do not clean it up yet.
- Pick three to five stages. Name them after what really happens, not after a template. A typical flow is Backlog → In progress → Review → Done. If you cannot say what "done" means for a stage, the stage is too vague. (Most service teams end up with the same five stages.)
- Put every item on a card in the stage it is really in. Be honest. A card that has not moved in a week belongs where it is stuck, not where you hope it is.
- Limit work in progress. Choose a maximum number of cards for the middle stages, and do not pull new work until something finishes. This is the rule people skip and the one that makes Kanban work. See WIP limits.
- Review the board every day. Five minutes: what is stuck, what is blocked, what can move. If a card is stuck, find out why before you start something new.
Add the part most boards are missing: time
A board shows where work is. It does not show how long it has been there. That is why a card can sit in "In progress" for ten days and nobody notices until the customer asks.
Give each stage a time budget. "A job spends at most 2 days in Review." Now every card has a clock, and you can mark it on track, at risk or overdue. That is what an SLA is at the job level, and it is the difference between a picture of your work and a system that warns you. If you want to try numbers before you commit, the free SLA calculator adds up your stages and shows whether the promise you make to customers fits.
Why sticky notes and spreadsheets stop working
- Nobody sees the clock. A sticky note does not turn red on day three. Someone has to remember to look.
- It only works in one room. The moment a person is remote, on a phone, or on another shift, the wall is out of date.
- No history. When a job goes wrong you cannot see where it slipped or who had it.
- No alert. Spreadsheets update when a human updates them. A board with timers updates itself.
- Customers cannot see it. The "is it ready yet?" phone call is a symptom of work that is visible only to you.
Common mistakes
- Too many columns. Eight stages is a process document, not a board. Start with three.
- No limit on work in progress. If the middle column keeps growing, you are starting work faster than you finish it.
- One card per big project. Cards should be small enough to finish in days. Split big work.
- Cards without an owner. A card nobody owns does not move.
- Treating the board as a report. It is a tool for the team to decide what to do next, not a status slide for a manager.
Doing it automatically
Everything above can be done by hand, and for a few weeks it is a good way to learn the method. When you have more than a handful of jobs, let software keep the clock.
In QodFlow you get the stages, the card for every job, an owner, a priority flag, and a time budget that turns each card on track, at risk or overdue by itself. The Free plan covers up to 3 people and 10 active jobs, with one due date for every job that you set once for the whole board. Premium adds a separate time budget per stage and tags, Diamond adds client status pages, and every paid plan starts with a 30-day trial that does not ask for a card. AI agents can work on the same board too; here is how that works.
Start with the Free plan, add your first job, and see which stage it gets stuck in.