View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Red Teaming |  Architecture C4 Model |  Product Discovery Smoke Test |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 | High | Low | Low | Low |
Timedifferent | 1-4 h | 1-4 h | 1-5 Tage | 60-90 min |
Participantsdifferent | 3-8 | 1-5 | Nutzertraffic | 4-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Challenge Findings, Risk Register, Mitigation Plan | Context Diagram, Container Diagram, Component Diagram | Interest Metrics, Conversion Signal, Learning Note | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RiskDecisionSensemaking | ArchitectureCommunicationVisualization | ValidationExperimentsDemandGrowth | RiskArchitectureWorkshopValidation |