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 |  Architecture arc42 |  Agile Sailboat Retrospective |  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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | 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 | 1-2 Tage | 45-90 min | 20-45 min |
Participantsdifferent | 3-10 | 1-4 | 4-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | Architecture Document, Context View, Runtime View, Deployment View | Sailboat Board, Risks, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | LearningRetrospectiveIncidentOperations | ArchitectureDocumentationCommunication | RetrospectiveTeamImprovement | LearningOperationsImprovement |