Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:ARID (Active Reviews for Intermediate Designs)Gemba Walk Goal Question Metric A3 Problem Solving

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Operations Gemba Walk	Engineering Goal Question Metric	Operations A3 Problem Solving
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.	Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.	For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.
Complexitydifferent	Medium	Low	Medium	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	30-120 min	90-180 min	45-90 min
Participantsdifferent	Designers, developers as users, and facilitation	2-6	3-6	2-5
Formatdifferent	Workshop + async	Workshop	Workshop	Workshop + async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Observation Notes, Improvement Ideas	GQM Table, Metric Profiles	A3 Report, Action Plan, Root Cause Analysis
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	LeanObservationProcessOperations	MetricsMeasurementEngineeringAlignment	LeanProblem solvingCoachingOperations

Add more methods