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 Concept Mapping |  Operations Accountability Ladder |  Systems Thinking Evaporating Cloud |  Facilitation Responsibility Poker |
|---|---|---|---|---|
Purposedifferent | 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. | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 h | 20-45 min | 60-120 min | 45-90 min |
Participantsdifferent | 1-8 | 1-8 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Ownership Reflection, Action Commitment, Coaching Notes | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Responsibility Map, Role Agreements, Open Questions |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | ResponsibilityLeadershipTeam | Theory of ConstraintsAssumptionsSystems thinking | RolesResponsibilityTeamFacilitation |