View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() DevOps Blameless Postmortem | ![]() Decision Making Assumption Surfacing | ![]() Architecture arc42 | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. | 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 | 30-90 min | 45-90 min | 1-2 Tage | 60-120 min |
Participantsdifferent | 3-12 | 2-8 | 1-4 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Assumption List, Critical Assumptions, Learning Plan | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | AssumptionsRiskDecisionDiscovery | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas |



