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 a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Learning Review.
Operations
Learning Review
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.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
LowLowMedium
Timedifferent
1-2 h20-45 min1-3 h
Participantsdifferent
2-83-123-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeLessons learned, Action items, Event summaryLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
LearningOperationsImprovement
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

Process Mapping method illustration showing its working structure
Operations
Process Mapping
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem