View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Communication Canvas |  Operations 5 Whys |  Operations MORT Analysis |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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 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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 60-120 min | 15-30 min | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 2-8 | 2-6 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Root cause notes, Countermeasures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | Root causeIncidentLeanProblem solving | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |