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 of a SWOT matrix with four separated quadrants and marked strategic options.
Business Strategy
SWOT Analysis
Paper illustration for Learning Review.
Operations
Learning Review
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.SWOT Analysis arranges strengths, weaknesses, opportunities, and threats into a compact picture of the situation. It keeps internal capabilities and external influences separate before strategic options emerge from them.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
LowLowMedium
Timedifferent
20-60 min30-60 min1-3 h
Participantsdifferent
1-43-123-10
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathSWOT matrix, Strategic options, Action listLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
OperationsReliabilityDocumentation
StrategyAnalysisMarketPositioning
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a six-field PESTLE grid
Business Strategy
PESTLE Analysis
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective