A kanban pull system means a card only moves into an active column when there is an open slot for it, never because a plan says today is the day to start. The signal to begin new work comes from finished work leaving a stage, not from a schedule written in advance. A WIP limit and a pull system are the same mechanism seen from two sides: the limit is what creates the open slot, and the slot is what pulls the next card forward. Without an enforced limit, "pull" is just a word painted over an ordinary to-do list.
Pull versus push, with an actual board
A push system assigns work on a timetable. A sprint plan, a manager's list, or a due date decides when something starts, whether or not anyone has room for it. A pull system works the other way: work enters a stage only because that stage has room, and something already there just left.
Take a small content board:
Backlog | Writing (2) | Editing (1) | Published
Writing is already full. "Q4 launch email" and "Product changelog for October" are both active there. A third piece, "Customer story draft", sits in Backlog waiting its turn. It does not move into Writing because Monday arrived or because someone decided it was next. It moves in once one of the two active pieces clears the column, either by finishing and moving to Editing or by getting pulled back out because it stalled. The open slot is the invitation. The calendar has nothing to do with it.
The board that looks like kanban but isn't one
The most common failure is building a board with the right column names and no pull at all, rather than skipping kanban outright. Three plain headings with no limit on the middle one will happily hold twelve cards at once, and nothing about the layout stops a thirteenth from landing there the moment someone thinks of it.
That board still looks like kanban in every screenshot. It just behaves like a list with headings. Nothing in it ever waits for a slot, because there is no slot to wait for. If your Doing column has grown past what anyone could plausibly be working on at once, the board has quietly become a push system with better formatting.
What actually happens when a column is full
On a physical board, this is not subtle. There is no space to pin a fourth card in a column with three slots, so someone has to make a decision before the new card gets a spot at all.
Software boards are less consistent about it, and this is where most explanations of pull systems stop short. Some tools block the move outright and refuse to let a card land in a column that's already at its limit. Others, EasyKanban included, treat the limit as advisory: the column header shows the overload, but the card can still be dropped there. The reasoning is practical rather than lazy. Refusing a drag mid-gesture would abort the move the moment a finger or cursor crossed into a full column, which is a worse experience than a coloured header that asks you to look. Either way, the point of the signal is the same: a full column is where the team decides whether to finish something, unblock something, or genuinely widen the limit, not where the tool quietly lets the queue grow.
If your tool doesn't block the move, the pull system only works if someone actually looks at the signal and acts on it. A limit nobody enforces is a decoration.
Pull and WIP limits are one idea, not two
It's easy to read about pull systems and WIP limits as if they were two separate techniques you bolt onto a board. They aren't. The WIP limit is the number; pull is the behaviour that number produces once it's actually respected. Set "Writing (2)" and enforce it, and you have a pull system for that column, whether or not anyone in the room uses the word "pull". Skip the enforcement and the number is trivia.
This post is about why that mechanism matters. For the practical side, how to pick the actual number, where to place it, and what to do when a column stays full for a week, see WIP limits in Kanban.
Where the idea comes from
Kanban started as a physical signal on the Toyota production line in the 1940s and 50s: a card attached to a bin of parts that only triggered a reorder once the bin was empty, so the next batch got pulled by actual consumption instead of pushed by a forecast. The Lean Enterprise Institute's kanban entry covers that manufacturing origin in more depth. The version on a software board keeps the same logic and swaps parts bins for cards: a slot opens, so the next piece of work gets pulled forward. The Atlassian kanban guide has a good overview of how the method carried over from the factory floor to knowledge work.
Frequently asked questions
What is a pull system in kanban?
It's a way of starting work only when there's capacity for it. A column's WIP limit caps how many cards can be active at once, and a new card enters only after an existing one leaves, freeing a slot. Nothing starts on a schedule; it starts when the board has room.
What's the difference between a push and pull system?
A push system starts work on a plan, a due date, or someone's decision, regardless of how much is already in progress. A pull system starts work only when an active stage has an open slot, created by something else finishing or leaving that stage. Kanban is a pull system; a sprint backlog assigned in advance is closer to push.
Do you need a WIP limit to have a pull system?
Yes. Without a limit, every column has unlimited room, so nothing is ever actually waiting for a slot. The limit is what creates scarcity, and scarcity is what makes "pull" mean anything more than "things move left to right eventually."
Can a solo or personal kanban board use a pull system?
Yes, and it's often where it matters most. A one-person board with "Doing (1)" turns pull into a simple rule: finish or set aside the current task before starting the next one. See personal kanban for goals and daily focus for how that plays out day to day.
Does every kanban tool block a card when the limit is reached?
No. Some tools refuse the move outright; others, including EasyKanban, let the card land and flag the column instead. Either way, the limit only works as a pull system if someone treats a full column as a decision point rather than a suggestion.
Related reading
- Scrumban Explained: Kanban With a Planning Trigger
- Kanban vs Scrum: Which Workflow Fits Your Team?
- What Is Kanban? A Practical Guide for Beginners
Try building the "Writing (2)" example above on your own board. Start a free board on EasyKanban and add one WIP limit before you add anything else. It's the fastest way to feel the difference between a board that pulls work forward and one that just holds a list.