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
Paper illustration of Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
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
Purposedifferent
The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning.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.
Complexitydifferent
HighLowLow
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews1-2 h5-20 min
Participantsdifferent
5-122-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogDomain Story, Glossary Notes, Process NarrativeUnderstanding Check, Clarification Notes, Learning Gaps
Tagsno overlap
ExecutionCadenceLearningGovernance
KnowledgeDomain-Driven DesignProcess
LearningUnderstandingCommunication
Add more methods

Often compared together

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

Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration of Strategic-Tactical-Operational Planning with its method-specific working model.
Business Strategy
Strategic, Tactical and Operational Planning
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 of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review