View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Kepner-Tregoe |  Operations A3 Problem Solving |  Architecture Software Architecture Canvas |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | High | Medium | Low | Low |
Timedifferent | 2-8 h | 45-90 min | 1-2 h | 15-30 min |
Participantsdifferent | 2-8 | 2-5 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Problem Analysis, Decision Analysis, Risk Plan | A3 Report, Action Plan, Root Cause Analysis | Architecture Canvas, Goals, Constraints, Quality Attributes | Root cause notes, Countermeasures |
Tagsno overlap | Problem solvingRoot causeDecisionOperations | LeanProblem solvingCoachingOperations | CanvasArchitectureAlignmentWorkshop | Root causeIncidentLeanProblem solving |