View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile WSJF |  Architecture ARID (Active Reviews for Intermediate Designs) |  Facilitation Consensus Workshop |  Facilitation Dot Voting |
|---|---|---|---|---|
Purposedifferent | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 45-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 5-15 min |
Participantsdifferent | 3-10 | Designers, developers as users, and facilitation | 5-30 | 3-20 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Consensus Clusters, Theme Titles, Priority Areas | Ranked list, Consensus signal, Shortlist |
Tagsno overlap | LeanEconomicsSequencePrioritization | ArchitectureEngineeringFeedbackValidationTasks | FacilitationConsensusWorkshopAlignment | FacilitationVotingConsensusPrioritization |