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)Assumption SurfacingTest CardAssumption Mapping
| Criterion | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Decision Making Assumption Surfacing | ![]() Product Discovery Test Card | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 20-35 min | 45-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 1-5 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption List, Critical Assumptions, Learning Plan | Test Card with a pre-set threshold | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskDecisionDiscovery | ExperimentsValidationDiscoveryHypothesis | AssumptionsRiskExperimentsValidation |



