View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Force Field Analysis |  Operations Failure Mode and Effects Analysis |  Operations After-Action Review |  Operations Fishbone Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 45-90 min | 2-6 h | 20-45 min | 30-60 min |
Participantsdifferent | 3-12 | 3-10 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | FMEA Table, Risk Priority, Mitigation Actions | Lessons learned, Action items, Event summary | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ChangeDecisionStrategy | RiskQualityOperationsRoot cause | LearningOperationsImprovement | Root causeQualityOperations |