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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.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.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 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.
Complexitydifferent
LowLowLowHigh
Timedifferent
30-60 min30-60 min30-60 min2-6 h
Participantsdifferent
2-83-103-123-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Fishbone Diagram, Cause Categories, Investigation BacklogEmotion Board, Themes, Action ItemsStart Stop Continue Board, Improvement ActionsFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Root causeQualityOperations
RetrospectiveTeamReflection
RetrospectiveImprovementTeamReflection
RiskQualityOperationsRoot cause
Add more methods