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 | ![]() Architecture Architecture Decision Record | ![]() Facilitation Barcamp | ![]() Architecture C4 Model |
|---|---|---|---|---|
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. | 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. | When many people can contribute knowledge and the flow should stay open, Barcamp provides a framework for self-organized sessions. The format channels energy without defining the content too narrowly in advance. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 5-20 min | 15-45 min | Halber Tag bis 2 Tage | 1-4 h |
Participantsdifferent | 2-8 | 1-3 | 15-200 | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | ADR File, Decision Log, Rationale | Session Board, Session Notes, Community Learnings | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | LearningUnderstandingCommunication | ArchitectureRationaleDocumentationGovernance | FacilitationLarge groupLearning | ArchitectureCommunicationVisualization |



