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 Risk Storming |  Operations Gemba Walk |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 60-90 min | 30-120 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 3-10 | 4-12 | 2-6 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Annotated Diagram, Prioritized Risk List, Action Backlog | Observation Notes, Improvement Ideas | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ProcessOperationsImprovement | RiskArchitectureWorkshopValidation | LeanObservationProcessOperations | ArchitectureEngineeringFeedbackValidationTasks |