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 ARID (Active Reviews for Intermediate Designs) |  Knowledge Modeling Concept Mapping |  Decision Making Cynefin Workshop |  Knowledge Modeling IBIS |
|---|---|---|---|---|
Purposedifferent | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-2 h | 60-180 min | 1-3 h |
Participantsdifferent | Designers, developers as users, and facilitation | 1-8 | 4-20 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Concept Map, Relationship Labels, Knowledge Gaps | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Issue Map, Positions, Argument Notes |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | KnowledgeConceptsMappingSensemaking | ComplexitySensemakingDecision | RationaleKnowledgeDecision |