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) |  Agile WSJF |  Decision Making Constraint Analysis |  Operations Getting Things Done |
|---|---|---|---|---|
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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 30-90 min | 1-2 h Setup, laufend |
Participantsdifferent | Designers, developers as users, and facilitation | 3-10 | 2-8 | 1 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Ranked Backlog, Cost-of-Delay Assumptions | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Action Lists, Project List, Review Routine |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | LeanEconomicsSequencePrioritization | ConstraintsDecisionPlanningOptions | ProductivityPlanningTasksExecution |