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
Paper illustration for Concierge MVP
Product Discovery
Concierge MVP
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Purposedifferent
When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution.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.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 a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-4 Wochen1-3 h2-6 h1-3 h
Participantsdifferent
3-10 Kunden2-82-83-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Concierge Learnings, Service Blueprint, MVP RisksContext Map, Integration Patterns, Boundary NotesEvent Model, UI Flow, Commands, Read ModelsContext Canvas, Glossary, Integration Notes
Tagsno overlap
MVPValidationServiceDiscovery
Domain-Driven DesignBoundariesStrategy
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignBoundariesModeling
Add more methods