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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Empathy Mapping
UX Research
Empathy Mapping
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties.
Complexitydifferent
MediumLowLowMedium
Timedifferent
2-6 h15-45 min30–60 min2-4 h
Participantsdifferent
2-81-34-85-15
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsADR File, Decision Log, RationaleEmpathy Map, Assumptions List, Research GapsQuality Scenarios, Priority List, Architecture Concerns
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureRationaleDocumentationGovernance
SynthesisQualitativeWorkshop
RequirementsArchitectureWorkshop
Add more methods