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
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.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.
Complexitydifferent
MediumLowLow
Timedifferent
As neededOngoing30-60 min
Participantsdifferent
4-151-203-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesVisual Board, Status Indicators, Exception CuesEmotion Board, Themes, Action Items
Tagsno overlap
IncidentOperationsReliability
SignalsOperationsVisual management
RetrospectiveTeamReflection
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