methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Future Reality Tree.
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.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
MediumMediumHigh
Timedifferent
60-120 min3–4 h for initial assessment; preparation and deeper analysis additional2-4 h
Participantsdifferent
2-81 or a small team; particularly suitable for 3–4 people3-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Conflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsLean 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 checksFuture Reality Tree, Negative Branches, Assumption List, Improved Injections
Tagsno overlap
Theory of ConstraintsAssumptionsSystems thinking
ArchitectureQualityRiskAssessmentLean
Theory of ConstraintsSystems thinkingChange
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing