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 Team API with its method-specific working model.
Team Design
Team API
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
Purposedifferent
When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.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.
Complexitysame
LowLow
Timedifferent
Half day initial, dann laufend5-20 min
Participantsdifferent
Ein Team plus Stakeholder2-8
Formatsame
Workshop + asyncWorkshop + async
Outputdifferent
Team API DocumentUnderstanding Check, Clarification Notes, Learning Gaps
Tags1 shared
TeamAlignmentCommunicationService
LearningUnderstandingCommunication
Add more methods

Often compared together

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

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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration of Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping