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 Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
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.For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.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
LowMediumLow
Timedifferent
30-60 min60-180 min30-60 min
Participantsdifferent
3-123-103-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveImprovementTeamReflection
IncidentTimelineSite Reliability Engineering
RetrospectiveTeamReflection
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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 Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem