View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Scenario AnalysisArchitecture Decision RecordC4 ModelArchitecture Communication Canvas
| Criterion | ![]() Engineering Failure Scenario Analysis | ![]() Architecture Architecture Decision Record | ![]() Architecture C4 Model | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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-3 h | 15-45 min | 1-4 h | 60-120 min |
Participantsdifferent | 3-8 | 1-3 | 1-5 | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | FailureResilienceRisk | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | ArchitectureCommunicationStakeholdersCanvas |



