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 Root Cause Analysis |  Delivery Communication Plan |  Operations 5 Whys |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-4 h | 45-90 min | 15-30 min | 60-120 min |
Participantsdifferent | 3-8 | 2-6 | 2-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Communication Plan, Channel Matrix, Message Cadence | Root cause notes, Countermeasures | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Root causeProblem solvingQualityIncident | CommunicationStakeholdersDeliveryPlanning | Root causeIncidentLeanProblem solving | ArchitectureCommunicationStakeholdersCanvas |