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 |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Weekly Review |
|---|---|---|---|
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. | 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 | Low | Medium | Low |
Timedifferent | 20–45 min | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min |
Participantsdifferent | Small cross-functional group | Designers, developers as users, and facilitation | 1 |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | 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 | RiskDecisionFailurePlanning | ArchitectureEngineeringFeedbackValidationTasks | ProductivityExecutionPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
