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 |  Architecture Architecture Inception Canvas |  Facilitation Stakeholder Mapping |  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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | Low | Low | Medium |
Timedifferent | 30-90 min | 1-2 h | 60–90 min | 1-2 h |
Participantsdifferent | 3-12 | 3-8 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Inception Canvas, Risks, Goal List, Open Questions | Stakeholder Map, Engagement Plan, Risk Notes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | AlignmentArchitectureCanvas | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersStrategyFacilitation |