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 Starfish Retrospective
Agile
Starfish Retrospective
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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.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
LowLowLowMedium
Timedifferent
1-2 h45-90 min30-60 min1-3 h
Participantsdifferent
2-84-123-103-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeStarfish Board, Practice Changes, ExperimentsEmotion Board, Themes, Action ItemsProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
RetrospectiveImprovementExperimentsTeam
RetrospectiveTeamReflection
ProcessOperationsImprovement
Add more methods