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)4Ls RetrospectiveStarfish RetrospectiveMad Sad Glad
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile 4Ls Retrospective |  Agile Starfish Retrospective |  Agile Mad Sad Glad |
|---|---|---|---|---|
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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45–75 min | 45-90 min | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | Team members involved | 4-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | 4Ls Board, Learning Themes, Improvement Actions | Starfish Board, Practice Changes, Experiments | Emotion Board, Themes, Action Items |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamReflection |