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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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 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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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'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
30-60 min30 min Setup, dann laufend45–75 min30-60 min
Participantsdifferent
3-121-3 maintaining, briefing for everyoneTeam members involved3-10
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsRAID Log, Status Report Source4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveImprovementTeamReflection
RiskTrackingStakeholdersGovernance
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
Add more methods