View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Mad Sad Glad |  Architecture arc42 |  Operations After-Action Review |  Operations Learning Review |
|---|---|---|---|---|
Purposedifferent | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. | 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. | 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. | 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 | Low | Low | Low | Medium |
Timedifferent | 30-60 min | 1-2 Tage | 20-45 min | 1-3 h |
Participantsdifferent | 3-10 | 1-4 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | Architecture Document, Context View, Runtime View, Deployment View | Lessons learned, Action items, Event summary | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | RetrospectiveTeamReflection | ArchitectureDocumentationCommunication | LearningOperationsImprovement | LearningRetrospectiveIncidentOperations |