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 Risk Storming |  Decision Making Pre-Mortem |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-2 h Setup, laufend | 60-90 min | 20–45 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1 | 4-12 | Small cross-functional group | Designers, developers as users, and facilitation |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Action Lists, Project List, Review Routine | Annotated Diagram, Prioritized Risk List, Action Backlog | Risk list, Mitigation plan, Assumption log | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ProductivityPlanningTasksExecution | RiskArchitectureWorkshopValidation | RiskDecisionFailurePlanning | ArchitectureEngineeringFeedbackValidationTasks |