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 ARID (Active Reviews for Intermediate Designs) |  Agile 4Ls Retrospective |  Agile Mad Sad Glad |  Product Discovery Learning Card |
|---|---|---|---|---|
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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45–75 min | 30-60 min | 25-40 min |
Participantsdifferent | Designers, developers as users, and facilitation | Team members involved | 3-10 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | 4Ls Board, Learning Themes, Improvement Actions | Emotion Board, Themes, Action Items | Learning Card with evidence and next action |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveLearningReflectionTeam | RetrospectiveTeamReflection | ExperimentsValidationDiscoveryLearning |