Turns workflows, data, causes, and improvements into a tangible result through defining the problem, asking why, and defining countermeasures.
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
Run sheet · visual · session plan
Details
Product StrategyCategory: Product Strategy. Describes the method's domain of use.
Turns target group, value, goals, and priorities into a tangible result by defining the problem, capturing customer segments, and prioritizing risks.
Core question: Which assumptions about problem, target group, and business model must be tested next before investing further?
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
Run sheet · visual · session plan
Details
OperationsCategory: Operations. Describes the method's domain of use.
Turns workflows, data, causes, and improvements into a tangible result by defining the problem, capturing the current state, and defining follow-up actions.
Core question: Which root cause behind the problem can be shifted with a testable countermeasure so that the target state is demonstrably reached?
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
Run sheet · visual · session plan
Details
OperationsCategory: Operations. Describes the method's domain of use.
Turns workflows, data, causes, and improvements into a tangible result by selecting a process, going to the place of work, and recording improvements.
Core question: Which gaps between standard work and real work become visible on site but do not appear in reports or dashboards?
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
Run sheet · visual · session plan
Details
OperationsCategory: Operations. Describes the method's domain of use.
Turns workflows, data, causes, and improvements into a tangible result by clarifying scope and goal, observing the current process, and setting the new standard and follow-up.
Core question: What concrete improvement in the defined process segment can the team implement and measure this week, and embed as a new standard?
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
Run sheet · visual · session plan
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: Which riskiest assumption does the team test in the next cycle with minimal effort, and what measurable behavior confirms or contradicts it?
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
Run sheet · visual · session plan
Details
OperationsCategory: Operations. Describes the method's domain of use.
Turns workflows, data, causes, and improvements into a tangible result by planning the problem and goal, applying a small change, and either standardizing or starting the next cycle.
Core question: Which hypothesis do we test in the next cycle, which metrics determine success, and which adjustment follows from the evaluation?
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
Run sheet · visual · session plan
Details
OperationsCategory: Operations. Describes the method's domain of use.
Turns workflows, data, causes, and improvements into a tangible result by collecting the current standard, observing actual work, and updating and training the standard.
Core question: Which steps of the examined process are actually standardized, where are unwanted deviations, and which variation is useful?
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
Run sheet · visual · session plan
Details
DeliveryCategory: Delivery. Describes the method's domain of use.
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?
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
Run sheet · visual · session plan
Details
OperationsCategory: Operations. Describes the method's domain of use.
Turns workflows, data, causes, and improvements into a tangible result by clarifying the process and value definition, observing or mapping the flow, and deriving improvements.
Core question: Which types of waste occur in the analyzed process with which frequency and effort?
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
Run sheet · visual · session plan
Details
AgileCategory: Agile. Describes the method's domain of use.
Turns backlog, sprint work, and team flow into a tangible result by defining the work queue, estimating cost of delay, and pulling highest value first.
Core question: Which item delivers the highest Cost-of-Delay value per effort and should be pulled next?
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.