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 |  Agile Start Stop Continue |  Operations Process Mapping |
|---|---|---|---|---|
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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-120 min | 30-60 min | 1-3 h |
Participantsdifferent | Designers, developers as users, and facilitation | 2-6 | 3-12 | 3-10 |
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 | Start Stop Continue Board, Improvement Actions | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | LeanObservationProcessOperations | RetrospectiveImprovementTeamReflection | ProcessOperationsImprovement |