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 notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Process Mapping method illustration showing its working structure
Operations
Process 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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 h1-2 h Setup, laufend20-45 min1-3 h
Participantsdifferent
2-813-123-10
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeAction Lists, Project List, Review RoutineLessons learned, Action items, Event summaryProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ProductivityPlanningTasksExecution
LearningOperationsImprovement
ProcessOperationsImprovement
Add more methods