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 ARID (Active Reviews for Intermediate Designs) |  Decision Making Decision Tree |  Decision Making Pre-Mortem |
|---|---|---|---|
Purposedifferent | 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. | For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch. | 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 | 2–4 h review as a planning range; preparation and evaluation additional | 30-90 min | 20–45 min |
Participantsdifferent | Designers, developers as users, and facilitation | 1-6 | Small cross-functional group |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Decision Tree, Option Map, Assumption List | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | DecisionTreeOptions | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
