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 |  Architecture arc42 |  Operations After-Action Review |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 1-2 Tage | 20-45 min | 15-45 min |
Participantsdifferent | 3-10 | 1-4 | 3-12 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Architecture Document, Context View, Runtime View, Deployment View | Lessons learned, Action items, Event summary | ADR File, Decision Log, Rationale |
Tagsno overlap | ProcessOperationsImprovement | ArchitectureDocumentationCommunication | LearningOperationsImprovement | ArchitectureRationaleDocumentationGovernance |