View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Pre-Mortem |  Facilitation Stakeholder Mapping |  Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitysame | Low | Low | Low |
Timedifferent | 20–45 min | 60–90 min | 1-2 h |
Participantsdifferent | Small cross-functional group | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Stakeholder Map, Engagement Plan, Risk Notes | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RiskDecisionFailurePlanning | StakeholdersAlignmentFacilitationChange | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
