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 | ![]() Domain Modeling Domain Context Map | ![]() Domain Modeling Context Map | ![]() Business Strategy GAP 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. | 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. | 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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-30 min Planung, laufend | 1-3 h | 1-3 h | 1-3 h |
Participantsdifferent | 1 | 3-10 | 2-8 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Blocked Calendar, Capacity View, Focus Plan | Domain Context Map, Boundary Notes, Ownership Map | Context Map, Integration Patterns, Boundary Notes | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | PlanningTime managementFocus | Domain-Driven DesignContextBoundaries | Domain-Driven DesignBoundariesStrategy | StrategyAnalysisPlanning |



