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 |
|---|---|---|---|
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. |
Complexitydifferent | Low | Low | High |
Timedifferent | 30 min Setup, dann laufend | 1-4 h | 1-4 Wochen |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-5 | 1-6 |
Formatdifferent | Async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Context Diagram, Container Diagram, Component Diagram | Experiment results, Decision log, Learning summary |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationVisualization | ExperimentsGrowthAnalyticsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
