View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Pre-Mortem |  Growth A/B Testing |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 20–45 min | 1-4 Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min |
Participantsdifferent | Small cross-functional group | 1-6 | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Experiment results, Decision log, Learning summary | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskDecisionFailurePlanning | ExperimentsGrowthAnalyticsValidation | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskDecisionDiscovery |