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 for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Purposedifferent
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.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.
Complexitydifferent
LowMedium
Timedifferent
30-60 min60-180 min
Participantssame
3-103-10
Formatdifferent
WorkshopWorkshop + async
Outputdifferent
Emotion Board, Themes, Action ItemsIncident Timeline, Evidence Log, Delay Analysis, Improvement Actions
Tagsno overlap
RetrospectiveTeamReflection
IncidentTimelineSite Reliability Engineering
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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis