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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.
Complexitydifferent
LowLowMedium
Timedifferent
1-2 h30 min Setup, dann laufend1-3 h
Participantsdifferent
2-81-3 maintaining, briefing for everyone3-12
Formatdifferent
WorkshopAsyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeRAID Log, Status Report SourceKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
RiskTrackingStakeholdersGovernance
KnowledgeMappingRisk
Add more methods

Often compared together

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

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model