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)A3 Problem Solving Affinity Diagramming Kepner-Tregoe

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Operations A3 Problem Solving	UX Research Affinity Diagramming	Operations Kepner-Tregoe
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.	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.	When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.	For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.
Complexitydifferent	Medium	Medium	Low	High
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	45-90 min	45–90 min	2-8 h
Participantsdifferent	Designers, developers as users, and facilitation	2-5	3-10	2-8
Formatdifferent	Workshop + async	Workshop + async	Workshop	Workshop + async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	A3 Report, Action Plan, Root Cause Analysis	Theme clusters, Insight statements, Opportunity areas	Problem Analysis, Decision Analysis, Risk Plan
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	LeanProblem solvingCoachingOperations	SynthesisQualitativeRoot cause	Problem solvingRoot causeDecisionOperations

Add more methods