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 8D Problem Solving.
Operations
8D Problem Solving
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 Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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.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
HighLowLowHigh
Timedifferent
1-6 Wochen45–75 min30-60 min2-6 h
Participantsdifferent
4-10Team members involved3-103-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action ItemsFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
QualityProblem solvingRoot cause
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
RiskQualityOperationsRoot cause
Add more methods