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 Change Analysis.
Operations
Change Analysis
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 Opportunity Interview
Product Discovery
Opportunity Interview
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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.When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
45-120 min2-8 h30-60 min je InterviewPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-65-125-12 InterviewsArchitecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Change Matrix, Cause Hypotheses, Validation Questions, Action ListEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsInterview Notes, Opportunity Themes, Customer QuotesDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives
Tagsno overlap
ChangeRoot causeTroubleshootingComparison
Domain-Driven DesignEventsDiscoveryWorkshop
DiscoveryInterviewsOpportunityCustomer
ArchitectureChangeAnalysisComparisonQuality
Add more methods