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 Root Cause Tree Analysis SAAM (Software Architecture Analysis Method)Weekly Review

Criterion	Operations Getting Things Done	Operations Root Cause Tree Analysis	Architecture SAAM (Software Architecture Analysis Method)	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 a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.	SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.	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	High	Low
Timedifferent	1-2 h Setup, laufend	1-3 h	Preparation, scenario analysis, and findings review; effort depends on scope	30-60 min
Participantsdifferent	1	2-8	Architecture experts and stakeholders for scenarios and weighting	1
Formatdifferent	Async	Workshop	Workshop + async	Async
Outputdifferent	Action Lists, Project List, Review Routine	Cause Tree, Evidence Notes, Countermeasures	Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives	Updated Task System, Weekly Focus, Next Actions
Tagsno overlap	ProductivityPlanningTasksExecution	Root causeTreeIncidentQuality	ArchitectureChangeAnalysisComparisonQuality	ProductivityExecutionPlanning

Add more methods