View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Time Blocking |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Getting Things Done |  Operations Weekly Review |
|---|---|---|---|---|
Purposedifferent | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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. | 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 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 | Low | High | Medium | Low |
Timedifferent | 15-30 min Planung, laufend | Preparation, scenario analysis, and findings review; effort depends on scope | 1-2 h Setup, laufend | 30-60 min |
Participantsdifferent | 1 | Architecture experts and stakeholders for scenarios and weighting | 1 | 1 |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | Blocked Calendar, Capacity View, Focus Plan | 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 | Action Lists, Project List, Review Routine | Updated Task System, Weekly Focus, Next Actions |
Tagsno overlap | PlanningTime managementFocus | ArchitectureChangeAnalysisComparisonQuality | ProductivityPlanningTasksExecution | ProductivityExecutionPlanning |