View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Decision Making Pre-Mortem |  Operations Weekly Review |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 60-90 min | 20–45 min | 30-60 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 4-12 | Small cross-functional group | 1 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | 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 |
Tagsno overlap | RiskArchitectureWorkshopValidation | RiskDecisionFailurePlanning | ProductivityExecutionPlanning | ArchitectureEngineeringFeedbackValidationTasks |