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 a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
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
Purposedifferent
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.For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
20-45 minOngoing30-60 min45-90 min
Participantsdifferent
3-122-203-124-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Lessons learned, Action items, Event summaryChat Transcript, Action Log, AutomationsStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
LearningOperationsImprovement
CollaborationEngineeringIncident
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Add more methods