View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy DIBB |  Engineering Fault Isolation |  Facilitation Stakeholder Mapping |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-2 h | 30-180 min | 60–90 min | 45-90 min |
Participantsdifferent | 2-8 | 1-6 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | DIBB document, Belief list, Bet list, Learning report | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Stakeholder Map, Engagement Plan, Risk Notes | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | StrategyDecisionAssumptionsHypothesis | TroubleshootingDiagnosisEngineering | StakeholdersAlignmentFacilitationChange | ChangeDecisionStrategy |