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
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 for ALPEN Method
Operations
ALPEN Method
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Purposedifferent
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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-8 h10-20 min daily3–4 h for initial assessment; preparation and deeper analysis additional45-90 min
Participantsdifferent
5-1211 or a small team; particularly suitable for 3–4 people2-5
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsDaily Plan, Time Estimates, Review NotesLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksA3 Report, Action Plan, Root Cause Analysis
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
PlanningTime managementProductivityOperations
ArchitectureQualityRiskAssessmentLean
LeanProblem solvingCoachingOperations
Add more methods