methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Weekly Review.
Operations
Weekly Review
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.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 many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-6 h30-60 min1-3 h1-2 h Setup, laufend
Participantsdifferent
2-813-101
Formatdifferent
Workshop + asyncAsyncWorkshopAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsUpdated Task System, Weekly Focus, Next ActionsDomain Context Map, Boundary Notes, Ownership MapAction Lists, Project List, Review Routine
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ProductivityExecutionPlanning
Domain-Driven DesignContextBoundaries
ProductivityPlanningTasksExecution
Add more methods