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
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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
When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.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.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.
Complexitysame
LowLowLowLow
Timedifferent
5-20 min20–45 min1-2 Tage15-45 min
Participantsdifferent
3-20Small cross-functional group1-41-3
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsRisk list, Mitigation plan, Assumption logArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
EstimationEffortRisk
RiskDecisionFailurePlanning
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods