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) |  Operations A3 Problem Solving |  Decision Making Constraint Analysis |
|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 30-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-5 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | A3 Report, Action Plan, Root Cause Analysis | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | LeanProblem solvingCoachingOperations | ConstraintsDecisionPlanningOptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
