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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Concierge MVP
Product Discovery
Concierge MVP
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 h2-8 h2–4 h review as a planning range; preparation and evaluation additional1-4 Wochen
Participantsdifferent
2-85-12Designers, developers as users, and facilitation3-10 Kunden
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsConcierge Learnings, Service Blueprint, MVP Risks
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Domain-Driven DesignEventsDiscoveryWorkshop
ArchitectureEngineeringFeedbackValidationTasks
MVPValidationServiceDiscovery
Add more methods