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)Architecture Decision RecordAssumption Surfacing
| Criterion |  Systems Thinking Evaporating Cloud |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Architecture Decision Record |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-120 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 15-45 min | 45-90 min |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 1-3 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Async | 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 | ADR File, Decision Log, Rationale | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureQualityRiskAssessmentLean | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskDecisionDiscovery |