View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Evaporating CloudLASR (Lightweight Approach for Software Reviews)Alignment MappingStakeholder Mapping
| Criterion | ![]() Systems Thinking Evaporating Cloud | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Facilitation Alignment Mapping | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | 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. | 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 | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-2 h | 60–90 min |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Alignment Map, Open Issues, Decision Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureQualityRiskAssessmentLean | AlignmentStakeholdersStrategyFacilitation | StakeholdersAlignmentFacilitationChange |



