View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hypothesis-Driven TroubleshootingAlignment MappingBusiness Model Stress TestStakeholder Mapping
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Alignment Mapping |  Business Strategy Business Model Stress Test |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
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 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 30-240 min | 1-2 h | Half day | 60–90 min |
Participantsdifferent | 1-6 | 4-12 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Alignment Map, Open Issues, Decision Questions | Stress Test Report, Action Plan per Scenario | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | AlignmentStakeholdersStrategyFacilitation | StrategyBusiness modelRiskDiagnosis | StakeholdersAlignmentFacilitationChange |