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
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Paper illustration for Learning Review.
Operations
Learning Review
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.When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.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.
Complexitydifferent
LowLowMedium
Timedifferent
20-45 min30-60 min1-3 h
Participantsdifferent
3-123-73-10
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Lessons learned, Action items, Event summaryExample Map, Acceptance Criteria, Open QuestionsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
LearningOperationsImprovement
Behavior-Driven DevelopmentRequirementsExamplesRefinement
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
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