View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Iceberg Model |  Operations A3 Problem Solving |  DevOps Incident Command |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30-60 min | 45-90 min | As needed | 1-4 h |
Participantsdifferent | 2-10 | 2-5 | 4-15 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Iceberg Worksheet, Pattern Notes, Intervention Ideas | A3 Report, Action Plan, Root Cause Analysis | Incident Log, Action Tracker, Stakeholder Updates | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | Systems thinkingRoot causePatterns | LeanProblem solvingCoachingOperations | IncidentOperationsReliability | Root causeProblem solvingQualityIncident |