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 |  Product Discovery Fake Door Test |  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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | 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 | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45–75 min | 1-5 Tage | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | Team members involved | Nutzertraffic | 3-10 |
Formatdifferent | Workshop + async | Workshop | Async | 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 | Click Data, Interest Signal, Learning Decision | Emotion Board, Themes, Action Items |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveLearningReflectionTeam | ValidationExperimentsDemandDiscovery | RetrospectiveTeamReflection |