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 5 Whys |  Architecture Software Architecture Canvas |  Operations Kepner-Tregoe |  Facilitation Decision Jam |
|---|---|---|---|---|
Purposedifferent | 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. | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 15-30 min | 1-2 h | 2-8 h | 60-90 min |
Participantsdifferent | 2-6 | 3-10 | 2-8 | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Root cause notes, Countermeasures | Architecture Canvas, Goals, Constraints, Quality Attributes | Problem Analysis, Decision Analysis, Risk Plan | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | Root causeIncidentLeanProblem solving | CanvasArchitectureAlignmentWorkshop | Problem solvingRoot causeDecisionOperations | FacilitationDecisionProblem solvingWorkshop |