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
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 tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
Paper illustration for Eat the Frog
Operations
Eat the Frog
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
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.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.The method protects energy and attention for the task that creates the largest progress and is often postponed.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.
Complexitydifferent
MediumLowLowLow
Timedifferent
2-8 h25 min Zyklen15-90 min daily10-20 min daily
Participantsdifferent
5-12111
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsFocus Sessions, Task Progress, Interruption NotesPriority Task, Completion Note, Daily FocusDaily Plan, Time Estimates, Review Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
FocusTime managementProductivityExecution
PrioritizationProductivityFocusExecution
PlanningTime managementProductivityOperations
Add more methods