View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Teach-back | ![]() Operations Process Mapping | ![]() Architecture Architecture Decision Record | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 5-20 min | 1-3 h | 15-45 min | 60-120 min |
Participantsdifferent | 2-8 | 3-10 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Process Map, Handoff List, Improvement Backlog | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | LearningUnderstandingCommunication | ProcessOperationsImprovement | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |



