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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Weekly Review.
Operations
Weekly Review
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.Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
2-6 h1-2 h1-2 h Setup, laufend30-60 min
Participantsdifferent
2-82-811
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsDomain Story, Glossary Notes, Process NarrativeAction Lists, Project List, Review RoutineUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
KnowledgeDomain-Driven DesignProcess
ProductivityPlanningTasksExecution
ProductivityExecutionPlanning
Add more methods