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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.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.
Complexitydifferent
MediumHighLow
Timedifferent
30-90 min2-6 h30-60 min
Participantsdifferent
3-123-103-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsStart Stop Continue Board, Improvement Actions
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
CausalityIncidentRoot causeTimeline
RetrospectiveImprovementTeamReflection
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 Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration for Learning Review.
Operations
Learning Review