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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
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
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.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.For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-6 h2–4 h review as a planning range; preparation and evaluation additionalWochen bis Monate je Lernzyklus2-8 h
Participantsdifferent
2-8Designers, developers as users, and facilitation2-85-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsHypothesis list, MVPs, Learning reports, Pivot or persevere decisionEvent Timeline, Ubiquitous Language, Boundaries, Open Questions
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureEngineeringFeedbackValidationTasks
LeanStartupValidationMVP
Domain-Driven DesignEventsDiscoveryWorkshop
Add more methods