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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
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 notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Weekly Review.
Operations
Weekly Review
Purposedifferent
GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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 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.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 h2-8 h1-2 h Setup, laufend30-60 min
Participantsdifferent
2-85-1211
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Gap Matrix, Action Plan, Risk NotesEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsAction Lists, Project List, Review RoutineUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
StrategyAnalysisPlanning
Domain-Driven DesignEventsDiscoveryWorkshop
ProductivityPlanningTasksExecution
ProductivityExecutionPlanning
Add more methods