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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.
Complexitydifferent
LowLowMediumLow
Timedifferent
30-60 min30-60 min1-3 h20-45 min
Participantsdifferent
2-83-123-103-12
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Fishbone Diagram, Cause Categories, Investigation BacklogStart Stop Continue Board, Improvement ActionsLearning Review Notes, System Factors, Improvement ActionsLessons learned, Action items, Event summary
Tagsno overlap
Root causeQualityOperations
RetrospectiveImprovementTeamReflection
LearningRetrospectiveIncidentOperations
LearningOperationsImprovement
Add more methods