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 |  Architecture ARID (Active Reviews for Intermediate Designs) |  Knowledge Modeling IBIS |  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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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 | Medium | High |
Timedifferent | 60-180 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 1-4 h |
Participantsdifferent | 4-20 | Designers, developers as users, and facilitation | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Issue Map, Positions, Argument Notes | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | ComplexitySensemakingDecision | ArchitectureEngineeringFeedbackValidationTasks | RationaleKnowledgeDecision | RiskDecisionSensemaking |