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 of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
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.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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
MediumLowMediumLow
Timedifferent
2-8 h60-90 min1-2 h Setup, laufend10-20 min daily
Participantsdifferent
5-124-1011
Formatdifferent
WorkshopWorkshopAsyncAsync
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsProblem Cluster, Prioritized Challenge, ExperimentAction Lists, Project List, Review RoutineDaily Plan, Time Estimates, Review Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
FacilitationDecisionProblem solvingWorkshop
ProductivityPlanningTasksExecution
PlanningTime managementProductivityOperations
Add more methods