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 |  Decision Making Constraint Analysis |  Architecture Software Architecture Canvas |  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. | 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. | 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. | 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 | 30-90 min | 1-2 h | 60-90 min |
Participantsdifferent | Small cross-functional group | 2-8 | 3-10 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Architecture Canvas, Goals, Constraints, Quality Attributes | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RiskDecisionFailurePlanning | ConstraintsDecisionPlanningOptions | CanvasArchitectureAlignmentWorkshop | RiskArchitectureWorkshopValidation |