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 Context Canvas with its core stages and visible working result.
Product Discovery
Context Canvas
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Purposedifferent
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.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.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 model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
45-90 min2-6 h1-3 h1-3 h
Participantsdifferent
3-102-82-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Context canvas, Open questions, Shared context notesEvent Model, UI Flow, Commands, Read ModelsGap Matrix, Action Plan, Risk NotesDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
ContextFramingRequirementsCanvas
EventsBlueprintDomain-Driven DesignBehavior
StrategyAnalysisPlanning
Domain-Driven DesignContextBoundaries
Add more methods