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)After-Action Review Mad Sad Glad 4Ls Retrospective

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Operations After-Action Review	Agile Mad Sad Glad	Agile 4Ls 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.	After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.	When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.	When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent	Medium	Low	Low	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	20-45 min	30-60 min	45–75 min
Participantsdifferent	Designers, developers as users, and facilitation	3-12	3-10	Team members involved
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	Lessons learned, Action items, Event summary	Emotion Board, Themes, Action Items	4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	LearningOperationsImprovement	RetrospectiveTeamReflection	RetrospectiveLearningReflectionTeam

Add more methods