Compare

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)Starfish Retrospective Test Card Hypothesis Prioritization Canvas

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Agile Starfish Retrospective	Product Discovery Test Card	Product Discovery Hypothesis Prioritization 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.	The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success.	When many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog.
Complexitydifferent	Medium	Low	Low	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	45-90 min	20-35 min	60-90 min
Participantsdifferent	Designers, developers as users, and facilitation	4-12	1-5	3-8
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Starfish Board, Practice Changes, Experiments	Test Card with a pre-set threshold	Prioritization Canvas, Hypothesis Backlog
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	RetrospectiveImprovementExperimentsTeam	ExperimentsValidationDiscoveryHypothesis	ExperimentsPrioritizationDiscoveryHypothesis

Add more methods