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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Learning Review.
Operations
Learning Review
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30-60 min1-3 hAs needed30-60 min
Participantsdifferent
3-123-104-153-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsLearning Review Notes, System Factors, Improvement ActionsIncident Log, Action Tracker, Stakeholder UpdatesEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveImprovementTeamReflection
LearningRetrospectiveIncidentOperations
IncidentOperationsReliability
RetrospectiveTeamReflection
Add more methods