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)Sailboat RetrospectiveA/B TestingStart Stop Continue
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Sailboat Retrospective |  Growth A/B Testing |  Agile Start Stop Continue |
|---|---|---|---|---|
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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 1-4 Wochen | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 4-12 | 1-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Sailboat Board, Risks, Improvement Actions | Experiment results, Decision log, Learning summary | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveTeamImprovement | ExperimentsGrowthAnalyticsValidation | RetrospectiveImprovementTeamReflection |