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
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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
Purposedifferent
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.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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent
LowMediumLowLow
Timedifferent
OngoingAs needed30-60 min45–75 min
Participantsdifferent
1-204-153-10Team members involved
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Visual Board, Status Indicators, Exception CuesIncident Log, Action Tracker, Stakeholder UpdatesEmotion Board, Themes, Action Items4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
SignalsOperationsVisual management
IncidentOperationsReliability
RetrospectiveTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods