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 Bottleneck Analysis |  Architecture Architecture Decision Record |  Operations After-Action Review |  Operations Process Mapping |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 15-45 min | 20-45 min | 1-3 h |
Participantsdifferent | 3-8 | 1-3 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | ADR File, Decision Log, Rationale | Lessons learned, Action items, Event summary | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | FlowMeasurementConstraints | ArchitectureRationaleDocumentationGovernance | LearningOperationsImprovement | ProcessOperationsImprovement |