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 for Teach-back.
Knowledge Modeling
Teach-back
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Purposedifferent
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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.
Complexitydifferent
LowMediumLow
Timedifferent
5-20 min60-120 minHalf day initial, dann laufend
Participantsdifferent
2-82-8Ein Team plus Stakeholder
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanTeam API Document
Tags1 shared
LearningUnderstandingCommunication
ArchitectureCommunicationStakeholdersCanvas
TeamAlignmentCommunicationService
Add more methods

Often compared together

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

Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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