View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Decision Making Red Teaming |  Product Discovery Smoke Test |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | High | Low | Low |
Timedifferent | 1-2 Tage | 1-4 h | 1-5 Tage | 60-90 min |
Participantsdifferent | 1-4 | 3-8 | Nutzertraffic | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Challenge Findings, Risk Register, Mitigation Plan | Interest Metrics, Conversion Signal, Learning Note | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureDocumentationCommunication | RiskDecisionSensemaking | ValidationExperimentsDemandGrowth | RiskArchitectureWorkshopValidation |