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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
20–45 min30-90 min1-2 Tage30-90 min
Participantsdifferent
Small cross-functional group1-61-42-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logDecision Tree, Option Map, Assumption ListArchitecture Document, Context View, Runtime View, Deployment ViewConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
RiskDecisionFailurePlanning
DecisionTreeOptions
ArchitectureDocumentationCommunication
ConstraintsDecisionPlanningOptions
Add more methods