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 ALPEN Method
Operations
ALPEN Method
Paper illustration for Weekly Review.
Operations
Weekly Review
A paper tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
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 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.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
2-8 h10-20 min daily30-60 min25 min Zyklen
Participantsdifferent
5-12111
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsDaily Plan, Time Estimates, Review NotesUpdated Task System, Weekly Focus, Next ActionsFocus Sessions, Task Progress, Interruption Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
PlanningTime managementProductivityOperations
ProductivityExecutionPlanning
FocusTime managementProductivityExecution
Add more methods