Turns technical problems, hypotheses, and next steps into a tangible result by clarifying the symptom and system boundaries, breaking the fault space into areas, and narrowing the affected area.
Core question: Which system area most likely causes the symptom, and which tests narrow the fault domain 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.
30-180 min
1-6
Run sheet · visual · session plan
Details
EngineeringCategory: Engineering. Describes the method's domain of use.
Turns technical problems, hypotheses, and next steps into a tangible result by collecting symptoms, formulating hypotheses, and refining them through testing.
Core question: Which hypothesis best explains the symptom, and which test delivers the highest information value?
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.
30-240 min
1-6
Run sheet · visual · session plan
Details
Business StrategyCategory: Business Strategy. Describes the method's domain of use.
Moves the current situation, opportunities, and strategic options toward a concrete result through "explain the nine-activity template", "describe primary activities", and "derive levers and weaknesses".
Core question: Which activities in our value creation are competitive advantage today, which cost without differentiation, and where are the strategic levers?
Mapping toolMethod form: Mapping tool. 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.
Half day
3-8
Run sheet · visual · session plan
Details
Business StrategyCategory: Business Strategy. Describes the method's domain of use.
Moves the current situation, opportunities, and strategic options toward a concrete result through "place the Business Model Canvas at the center", "define two to three scenarios", and "derive actions per scenario".
Core question: Which parts of the business model hold up across different scenarios, and which actions should follow from the weak spots?
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.
Half day
3-8
Run sheet · visual · session plan
Details
Business StrategyCategory: Business Strategy. Describes the method's domain of use.
Moves the current situation, opportunities, and strategic options toward a concrete result through "collect resources and capabilities", "answer question V for each resource", and "derive strategic actions".
Core question: Which of our resources are sources of sustainable competitive advantage, and which are only parity or even weakness?
Decision methodMethod form: Decision 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.
90-180 min
3-6
Run sheet · visual · session plan
Details
Team DesignCategory: Team Design. Describes the method's domain of use.
Moves team boundaries, interfaces, and collaboration toward a concrete result through "explain the scale and categories", "run an anonymous team survey", and "derive and track actions".
Core question: How high is our team's cognitive load in three categories, and which structural measures reduce it?
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.
60-90 min
3-12
Run sheet · visual · session plan
Details
Team DesignCategory: Team Design. Describes the method's domain of use.
Moves team boundaries, interfaces, and collaboration toward a concrete result through "prepare a template with the four structures", "place current teams as squads", and "derive actions".
Core question: How is our engineering org actually structured into squads, tribes, chapters and guilds, and where do friction or gaps emerge?
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.
90-180 min
5-15
Run sheet · visual · session plan
Details
Systems ThinkingCategory: Systems Thinking. Describes the method's domain of use.
Moves relationships, patterns, and leverage toward a concrete result through "formulate current observations", "introduce archetype cards", and "discuss leverage and derive actions".
Core question: Which archetype best explains recurring symptoms, and which levers are typical for this archetype?
Mapping toolMethod form: Mapping tool. 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.