View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Team Charter | ![]() Systems Thinking Evaporating Cloud | ![]() Systems Thinking CATWOE Analysis | ![]() Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h | 60-120 min | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 2-8 | 3-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamAlignmentCollaboration | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingFramingStakeholders | AlignmentStakeholdersTeam |



