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 | ![]() Architecture Architecture Decision Record | ![]() Operations A3 Problem Solving | ![]() Operations 5 Whys |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-60 min | 15-45 min | 45-90 min | 15-30 min |
Participantsdifferent | 2-10 | 1-3 | 2-5 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Iceberg Worksheet, Pattern Notes, Intervention Ideas | ADR File, Decision Log, Rationale | A3 Report, Action Plan, Root Cause Analysis | Root cause notes, Countermeasures |
Tagsno overlap | Systems thinkingRoot causePatterns | ArchitectureRationaleDocumentationGovernance | LeanProblem solvingCoachingOperations | Root causeIncidentLeanProblem solving |



