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 Cynefin Workshop | ![]() Delivery RAID Log | ![]() Architecture arc42 | ![]() Decision Making Red Teaming |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 60-180 min | 30 min Setup, dann laufend | 1-2 Tage | 1-4 h |
Participantsdifferent | 4-20 | 1-3 maintaining, briefing for everyone | 1-4 | 3-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Cynefin Map, Domain-specific Actions, Sensemaking Notes | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | ComplexitySensemakingDecision | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | RiskDecisionSensemaking |



