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 tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Ivy Lee Method
Operations
Ivy Lee Method
Purposedifferent
For easily distracted solo work, the method sets clear time boundaries for concentrated work. It protects attention when large tasks would otherwise fall apart into small avoidance moves.When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.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.With a restless workday full of too many open items, the method creates radical simplicity. It directs attention to a short sequence instead of a broad, still-open field.
Complexitydifferent
LowMediumMediumLow
Timedifferent
25 min Zyklen2-8 h2-6 h5-10 min daily
Participantsdifferent
15-122-81
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
Focus Sessions, Task Progress, Interruption NotesEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsEvent Model, UI Flow, Commands, Read ModelsDaily Priority List, Completion Notes
Tagsno overlap
FocusTime managementProductivityExecution
Domain-Driven DesignEventsDiscoveryWorkshop
EventsBlueprintDomain-Driven DesignBehavior
PrioritizationProductivityExecution
Add more methods