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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
A paper-based illustration representing Context Canvas with its core stages and visible working result.
Product Discovery
Context Canvas
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency.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.
Complexitydifferent
MediumLowMedium
Timedifferent
2-6 h45-90 min1-3 h
Participantsdifferent
2-83-102-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsContext canvas, Open questions, Shared context notesGap Matrix, Action Plan, Risk Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ContextFramingRequirementsCanvas
StrategyAnalysisPlanning
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
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