View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Learning Review | ![]() Agile Example Mapping | ![]() Agile Three Amigos | ![]() Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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 | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 30-60 min | 15-30 min | 20-45 min |
Participantsdifferent | 3-10 | 3-7 | 3 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions | Lessons learned, Action items, Event summary |
Tagsno overlap | LearningRetrospectiveIncidentOperations | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement | LearningOperationsImprovement |



