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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Purposedifferent
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.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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.
Complexitydifferent
LowMediumMedium
Timedifferent
15-45 min1-3 h2-6 h
Participantsdifferent
1-32-82-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleGap Matrix, Action Plan, Risk NotesEvent Model, UI Flow, Commands, Read Models
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
StrategyAnalysisPlanning
EventsBlueprintDomain-Driven DesignBehavior
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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