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 |  Architecture Architecture Inception Canvas |
|---|---|---|---|---|
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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 15-30 min | 1-2 h | 2-8 h | 1-2 h |
Participantsdifferent | 2-6 | 3-10 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Root cause notes, Countermeasures | Architecture Canvas, Goals, Constraints, Quality Attributes | Problem Analysis, Decision Analysis, Risk Plan | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | Root causeIncidentLeanProblem solving | CanvasArchitectureAlignmentWorkshop | Problem solvingRoot causeDecisionOperations | AlignmentArchitectureCanvas |