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 Cynefin Workshop |  Delivery MoSCoW |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
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. | 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. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 60-180 min | 30-90 min | 1-2 h |
Participantsdifferent | 2-8 | 4-20 | 3-12 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Issue Map, Positions, Argument Notes | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Prioritized Backlog, Release Scope, Tradeoff Notes | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | RationaleKnowledgeDecision | ComplexitySensemakingDecision | PrioritizationScopeDecision | KnowledgeConceptsMappingSensemaking |