Kanban method
Kanban visualizes work, caps work in progress, and runs replenishment and service review cadences that continuously tune policy, covering Flow, Learning, and cross service Coordination, while never naming teams, executors, or incentives.
David J. Anderson, building on Taiichi Ohno's Toyota kanban system, c. 2007
The origin of the framework, as the directory records it. The mark grades the origin, not this page.
The directory entry this score was read from. Umbrex is a consultancy network; its summary is the reference, not a primary source.
Scored against the twelve cells, it loads three: Flow, Learning, and Coordination. The other nine it leaves to you. None of Composition, Evidence, or Mastery is among them, which is the usual result in this directory: the questions an agent in the loop raises first are the ones the literature answers least.
This is not a summary of the framework. Umbrex has one; the link under Sources goes there.
What limits throughput, and what is supposed to happen when the line stops?
How does tacit judgment become reusable, and who owns the loop that has to close?
What synchronizes the work when there is no room and half the team is not a person?