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
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.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
LowLowLow
Timedifferent
1-2 h45–75 min30-60 min
Participantsdifferent
2-8Team members involved3-10
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process Narrative4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
Add more methods

Often compared together

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

Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective