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 of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception 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.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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
20–45 min1-2 h45-60 min1-2 h
Participantsdifferent
Small cross-functional group3-102-83-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Risk list, Mitigation plan, Assumption logArchitecture Canvas, Goals, Constraints, Quality AttributesAssumption map, Test backlog, Risk rankingInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
RiskDecisionFailurePlanning
CanvasArchitectureAlignmentWorkshop
AssumptionsRiskExperimentsValidation
AlignmentArchitectureCanvas
Add more methods