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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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 Sailboat Retrospective
Agile
Sailboat Retrospective
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Purposedifferent
For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
HighLowLowLow
Timedifferent
2-6 h30-60 min45-90 min30-60 min
Participantsdifferent
3-103-124-122-8
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
FMEA Table, Risk Priority, Mitigation ActionsStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement ActionsFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
RiskQualityOperationsRoot cause
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Root causeQualityOperations
Add more methods