View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Assumption Mapping |  Product Strategy Counter Metrics |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 45-60 min | 30-60 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 2-8 | 2-6 | Designers, developers as users, and facilitation |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Assumption map, Test backlog, Risk ranking | Counter Metric List, Guardrail Definitions | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | AssumptionsRiskExperimentsValidation | MetricsMeasurementStrategyExperiments | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
