Skip to content
  • Official
  • Beginner
  • English
  • 10 steps · 2 quizzes

Kanban Workshop: Visualize Work and Limit Work in Progress

Kanban training exercise for teams: build a board, set WIP limits in a flow simulator and watch lead time fall. Practise Little's Law and read a CFD.

  • Free
  • No account needed
  • Stop any time, pick up where you left off
Workshopy.io

WorkshopyOfficial

78 lessons · used by 2 teachers

For teachers

Teaching this? Run it live with your class.

  • Students join with a code — no accounts
  • See who’s done and who’s stuck, step by step
  • It’s your copy — change anything before class

Sign in to copy it to your workspace. It’s free.

Your path

10 steps · 2 quizzes · open any step, or read it here

  1. Start here: why does starting less finish sooner?Start hereThis Kanban workshop starts with a problem most teams know: more work gets started than finished. Everyone is busy and the board is full, yet each request still takes weeks to get done.InteractiveHands-on
    Read this step

    This Kanban workshop starts with a problem most teams know: more work gets started than finished. Everyone is busy and the board is full, yet each request still takes weeks to get done.

    Interactive · Start everything, or limit work in progress? — try it in the lesson

    You just watched one team with the same requests on two boards. On the top board everything starts at once and piles up in Build; on the bottom board each column has a work-in-progress limit, and far more reaches Done. By the end of this lesson you can set those limits on your own team's board.

    What you'll do

    • Sort a messy pile of real work onto a Kanban board, and flag what is stuck
    • Compare pushing work with pulling it, side by side
    • Set WIP limits in a flow simulator and watch lead time and throughput change
    • Explain what you saw with Little's Law and a cumulative flow diagram

    By the end you can

    • build a board for your team's work and set WIP limits you can defend
    • predict lead time from the amount of work in progress
    • read a cumulative flow diagram and write policies for blockers and urgent work

    You need a laptop or tablet. No Kanban experience needed.

  2. Kanban workshop: visualize work and limit work in progressIn this Kanban workshop you visualize your team's work on a board and learn why limiting work in progress makes each item finish sooner.InteractiveHands-on
    Read this step

    In this Kanban workshop you visualize your team's work on a board and learn why limiting work in progress makes each item finish sooner. You will run a small flow simulator, set WIP limits yourself and watch lead time fall while the team gets just as much done.

    Below are two copies of the same team with the same requests. On the top board everyone starts work the moment it arrives. On the bottom board each column has a limit on how many items it may hold. Press Play and watch where the work piles up.

    Interactive · Same team, same requests: start everything or limit WIP — try it in the lesson

    The lead time shown is the average for items finished in the last two weeks: how long an item took from the moment the team started it until it was done. The numbers are illustrative, but the pattern is the one teams see on real boards.

    Takeaway: starting less work is how each piece of work finishes sooner.

  3. Visualize the work: build the boardKanban started on Toyota's factory floor, where a kanban (Japanese for "signboard" or "card") told the previous station to make more parts. The Kanban Method for knowledge work was worked out by David J.InteractiveHands-on
    Read this step

    Kanban started on Toyota's factory floor, where a kanban (Japanese for "signboard" or "card") told the previous station to make more parts. The Kanban Method for knowledge work was worked out by David J. Anderson in the mid-2000s and described in his 2010 book Kanban. Its first rule is gentle: start with what you do now. You don't reorganise the team or rename roles. You draw the work as it really flows today.

    A board has columns for the stages work passes through, and one card per piece of work. The simplest board is To do · Doing · Done. Every card says what the work is, so anyone can read the board in a minute and know:

    • what is waiting,
    • what is being worked on, and by whom,
    • what is finished,
    • what is stuck.

    The last one matters most. A blocked item is one that can't move because it waits on someone outside the team: a supplier, another department, a customer's answer. Mark it so everyone sees it, with a red sticker or a flag.

    Try it: here is a support team's work this morning, unsorted. Tap a card, then tap Move here under the column where it belongs. Then flag the item that is stuck.

    Interactive · Sort a support team's work onto a board — try it in the lesson

    Takeaway: draw the work as it flows today, one card per item, and make blocked work impossible to miss.

  4. Pull, not push: WIP limits per columnIn a push system, each stage hands work on as soon as it's finished, whether the next stage has room or not. Work piles up in front of the slowest stage, the bottleneck, and every item in that pile ages while nobody touches it.InteractiveHands-on
    Read this step

    In a push system, each stage hands work on as soon as it's finished, whether the next stage has room or not. Work piles up in front of the slowest stage, the bottleneck, and every item in that pile ages while nobody touches it.

    In a pull system, a stage takes new work only when it has room. That room is set by a work-in-progress (WIP) limit: the most items a column may hold at once, written at the top of the column ("Build 4"). When a column is full, the stage before it doesn't push more in. Its people help finish what is already started, or fix what slows the bottleneck.

    Try it: a content team's writers can draft 3 articles a day, and the one editor can review 2. Play 10 days with Push, then switch to Pull, limit 2 and play again.

    Interactive · Push or pull: a queue in front of the bottleneck — try it in the lesson

    After 10 days both teams have reviewed the same 18 articles, because the editor is the bottleneck either way. With push, 12 drafts are waiting and each finished article sat in the queue 2.5 days on average, and the wait grows every day. With pull, only 2 are waiting and the average wait is 1 day.

    A few rules for WIP limits:

    • Set a limit per column, starting near what the column holds on a normal day, then lower it step by step.
    • Count every item in the column, including items finished there and waiting to be pulled.
    • A full column is a signal, not a failure: stop starting, start finishing.

    Takeaway: a WIP limit turns push into pull, and the queue in front of the bottleneck stops growing.

  5. The flow simulator: limit WIP, watch lead timeNow a whole board. A product team gets requests into its Backlog. When the team commits to an item it pulls it into Analyse, then Build, then Test, then Done. Build is the slowest stage: on average it can finish about 1.6 items a day.InteractiveHands-on
    Read this step

    Now a whole board. A product team gets requests into its Backlog. When the team commits to an item it pulls it into Analyse, then Build, then Test, then Done. Build is the slowest stage: on average it can finish about 1.6 items a day. New requests arrive at 1.5 a day, and 12 are already waiting on day 1.

    Three numbers tell you how work flows:

    • WIP: how many items are started and not yet done (Analyse + Build + Test).
    • Throughput: how many items the team finishes per day.
    • Lead time: how many days an item takes from the day the team pulls it out of the Backlog until it reaches Done.

    Each slider sets the column's WIP limit; slide it all the way right for no limit. Every run uses the same requests, so you can compare runs fairly. Your runs are listed under the numbers.

    Try it: do the three tasks at the top of the simulator.

    Interactive · Kanban flow simulator: set WIP limits, watch lead time — try it in the lesson

    What you should see:

    • No limits: everything starts at once. Build holds around 30 items, each gets a sliver of attention, and an item takes over 20 days.
    • Sensible limits (for example 3 · 4 · 3): WIP stays under 10 and lead time falls to about 6 days. Throughput doesn't drop; it is set by Build, the bottleneck.
    • Limits that are too tight (1 · 1 · 1): lead time is short, but Build sometimes sits idle, throughput falls to 1 a day and the backlog grows.

    The work that isn't started yet waits in the Backlog, before the commitment point, where waiting is cheap: nothing is half-done and the team can still change its mind about it. A growing backlog is honest information too. It says demand is higher than the team's capacity, which is a conversation to have with whoever sends the work.

    The numbers in this simulator are illustrative. Real teams have more variation, but the direction is the same.

    Takeaway: limit WIP to the level that keeps the bottleneck busy. Less than that starves it, more than that only adds waiting.

  6. Check: boards, pull and WIP limitsQuiz · 4 questions
    Read the questions

    Question 1. A column on your board has a WIP limit of 3 and holds 3 items. You just finished your own item in the column before it. What does a pull system say you do?

    • Move your item in anyway, since it's finished
    • Leave it where it is and help the full column finish something
    • Start a new item so you are not idle
    • Raise the limit to 4

    Question 2. What is a blocked item?

    • An item nobody has started yet
    • An item that is over its WIP limit
    • An item that can't move because it waits on someone outside the team
    • An item that failed testing

    Question 3. In the simulator, removing every WIP limit mainly changed which number?

    • Throughput went up a lot
    • Lead time went up a lot
    • The backlog grew faster
    • Nothing changed

    Question 4. Why did very tight limits (1 · 1 · 1) lower throughput?

    • The team worked more slowly on each item
    • The bottleneck sometimes had nothing to work on
    • Items were blocked more often
    • Fewer requests arrived
  7. Little's Law: why less WIP means shorter lead timeThe simulator's result isn't luck. It follows from Little's Law, proved by John Little in 1961 for any stable queue.InteractiveHands-on
    Read this step

    The simulator's result isn't luck. It follows from Little's Law, proved by John Little in 1961 for any stable queue. Written the way Kanban teams use it:

    $$\text{average WIP} = \text{throughput} \times \text{average lead time}$$

    Rearranged for the number you usually care about:

    $$\text{average lead time} = \frac{\text{average WIP}}{\text{throughput}}$$

    If a team has 12 items in progress and finishes 2 a day, a new item will take about 12 ÷ 2 = 6 days on average. To make it 3 days without working any faster, the team has to hold only 6 items in progress.

    Three conditions keep it honest:

    • It is about averages over a period, not about one item.
    • The system should be stable: about as much work leaves as arrives, and WIP isn't climbing.
    • WIP and lead time must be measured between the same two points on the board, and in the same time unit as throughput.

    Try it: move the sliders. Keep throughput at 2 a day and halve the work in progress. What happens to lead time?

    Interactive · Little's Law: work in progress, throughput and lead time — try it in the lesson

    Takeaway: at the same throughput, lead time moves in step with WIP. Halve WIP, halve lead time.

  8. Little's Law at workUse average WIP = throughput × average lead time. Give each answer as a plain number in the unit the question asks for.Practice · 6 exercises
    Read this step

    Use average WIP = throughput × average lead time. Give each answer as a plain number in the unit the question asks for.

    A team has 12 items in progress on average and finishes 3 items a day. What is the average lead time, in days?

    A team's average lead time is 5 days and it finishes 2 items a day. How many items are in progress on average?

    A support team has 20 tickets open on average, and the average ticket takes 10 days to close. How many tickets does it close per day?

    A support team has 30 tickets open on average and closes 6 a day. It agrees to keep at most 18 open at once, and still closes 6 a day. What is the new average lead time, in days?

    A marketing team finishes 8 items a week, and an item takes 2.5 weeks on average. How many items are in progress on average?

    A team's average lead time is 10 days. It wants 5 days without finishing items any faster. What must happen to its average WIP?

    • Halve it
    • Double it
    • Keep it the same
    • Cut it by 5 items whatever it is now
  9. Lead time and cycle time: what you measureTeams use two words for "how long", and the definitions vary from book to book and tool to tool: Lead time in the Kanban Method means the time from the commitment point (the moment the team agrees to do an item) to the delivery point (when it reaches the…InteractiveHands-on
    Read this step

    Teams use two words for "how long", and the definitions vary from book to book and tool to tool:

    • Lead time in the Kanban Method means the time from the commitment point (the moment the team agrees to do an item) to the delivery point (when it reaches the customer). Many teams instead measure lead time from the customer's request to delivery, which is what the customer feels.
    • Cycle time usually means the time from starting work on an item to finishing it. The Kanban Guide (2020) defines cycle time as the time between when an item started and when it finished, and leaves each team to decide where "started" and "finished" are on its board.

    Neither is wrong. What matters is that your team picks its two points, writes them on the board and measures every item the same way.

    Try it: press each button and watch which part of one item's life it measures.

    Interactive · Lead time and cycle time on one card — try it in the lesson

    To get a number, note the day each card starts and the day it finishes. Here are five cards from a team's board. Work out the average cycle time as "finish day minus start day".

    Card Started on day Finished on day
    A 3 7
    B 4 10
    C 5 8
    D 7 12
    E 8 10

    Check your work · Paste the average cycle time of cards A to E, in days. — check it in the lesson

    Takeaway: say which two points you measure between, then measure every item the same way.

  10. Reading a cumulative flow diagramA cumulative flow diagram (CFD) shows a board over time. Each day, it stacks how many items have ever reached each column: Done at the bottom, then Test, Build, Analyse and Backlog.InteractiveHands-on
    Read this step

    A cumulative flow diagram (CFD) shows a board over time. Each day, it stacks how many items have ever reached each column: Done at the bottom, then Test, Build, Analyse and Backlog. Because items only move forward, each band's top edge can only rise or stay flat.

    How to read it:

    • Height of the middle bands on any day = the work in progress that day.
    • Horizontal distance from the top of Analyse to the top of Done = roughly how long items take from start to finish.
    • The slope of Done = throughput. Steeper is faster.
    • A band that keeps getting wider = work piles up in that column. That column, or the one after it, is your bottleneck.
    • Flat lines everywhere = nothing is moving: look for blockers.

    Try it: switch between the two boards from the simulator. Move the day slider and compare how tall the middle bands are and how far right you go before Done catches up.

    Interactive · A cumulative flow diagram, with and without WIP limits — try it in the lesson

    Without limits, the blue Build band swells to around 30 items and Done takes weeks to catch up with what was started. With limits, the middle bands stay thin and parallel: the sign of steady flow. The work waiting moves up into the grey Backlog band, before the commitment point.

    Takeaway: parallel bands mean steady flow; a widening band shows where work piles up.

Comments

You’ll sign in with Google before it’s posted.Comments are public — don’t name your students.
0 / 1,500

No comments yet. Be the first to say how it went.

Using it

Workshopy shares this lesson under CC BY 4.0. Anyone may use and change it, with credit to you. Anyone can learn it here, free. A copy in your workspace is yours to change and run live; your students never need an account.

Versions

  1. 2

    Version 2Current

    · A new Start here step with the lesson's scene; the cover is now a frame of the two boards you run in the lesson.

  2. 1

    Version 1

    · First published

Copies are made from the current version. A copy you already have doesn’t change.

More from Workshopy

All 78 lessons
All 14 Business lessons