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 an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Risk Storming.
Architecture
Risk Storming
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
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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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
45-90 min60-90 min1-3 h15-45 min
Participantsdifferent
2-84-121-81-3
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanAnnotated Diagram, Prioritized Risk List, Action BacklogArgument Map, Evidence Gaps, Decision RationaleADR File, Decision Log, Rationale
Tagsno overlap
AssumptionsRiskDecisionDiscovery
RiskArchitectureWorkshopValidation
SensemakingDecisionRationale
ArchitectureRationaleDocumentationGovernance
Add more methods