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 Request for Comments |  Decision Making Cynefin Workshop |  Delivery RAID Log |  Decision Making Red Teaming |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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. | 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 | Medium | Low | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-180 min | 30 min Setup, dann laufend | 1-4 h |
Participantsdifferent | 3-20 Reviewer | 4-20 | 1-3 maintaining, briefing for everyone | 3-8 |
Formatdifferent | Async | Workshop | Async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Cynefin Map, Domain-specific Actions, Sensemaking Notes | RAID Log, Status Report Source | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ComplexitySensemakingDecision | RiskTrackingStakeholdersGovernance | RiskDecisionSensemaking |