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 for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept 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.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.A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.
Complexitydifferent
LowMediumHighMedium
Timedifferent
1-2 h1-3 hHalf day1-2 h
Participantsdifferent
2-83-123-81-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeKnowledge Map, Critical Knowledge Areas, Transfer PlanStress Test Report, Action Plan per ScenarioConcept Map, Relationship Labels, Knowledge Gaps
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
KnowledgeMappingRisk
StrategyBusiness modelRiskDiagnosis
KnowledgeConceptsMappingSensemaking
Add more methods