methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration for DACI
Decision Making
DACI
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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
LowLowMediumLow
Timedifferent
20–45 min1-2 h45-90 min30-60 min
Participantsdifferent
Small cross-functional group3-103-122-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logArchitecture Canvas, Goals, Constraints, Quality AttributesRAPID Role Map, Recommendation, Decision LogDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
RiskDecisionFailurePlanning
CanvasArchitectureAlignmentWorkshop
DecisionRolesGovernance
DecisionRolesGovernanceAlignment
Add more methods