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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
2-6 h1-3 h30-90 min45-90 min
Participantsdifferent
2-82-82-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsContext Map, Integration Patterns, Boundary NotesConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignBoundariesStrategy
ConstraintsDecisionPlanningOptions
OutcomesStrategyBehaviorPlanning
Add more methods