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
Paper illustration for Time Blocking
Operations
Time Blocking
Paper illustration for Ivy Lee Method
Operations
Ivy Lee Method
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.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.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.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 h15-30 min Planung, laufend5-10 min daily10-20 min daily
Participantsdifferent
5-12111
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsBlocked Calendar, Capacity View, Focus PlanDaily Priority List, Completion NotesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
PlanningTime managementFocus
PrioritizationProductivityExecution
PlanningTime managementProductivityOperations
Add more methods