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 Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
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 a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.
Complexitydifferent
LowMediumHigh
Timedifferent
30-60 min2-4 hMehrere Tage bis Wochen
Participantsdifferent
3-122-62-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Start Stop Continue Board, Improvement ActionsFamily Tree Diagram, Pattern Notes, Systemic MeasuresMORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations
Tagsno overlap
RetrospectiveImprovementTeamReflection
Root causePatternsIncidentSystemic
Root causeSafetySystemicIncident
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 Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective