View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Evaporating Cloud | ![]() Facilitation Delegation Poker | ![]() Facilitation Responsibility Poker |
|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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 | Low |
Timedifferent | 60-120 min | 45-90 min | 45-90 min |
Participantsdifferent | 2-8 | 3-10 | 3-10 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Delegation Board, Decision Boundaries, Role Agreements | Responsibility Map, Role Agreements, Open Questions |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | AutonomyRolesTeam | RolesResponsibilityTeamFacilitation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






