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
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
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.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.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.
Complexitydifferent
LowMediumMedium
Timedifferent
45-90 min1-3 h2-6 h
Participantsdifferent
3-103-102-8
Formatdifferent
WorkshopWorkshopWorkshop + async
Outputdifferent
Context canvas, Open questions, Shared context notesDomain Context Map, Boundary Notes, Ownership MapEvent Model, UI Flow, Commands, Read Models
Tagsno overlap
ContextFramingRequirementsCanvas
Domain-Driven DesignContextBoundaries
EventsBlueprintDomain-Driven DesignBehavior
Add more methods

Often compared together

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

A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
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
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop