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 hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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 for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.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.
Complexitysame
LowLowLowLow
Timedifferent
20–45 min45–75 min30-60 min30-60 min
Participantsdifferent
Small cross-functional groupTeam members involved3-123-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Risk list, Mitigation plan, Assumption log4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
RiskDecisionFailurePlanning
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods