Condenses target group, problem, value proposition, and core assumptions into a lean picture for early product bets.
Core question: Which assumptions about problem, segment, solution, and economics must we test next?
CanvasMethod form: Canvas. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
45-90 min
1-6
Details
AgileCategory: Agile. Describes the method's domain of use.
Weighs work by business value, urgency, risk, and effort so that sequencing becomes economically justifiable.
Core question: Which job delivers the highest Cost of Delay divided by Job Size?
Decision methodMethod form: Decision method. Describes how this method is used in practice.HighComplexity: high. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
45-90 min
3-10
Details
DeliveryCategory: Delivery. Describes the method's domain of use.
Maps a service's path all the way to delivery and exposes wait times, waste, and bottlenecks.
Core question: How does one concrete work item move from request to delivery today?
Mapping toolMethod form: Mapping tool. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
1-3 h
4-10
Details
OperationsCategory: Operations. Describes the method's domain of use.
Asks its way step by step to a controllable cause and stops only once an effective countermeasure is within reach.
Core question: Which controllable cause behind the symptom can the team fix with a concrete countermeasure?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
15-30 min
2-6
Details
OperationsCategory: Operations. Describes the method's domain of use.
Condenses problem, analysis, countermeasures, and follow-up onto one sheet and forces joint analysis.
Core question: Which gap between current and target condition is evidenced, and which countermeasure will we test first?
Operating practiceMethod form: Operating practice. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
45-90 min
2-5
Details
OperationsCategory: Operations. Describes the method's domain of use.
Goes to the place where work happens, observes the process without disrupting it, and gathers solid clues about friction.
Core question: What is happening where work occurs, and which process question should we investigate together?
Operating practiceMethod form: Operating practice. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
30-120 min
2-6
Details
OperationsCategory: Operations. Describes the method's domain of use.
Runs changes as a repeatable cycle of Plan, Do, Check, and Act until a standard becomes solid.
Core question: Which small change will we test, what do we predict, what occurred, and how will learning enter the next cycle?
Process modelMethod form: Process model. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
1 h bis mehrere Wochen
1-8
Details
OperationsCategory: Operations. Describes the method's domain of use.
Bundles observation, waste analysis, and experiments into a compact improvement process with a new standard.
Core question: Which measurable process improvement can the frontline team implement, test, and standardise at the gemba within days?
Operating practiceMethod form: Operating practice. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
0.5-5 Tage
4-10
Details
OperationsCategory: Operations. Describes the method's domain of use.
Compares work as actually performed with the standard and reveals deviations that improve the process in a targeted way.
Core question: Which safe, quality-capable sequence meets customer takt with the minimum required standard WIP?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
1-3 h
2-6
Details
OperationsCategory: Operations. Describes the method's domain of use.
Identifies waste along a process, prioritizes impact, and derives improvements.
Core question: Which work creates customer value, which waste is immediately avoidable, which is currently necessary, and which unevenness or overburden produces it?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
45-120 min
2-8
Details
InnovationCategory: Innovation. Describes the method's domain of use.
Build Measure Learn cycles turn risky assumptions into experiments that support persevere, pivot, or stop decisions.
Core question: What smallest experiment creates decision-ready learning about the riskiest assumption?
Process modelMethod form: Process model. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
Wochen bis Monate je Lernzyklus
2-8
Details
ArchitectureCategory: Architecture. Describes the method's domain of use.
Helps a small team assess the main quality risks in its software and choose where to investigate further.
Core question: How well does our software meet its quality goals, and which risks should we investigate further?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
3–4 h for initial assessment; preparation and deeper analysis additional
1 or a small team; particularly suitable for 3–4 people