View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Pre-Mortem |  Operations Weekly Review |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Getting Things Done |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 20–45 min | 30-60 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-2 h Setup, laufend |
Participantsdifferent | Small cross-functional group | 1 | Designers, developers as users, and facilitation | 1 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Updated Task System, Weekly Focus, Next Actions | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Action Lists, Project List, Review Routine |
Tagsno overlap | RiskDecisionFailurePlanning | ProductivityExecutionPlanning | ArchitectureEngineeringFeedbackValidationTasks | ProductivityPlanningTasksExecution |