View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy GAP Analysis |  Architecture ARID (Active Reviews for Intermediate Designs) |  Growth A/B Testing |  Product Strategy Counter Metrics |
|---|---|---|---|---|
Purposedifferent | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | 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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 Wochen | 30-60 min |
Participantsdifferent | 2-8 | Designers, developers as users, and facilitation | 1-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Experiment results, Decision log, Learning summary | Counter Metric List, Guardrail Definitions |
Tagsno overlap | StrategyAnalysisPlanning | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsGrowthAnalyticsValidation | MetricsMeasurementStrategyExperiments |