View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Domain Context Map |  Operations Time Blocking |  Architecture Architecture Decision Record |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 15-30 min Planung, laufend | 15-45 min | 1-3 h |
Participantsdifferent | 3-10 | 1 | 1-3 | 2-8 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Blocked Calendar, Capacity View, Focus Plan | ADR File, Decision Log, Rationale | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Domain-Driven DesignContextBoundaries | PlanningTime managementFocus | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesStrategy |