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 ABC Analysis
Operations
ABC Analysis
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
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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 similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitysame
LowLowLowLow
Timedifferent
1-2 h30-60 min45–75 min30-60 min
Participantsdifferent
2-81-5Team members involved3-10
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeABC Classification, Focus Rules, Control List4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
PrioritizationOperationsPortfolio
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
Add more methods