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)Process Mapping Starfish Retrospective Sailboat Retrospective

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Operations Process Mapping	Agile Starfish Retrospective	Agile Sailboat 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.	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.	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.	When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent	Medium	Medium	Low	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	1-3 h	45-90 min	45-90 min
Participantsdifferent	Designers, developers as users, and facilitation	3-10	4-12	4-12
Formatdifferent	Workshop + async	Workshop	Workshop	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Process Map, Handoff List, Improvement Backlog	Starfish Board, Practice Changes, Experiments	Sailboat Board, Risks, Improvement Actions
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	ProcessOperationsImprovement	RetrospectiveImprovementExperimentsTeam	RetrospectiveTeamImprovement

Add more methods