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 Getting Things Done |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Pre-Mortem |
|---|---|---|---|
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. | 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 early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 h Setup, laufend | 2–4 h review as a planning range; preparation and evaluation additional | 20–45 min |
Participantsdifferent | 1 | Designers, developers as users, and facilitation | Small cross-functional group |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | Action Lists, Project List, Review Routine | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | ProductivityPlanningTasksExecution | ArchitectureEngineeringFeedbackValidationTasks | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
