A Kanban system is a visible workflow with an explicit policy for how work enters and moves. A board that is a wallpaper of tickets is not a system. It is a to-do list that learned to stand up. The cards are not the point. The agreement is the point.
Visualise the flow you actually have
Map columns to the real states work sits in — Ready, In development, Review, Waiting on vendor, Done — not the three you copied from a template. If work regularly vanishes into 'with Dave,' Dave is a column. Hidden states are hidden queues.
Each card should be a single unit you could finish and count: a story, a change, a ticket. Cards that are secret projects in a trench coat destroy every metric you will meet in two lessons. Split them. If you cannot split them, you do not have an item. You have a hope.
Policies belong on the board: what 'Ready' means, what 'Done' means, who can pull, what happens when a card is blocked. A board without policies is interior decoration. People will invent private rules, then argue about why the other column is being unreasonable.
Pull: start because there is a slot, not because there is a Monday
In a pull system, a person takes the next ready item when they have capacity in their column — and only then. Nobody assigns six things on Monday because the sprint fairy arrived. Assignment is push. Pull is a signal: there is space, so replenish.
Replenishment is a meeting with a purpose: fill the Ready column up to its limit, in priority order, with items that meet the entry policy. It is not a status tour. If replenishment becomes a two-hour wander through the backlog, you have reinvented sprint planning and forgotten the limit.
Blocked work stays visible. A card that sits in a 'blocked' swimlane for a fortnight is a management failure on display, which is the point. Moving it back to 'Ready' to tidy the board is how systems lie. Kanban is rude on purpose. Rude and true beats polite and late.
It is a system for the stream, not a team hobby
Kanban can sit on a Scrum team, a service desk, or a portfolio. The mechanics do not require sprints. They require a stream of similar work, a visible path, and a willingness to limit what is mid-flight. If your work is a one-off construction sequence with no repeating flow, you may want a network diagram more than a board. Tools are not moral.
Classes of service — expedite, standard, fixed date — are policies for when something may break the usual order. An expedite lane with no limit is a hole in the system. Everything becomes expedite by week three. If leadership wants a fast lane, they also own the rule for how rare it is.
Do not start by buying a tool. Start with the states, the policies, and a physical or simple digital board the team will actually update. A neglected Jira project is still a neglected system. The next lesson is the policy that makes the board more than a picture: the WIP limit.
Summary & next steps
A Kanban system visualises real states, attaches explicit policies, and pulls work when there is a slot. Cards are countable items. Hidden queues and unlimited expedite lanes are how boards become fiction.
Next: WIP limits — the policy that makes pull real, and the slogan that fails the first time someone is anxious.