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 | ![]() Team Design Team Topologies Interaction Modes | ![]() Facilitation Expectation Mapping | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 60-120 min | Half day | 45-90 min | 1-2 h |
Participantsdifferent | 2-8 | Team-Leads plus Architecture | 3-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Interaction Heat Map, Agreements per Pair | Expectation Map, Alignment Notes, Agreements | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersTeam | AlignmentStakeholdersStrategyFacilitation |



