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 Time Blocking |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Assumption Surfacing |  Decision Making Pre-Mortem |
|---|---|---|---|---|
Purposedifferent | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 | Low | Medium | Low | Low |
Timedifferent | 15-30 min Planung, laufend | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 20–45 min |
Participantsdifferent | 1 | Designers, developers as users, and facilitation | 2-8 | Small cross-functional group |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Blocked Calendar, Capacity View, Focus Plan | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption List, Critical Assumptions, Learning Plan | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | PlanningTime managementFocus | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskDecisionDiscovery | RiskDecisionFailurePlanning |