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)Assumption MappingSailboat RetrospectiveStart Stop Continue
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Assumption Mapping |  Agile Sailboat Retrospective |  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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 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 | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-60 min | 45-90 min | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption map, Test backlog, Risk ranking | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskExperimentsValidation | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection |