Kanban: Successful Evolutionary Change for Your Technology Business
Source: https://www.amazon.com/Kanban-Successful-Evolutionary-Technology-Business/dp/0984521402 ↗
Anderson's central claim is subtle: you do not adopt Kanban, you discover it by making your current work visible.
Start where you are, make WIP limits explicit, manage flow — and the process improves itself.
The virtue of the book is that it does not ask organisations to reorganise before they start; it asks them to look, which is much harder.
Reinertsen's queueing theory sits underneath, but Anderson gives you the operating manual.
For product direction it is a useful antidote to the cargo-cult of Scrum ceremonies — evolutionary change beats imposed change in most teams most of the time.
Central argument
Anderson argues that Kanban is not a methodology to be installed but a lens applied to existing work: by visualising the current process, setting explicit work-in-progress limits, and actively managing flow, teams trigger self-sustaining improvement without prior reorganisation. The central thesis is evolutionary over revolutionary change — start where you are, respect current roles and processes, and let constraints surface organically. Underpinning the operational advice is Reinertsen's queueing theory, which frames WIP accumulation as the root cause of lead-time variability rather than individual pace or effort.
Critique
The evolutionary premise — that organisations will genuinely respond to visibility and self-correct — assumes a baseline of psychological safety and management willingness to act on what the board reveals, neither of which Anderson adequately addresses. In practice, making queues visible can threaten managers whose authority depends on opacity, and the book offers little guidance for navigating that political reality. There is also a tension between Kanban's system-level focus on flow and the messy reality of product work, where demand is heterogeneous and 'done' is rarely binary — a tension the manufacturing-derived model handles less cleanly than it implies.
Why it matters for product
For a CPO managing multiple teams with entrenched delivery habits, Kanban's 'start where you are' principle is directly actionable: it removes the prerequisite of organisational consensus before improvement begins, which is the typical stalling point when pushing agile transitions from the top. WIP limits applied at the product level expose a specific and common failure mode — too many initiatives in parallel, each starved of attention — making the case for strategic focus in the language of flow rather than opinion. The explicit focus on lead time and throughput as primary metrics also gives product leaders a more honest signal of delivery health than velocity, which is easily gamed.