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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.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
MediumLowLow
Timedifferent
1-2 h20-60 min15-45 min
Participantsdifferent
3-121-41-3
Formatdifferent
WorkshopAsyncAsync
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsRunbook, Checklist, Escalation PathADR File, Decision Log, Rationale
Tagsno overlap
Systems thinkingTradeoffsLeadership
OperationsReliabilityDocumentation
ArchitectureRationaleDocumentationGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix