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 |  Architecture Software Architecture Canvas |  Decision Making Assumption Surfacing |  Architecture Risk Storming |
|---|---|---|---|---|
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. | 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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20–45 min | 1-2 h | 45-90 min | 60-90 min |
Participantsdifferent | Small cross-functional group | 3-10 | 2-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Architecture Canvas, Goals, Constraints, Quality Attributes | Assumption List, Critical Assumptions, Learning Plan | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RiskDecisionFailurePlanning | CanvasArchitectureAlignmentWorkshop | AssumptionsRiskDecisionDiscovery | RiskArchitectureWorkshopValidation |