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 Starfish Retrospective 5 Whys

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Operations A3 Problem Solving	Agile Starfish Retrospective	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.	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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.	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	Medium	Low	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	45-90 min	45-90 min	15-30 min
Participantsdifferent	Designers, developers as users, and facilitation	2-5	4-12	2-6
Formatdifferent	Workshop + async	Workshop + async	Workshop	Workshop
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	Starfish Board, Practice Changes, Experiments	Root cause notes, Countermeasures
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	LeanProblem solvingCoachingOperations	RetrospectiveImprovementExperimentsTeam	Root causeIncidentLeanProblem solving

Add more methods