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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.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.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.
Complexitydifferent
LowHighLowMedium
Timedifferent
20-60 min0.5-3 Tage15-45 min1-3 h
Participantsdifferent
1-45-151-31-8
Formatdifferent
AsyncWorkshopAsyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathRich Picture, Root Definitions, Conceptual Models, Change AgendaADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
OperationsReliabilityDocumentation
Soft systemsComplexitySensemakingSystems thinking
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
Add more methods