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 Mad Sad Glad
Agile
Mad Sad Glad
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.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.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
LowLowMedium
Timedifferent
1-2 h30-60 min1-3 h
Participantsdifferent
2-83-103-10
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeEmotion Board, Themes, Action ItemsProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
RetrospectiveTeamReflection
ProcessOperationsImprovement
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
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 Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective