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 Discovery Assumption Mapping |  Decision Making Force Field 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked 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 | Medium | Medium | Low |
Timedifferent | 30-180 min | 45-60 min | 45-90 min |
Participantsdifferent | 1-6 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Assumption map, Test backlog, Risk ranking | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | TroubleshootingDiagnosisEngineering | AssumptionsRiskExperimentsValidation | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
