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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
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.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.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
MediumLowLow
Timedifferent
As needed30-60 min45-90 min
Participantsdifferent
4-153-104-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesEmotion Board, Themes, Action ItemsSailboat Board, Risks, Improvement Actions
Tagsno overlap
IncidentOperationsReliability
RetrospectiveTeamReflection
RetrospectiveTeamImprovement
Add more methods

Often compared together

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

Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 for Starfish Retrospective
Agile
Starfish Retrospective