View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Operations Process Mapping |  Architecture C4 Model |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 15-45 min | 1-3 h | 1-4 h | 20-45 min |
Participantsdifferent | 1-3 | 3-10 | 1-5 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Process Map, Handoff List, Improvement Backlog | Context Diagram, Container Diagram, Component Diagram | Lessons learned, Action items, Event summary |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ProcessOperationsImprovement | ArchitectureCommunicationVisualization | LearningOperationsImprovement |