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 Mad Sad Glad
Agile
Mad Sad Glad
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.
Complexitydifferent
LowLowMedium
Timedifferent
20-60 min30-60 minAs needed
Participantsdifferent
1-43-104-15
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathEmotion Board, Themes, Action ItemsIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
OperationsReliabilityDocumentation
RetrospectiveTeamReflection
IncidentOperationsReliability
Add more methods

Often compared together

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

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
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem