View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Dot VotingARID (Active Reviews for Intermediate Designs)LASR (Lightweight Approach for Software Reviews)Nominal Group Technique
| Criterion |  Facilitation Dot Voting |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Nominal Group Technique |
|---|---|---|---|---|
Purposedifferent | When a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | When loud voices could dominate a round, Nominal Group Technique protects individual thinking time from group effects. It collects ideas separately first and only then enables shared weighting. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 5-15 min | 2–4 h review as a planning range; preparation and evaluation additional | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-120 min |
Participantsdifferent | 3-20 | Designers, developers as users, and facilitation | 1 or a small team; particularly suitable for 3–4 people | 5-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Ranked list, Consensus signal, Shortlist | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Ranked Ideas, Clarified Options, Group Priority |
Tagsno overlap | FacilitationVotingConsensusPrioritization | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskAssessmentLean | FacilitationPrioritizationVotingInclusion |