View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling IBIS | ![]() Decision Making Red Teaming | ![]() Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 h | 1-4 h | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 2-8 | 3-8 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Issue Map, Positions, Argument Notes | Challenge Findings, Risk Register, Mitigation Plan | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | RationaleKnowledgeDecision | RiskDecisionSensemaking | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






