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 Gemba Walk |  Facilitation Decision Jam |  Operations 5 Whys |
|---|---|---|---|---|
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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-120 min | 60-90 min | 15-30 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-6 | 4-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Observation Notes, Improvement Ideas | Problem Cluster, Prioritized Challenge, Experiment | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | LeanObservationProcessOperations | FacilitationDecisionProblem solvingWorkshop | Root causeIncidentLeanProblem solving |