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 Starfish Retrospective | ![]() Product Discovery Experiment Canvas |
|---|---|---|---|
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 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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 4-12 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Starfish Board, Practice Changes, Experiments | Completed Experiment Canvas, Success Metric |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveImprovementExperimentsTeam | ExperimentsValidationDiscoveryHypothesis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






