View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Process Mapping | ![]() Knowledge Modeling Teach-back | ![]() Architecture Architecture Decision Record | ![]() Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 5-20 min | 15-45 min | 1-4 h |
Participantsdifferent | 3-10 | 2-8 | 1-3 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Understanding Check, Clarification Notes, Learning Gaps | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ProcessOperationsImprovement | LearningUnderstandingCommunication | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization |



