View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Architecture C4 Model |  Growth A/B Testing |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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 | Low | Low | High | Low |
Timedifferent | 30 min Setup, dann laufend | 1-4 h | 1-4 Wochen | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-5 | 1-6 | 4-12 |
Formatdifferent | Async | Workshop + async | Async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Context Diagram, Container Diagram, Component Diagram | Experiment results, Decision log, Learning summary | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationVisualization | ExperimentsGrowthAnalyticsValidation | RiskArchitectureWorkshopValidation |