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 Alignment Mapping |  Engineering Goal Question Metric |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 60-120 min | 1-2 h | 90-180 min | 60–90 min |
Participantsdifferent | 2-8 | 4-12 | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Alignment Map, Open Issues, Decision Questions | GQM Table, Metric Profiles | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | AlignmentStakeholdersStrategyFacilitation | MetricsMeasurementEngineeringAlignment | StakeholdersAlignmentFacilitationChange |