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 Architecture Decision Record |  Architecture Request for Comments |  Decision Making Constraint Analysis |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-30 min Planung, laufend | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min |
Participantsdifferent | 1 | 1-3 | 3-20 Reviewer | 2-8 |
Formatdifferent | Async | Async | Async | Workshop + async |
Outputdifferent | Blocked Calendar, Capacity View, Focus Plan | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | PlanningTime managementFocus | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | ConstraintsDecisionPlanningOptions |