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
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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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.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.For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.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
LowLowHighLow
Timedifferent
45–75 min30-60 minMehrere Tage bis Wochen30-60 min
Participantsdifferent
Team members involved3-122-63-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement ActionsMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
Root causeSafetySystemicIncident
RetrospectiveTeamReflection
Add more methods