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 MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
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.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
HighLowMedium
Timedifferent
Mehrere Tage bis Wochen45-90 min2-4 h
Participantsdifferent
2-64-122-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
MORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsStarfish Board, Practice Changes, ExperimentsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Root causeSafetySystemicIncident
RetrospectiveImprovementExperimentsTeam
Root causeSafetyIncident
Add more methods

Often compared together

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

Paper illustration of Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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