View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Operations Learning Review |  Agile Mad Sad Glad |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 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. | 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 | Low | Medium | Low | Low |
Timedifferent | 60-90 min | 1-3 h | 30-60 min | 20-45 min |
Participantsdifferent | 4-12 | 3-10 | 3-10 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Learning Review Notes, System Factors, Improvement Actions | Emotion Board, Themes, Action Items | Lessons learned, Action items, Event summary |
Tagsno overlap | RiskArchitectureWorkshopValidation | LearningRetrospectiveIncidentOperations | RetrospectiveTeamReflection | LearningOperationsImprovement |