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 ARID (Active Reviews for Intermediate Designs) |  Architecture C4 Model |  Architecture Risk Storming |
|---|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 h | 60-90 min |
Participantsdifferent | 3-8 | Designers, developers as users, and facilitation | 1-5 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Context Diagram, Container Diagram, Component Diagram | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | FlowMeasurementConstraints | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureCommunicationVisualization | RiskArchitectureWorkshopValidation |