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 arc42 |  Operations After-Action Review |  Architecture C4 Model |
|---|---|---|---|---|
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. | 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. | 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 | 1-2 Tage | 20-45 min | 1-4 h |
Participantsdifferent | 3-8 | 1-4 | 3-12 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Architecture Document, Context View, Runtime View, Deployment View | Lessons learned, Action items, Event summary | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | FlowMeasurementConstraints | ArchitectureDocumentationCommunication | LearningOperationsImprovement | ArchitectureCommunicationVisualization |