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 team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
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 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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.
Complexitydifferent
LowLowMedium
Timedifferent
30-60 min20-45 minAs needed
Participantsdifferent
3-123-124-15
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Start Stop Continue Board, Improvement ActionsLessons learned, Action items, Event summaryIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
RetrospectiveImprovementTeamReflection
LearningOperationsImprovement
IncidentOperationsReliability
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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 Learning Review.
Operations
Learning Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem