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 Start Stop Continue Starfish Retrospective

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Operations A3 Problem Solving	Agile Start Stop Continue	Agile Starfish Retrospective
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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.	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.
Complexitydifferent	Medium	Medium	Low	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	45-90 min	30-60 min	45-90 min
Participantsdifferent	Designers, developers as users, and facilitation	2-5	3-12	4-12
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	Start Stop Continue Board, Improvement Actions	Starfish Board, Practice Changes, Experiments
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	LeanProblem solvingCoachingOperations	RetrospectiveImprovementTeamReflection	RetrospectiveImprovementExperimentsTeam

Add more methods