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 |  Innovation Contradiction Analysis |  Business Strategy Business Model Canvas |
|---|---|---|---|
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. | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 30-240 min | 60-120 min | 1-2 h |
Participantsdifferent | 1-6 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Business Model Canvas, Assumption List, Business Hypotheses |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ContradictionsInnovationProblem solving | Business modelStrategyValueInnovation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
