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
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
LowHighLowLow
Timedifferent
20–45 min90-180 min1-2 Tage15-45 min
Participantsdifferent
Small cross-functional group3-81-41-3
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logCoD Table, Prioritization SequenceArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
RiskDecisionFailurePlanning
PrioritizationDeliveryEconomicsDecision
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods