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
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
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.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
LowLowMediumLow
Timedifferent
30-60 min20-45 minAs needed30-60 min
Participantsdifferent
3-101-84-153-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Emotion Board, Themes, Action ItemsOwnership Reflection, Action Commitment, Coaching NotesIncident Log, Action Tracker, Stakeholder UpdatesStart Stop Continue Board, Improvement Actions
Tagsno overlap
RetrospectiveTeamReflection
ResponsibilityLeadershipTeam
IncidentOperationsReliability
RetrospectiveImprovementTeamReflection
Add more methods