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 Future Reality Tree | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|
Purposedifferent | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | High | High | Medium |
Timedifferent | 2-4 h | Preparation, scenario analysis, and findings review; effort depends on scope | 45-60 min |
Participantsdifferent | 3-8 | Architecture experts and stakeholders for scenarios and weighting | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsSystems thinkingChange | ArchitectureChangeAnalysisComparisonQuality | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






