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 Fault Isolation |  Product Strategy Impact Mapping |  Decision Making Force Field Analysis |  Decision Making Constraint Analysis |
|---|---|---|---|---|
Purposedifferent | 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 a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-180 min | 45-90 min | 45-90 min | 30-90 min |
Participantsdifferent | 1-6 | 3-8 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Impact Map, Outcome Hypotheses, Delivery Options | Force Field Map, Change Levers, Risk Notes | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | TroubleshootingDiagnosisEngineering | OutcomesStrategyBehaviorPlanning | ChangeDecisionStrategy | ConstraintsDecisionPlanningOptions |