(Select 3) What are the primary reasons to limit WIP?

Question

Options

• AReduce multiplexing
• BDecrease wait times
• CExpand context switching
• DMake it easier to visualize the important work
• EIncrease throughput

• A
  89% (34)
• C
  3% (1)
• D
  8% (3)

Explanation

Limiting WIP (Work in Progress) is a core Lean/Kanban principle that improves flow efficiency. Reducing multiplexing (A) means fewer items compete for the same resources at once, preventing teams from spreading effort too thin. Decreasing wait times (B) follows directly from Little's Law: WIP = Throughput × Cycle Time - less WIP in the system means items spend less time sitting in queues. Increasing throughput (E) results because focused teams complete items faster when they aren't constantly splitting attention across many tasks.

C (Expand context switching) is wrong - it's the opposite effect; limiting WIP reduces context switching, which is a key benefit. D (Visualize important work) is a benefit of a Kanban board itself, not specifically of WIP limits - visualization and WIP limits are related practices but distinct purposes.

Memory tip: Think of WIP limits as a traffic control system - fewer cars on the road (less multiplexing) means shorter travel times (less wait) and more cars reaching their destination per hour (higher throughput). Option C is a trap word ("expand" sounds good but is the wrong direction), and D confuses the board with the limit.

No community discussion yet for this question.