View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Process Mapping |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Theory of Constraints |
|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional | 2-4 h Analyse, laufend |
Participantsdifferent | 3-10 | Designers, developers as users, and facilitation | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | ProcessOperationsImprovement | ArchitectureEngineeringFeedbackValidationTasks | OperationsConstraintsFlowImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
