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 |  Facilitation Consensus Workshop |  Architecture arc42 |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-90 min | 1-3 h | 1-2 Tage | 1-2 h |
Participantsdifferent | 3-12 | 5-30 | 1-4 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Consensus Clusters, Theme Titles, Priority Areas | Architecture Document, Context View, Runtime View, Deployment View | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | FacilitationConsensusWorkshopAlignment | ArchitectureDocumentationCommunication | AlignmentStakeholdersStrategyFacilitation |