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:Getting Things Done Design Thinking ARID (Active Reviews for Intermediate Designs)Weekly Review

Criterion	Operations Getting Things Done	Innovation Design Thinking	Architecture ARID (Active Reviews for Intermediate Designs)	Operations Weekly Review
Purposedifferent	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.	For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.	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.	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	High	Medium	Low
Timedifferent	1-2 h Setup, laufend	1 Tag bis mehrere Wochen	2–4 h review as a planning range; preparation and evaluation additional	30-60 min
Participantsdifferent	1	4-10	Designers, developers as users, and facilitation	1
Formatdifferent	Async	Workshop	Workshop + async	Async
Outputdifferent	Action Lists, Project List, Review Routine	Problem Statement, Prototype, Test Learnings	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Updated Task System, Weekly Focus, Next Actions
Tagsno overlap	ProductivityPlanningTasksExecution	InnovationPrototypeResearch	ArchitectureEngineeringFeedbackValidationTasks	ProductivityExecutionPlanning

Add more methods