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 Constraint Analysis |  Delivery Communication Plan |  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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 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 | 30-90 min | 45-90 min | 60-120 min |
Participantsdifferent | 3-12 | 2-8 | 2-6 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Communication Plan, Channel Matrix, Message Cadence | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | ConstraintsDecisionPlanningOptions | CommunicationStakeholdersDeliveryPlanning | ArchitectureCommunicationStakeholdersCanvas |