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 Eat the Frog
Operations
Eat the Frog
Paper illustration for Weekly Review.
Operations
Weekly Review
Paper illustration for Ivy Lee Method
Operations
Ivy Lee 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.The method protects energy and attention for the task that creates the largest progress and is often postponed.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.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
MediumLowLowLow
Timedifferent
2-8 h15-90 min daily30-60 min5-10 min daily
Participantsdifferent
5-12111
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsPriority Task, Completion Note, Daily FocusUpdated Task System, Weekly Focus, Next ActionsDaily Priority List, Completion Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
PrioritizationProductivityFocusExecution
ProductivityExecutionPlanning
PrioritizationProductivityExecution
Add more methods