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 |  Architecture Architecture Communication Canvas |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-30 min | 1-2 h | 60-120 min | 45-90 min |
Participantsdifferent | 2-6 | 3-10 | 2-8 | 2-5 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | Root causeIncidentLeanProblem solving | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas | LeanProblem solvingCoachingOperations |