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)Getting Things Done Decision Rights Mapping Weekly Review

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Operations Getting Things Done	Decision Making Decision Rights Mapping	Operations Weekly Review
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 many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.	In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.	In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.
Complexitydifferent	Medium	Medium	Medium	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	1-2 h Setup, laufend	90-180 min	30-60 min
Participantsdifferent	Designers, developers as users, and facilitation	1	4-12	1
Formatdifferent	Workshop + async	Async	Workshop	Async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Action Lists, Project List, Review Routine	Decision Rights Matrix, Agreement	Updated Task System, Weekly Focus, Next Actions
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	ProductivityPlanningTasksExecution	DecisionGovernanceAlignmentResponsibility	ProductivityExecutionPlanning

Add more methods