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 |  Facilitation Stakeholder Mapping |  Growth A/B Testing |  Facilitation Alignment 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 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. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 30-240 min | 60–90 min | 1-4 Wochen | 1-2 h |
Participantsdifferent | 1-6 | 2-8 | 1-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Stakeholder Map, Engagement Plan, Risk Notes | Experiment results, Decision log, Learning summary | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | StakeholdersAlignmentFacilitationChange | ExperimentsGrowthAnalyticsValidation | AlignmentStakeholdersStrategyFacilitation |