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 CloudStakeholder MappingLASR (Lightweight Approach for Software Reviews)Future Reality Tree
| Criterion | ![]() Systems Thinking Evaporating Cloud | ![]() Facilitation Stakeholder Mapping | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Systems Thinking Future Reality Tree |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 60-120 min | 60–90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-4 h |
Participantsdifferent | 2-8 | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Stakeholder Map, Engagement Plan, Risk Notes | 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 | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | StakeholdersAlignmentFacilitationChange | ArchitectureQualityRiskAssessmentLean | Theory of ConstraintsSystems thinkingChange |



