View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Assumption SurfacingHypothesis-Driven TroubleshootingAlignment MappingBusiness Model Stress Test
| Criterion | ![]() Decision Making Assumption Surfacing | ![]() Engineering Hypothesis-Driven Troubleshooting | ![]() Facilitation Alignment Mapping | ![]() Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 45-90 min | 30-240 min | 1-2 h | Half day |
Participantsdifferent | 2-8 | 1-6 | 4-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Alignment Map, Open Issues, Decision Questions | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | TroubleshootingProblem solvingDiagnosis | AlignmentStakeholdersStrategyFacilitation | StrategyBusiness modelRiskDiagnosis |



