View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Business Strategy GAP Analysis |  Business Strategy Business Model Canvas |  Business Strategy Value Chain Analysis |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | The Business Model Canvas condenses a business model to its key building blocks and assumptions. It makes variants quickly comparable and reveals gaps before validation or implementation begins. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 30-240 min | 1-3 h | 1-2 h | Half day |
Participantsdifferent | 1-6 | 2-8 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Gap Matrix, Action Plan, Risk Notes | Business Model Canvas, Assumption List, Business Hypotheses | Value Chain Map, Lever List |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | StrategyAnalysisPlanning | Business modelStrategyValueInnovation | StrategyBusiness modelDiagnosisAnalysis |