View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Facilitation Stakeholder Salience Model |  Growth A/B Testing |
|---|---|---|---|
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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min | 1-4 Wochen |
Participantsdifferent | Designers, developers as users, and facilitation | 3-6 | 1-6 |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Salience Diagram, Strategy per Class | Experiment results, Decision log, Learning summary |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StakeholdersFacilitationAlignmentGovernance | ExperimentsGrowthAnalyticsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
