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 Teach-back.
Knowledge Modeling
Teach-back
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 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.Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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 h5-20 min30-60 min30-60 min
Participantsdifferent
2-82-83-123-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeUnderstanding Check, Clarification Notes, Learning GapsStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
LearningUnderstandingCommunication
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods