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)Learning ReviewStarfish RetrospectiveLearning Card
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Learning Review |  Agile Starfish Retrospective |  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. | 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 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 45-90 min | 25-40 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-10 | 4-12 | 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 | Learning Review Notes, System Factors, Improvement Actions | Starfish Board, Practice Changes, Experiments | Learning Card with evidence and next action |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementExperimentsTeam | ExperimentsValidationDiscoveryLearning |