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 Theory of Constraints |  Operations After-Action Review |
|---|---|---|---|
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 system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 2-4 h Analyse, laufend | 20-45 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | 3-12 |
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 | Constraint Map, Improvement Plan, Flow Metrics | Lessons learned, Action items, Event summary |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | OperationsConstraintsFlowImprovement | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
