View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Discovery Assumption Mapping | ![]() Architecture Architecture Decision Record | ![]() Decision Making Red Teaming |
|---|---|---|---|
Purposedifferent | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 45-60 min | 15-45 min | 1-4 h |
Participantsdifferent | 2-8 | 1-3 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Assumption map, Test backlog, Risk ranking | ADR File, Decision Log, Rationale | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | AssumptionsRiskExperimentsValidation | ArchitectureRationaleDocumentationGovernance | RiskDecisionSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






