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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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
LowLowMediumLow
Timedifferent
30 min Setup, dann laufend45-90 min1-3 h15-45 min
Participantsdifferent
1-3 maintaining, briefing for everyone2-81-81-3
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
RAID Log, Status Report SourceAssumption List, Critical Assumptions, Learning PlanArgument Map, Evidence Gaps, Decision RationaleADR File, Decision Log, Rationale
Tagsno overlap
RiskTrackingStakeholdersGovernance
AssumptionsRiskDecisionDiscovery
SensemakingDecisionRationale
ArchitectureRationaleDocumentationGovernance
Add more methods