View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Mad Sad GladAfter-Action ReviewSailboat Retrospective
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Mad Sad Glad |  Operations After-Action Review |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min | 20-45 min | 45-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-10 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Emotion Board, Themes, Action Items | Lessons learned, Action items, Event summary | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveTeamReflection | LearningOperationsImprovement | RetrospectiveTeamImprovement |