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 Family Tree Analysis |  Architecture arc42 |  Operations Barrier Analysis |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | 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 | Medium | Medium |
Timedifferent | 2-4 h | 1-2 Tage | 2-4 h | 60-120 min |
Participantsdifferent | 2-6 | 1-4 | 2-6 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Architecture Document, Context View, Runtime View, Deployment View | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Root causePatternsIncidentSystemic | ArchitectureDocumentationCommunication | Root causeSafetyIncident | ArchitectureCommunicationStakeholdersCanvas |