View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Engineering Failure Scenario Analysis | ![]() Architecture Architecture Communication Canvas | ![]() Delivery Communication Plan | ![]() Architecture C4 Model |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 60-120 min | 45-90 min | 1-4 h |
Participantsdifferent | 3-8 | 2-8 | 2-6 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Communication Plan, Channel Matrix, Message Cadence | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | FailureResilienceRisk | ArchitectureCommunicationStakeholdersCanvas | CommunicationStakeholdersDeliveryPlanning | ArchitectureCommunicationVisualization |



