Method Catalog
Decide faster which method fits right now.
288 Methods20 Categories12 Method forms
Favorites
Favorites are stored locally in the browser and appear through the favorites filter in the catalog.
288 Methods20 Categories12 Method forms
Favorites are stored locally in the browser and appear through the favorites filter in the catalog.
Turns technical problems, assumptions, and next steps into a tangible result through mapping the workflow, making work visible, and improving bottlenecks.
Core question: How does work flow through the stages, where does it queue up, and which policy keeps WIP limits intact?
Turns workflows, data, causes, and improvements into a tangible result by clarifying the system goal, identifying the bottleneck, and repeating the cycle after expansion.
Core question: Which process step currently limits overall throughput, how can this constraint be exploited to the maximum, and which escalation level (exploit, subordinate, elevate) is next?
Turns scope, sequence, and delivery flow into a tangible result through selecting a value stream, mapping current state, and designing a future state.
Core question: Where do waiting time, rework, and waste emerge between trigger and delivery, and which two or three interventions improve lead time most?
Turns workflows, data, causes, and improvements into a tangible result by mapping the process flow, measuring waiting time and WIP, and re-evaluating the bottleneck after changes.
Core question: Where does work accumulate in the process, which step limits overall throughput, and which escalation level, utilization, subordination, or elevation, is the next effective move?
Moves scope, sequence, and delivery flow toward a concrete result through "formulate the forecast question", "choose historical flow data", and "update the forecast regularly".
Core question: With what probability will the desired scope be finished by the target date (or how much scope can we complete by then), and which assumptions drive the distribution?
Moves backlog, sprint work, and team flow toward a concrete result through "clarify the planning question", "slice work smaller", and "calibrate regularly with reality".
Core question: Which planning decision do we need to make, and which flow data or slicing rules answer it more cheaply than an estimation ritual?