Relevance Tree Analysis
Also known as: Relevance Tree Method, Relevance Number Analysis, Normative Relevance Tree, PATTERN-Style Relevance Trees
Relevance tree analysis is a normative forecasting method that decomposes a high-level objective into a hierarchy of sub-objectives, functions, and contributing technologies, and then assigns relevance numbers that quantify how much each branch contributes to its parent. By normalizing these numbers so that the children of every node sum to one and multiplying them down each path, the method produces an overall relevance score for every technology or task at the leaves, which ranks them by their importance to the top objective. Unlike exploratory forecasting, which projects what the future will be, relevance trees work backward from a desired goal — they are 'normative,' starting from where you want to go and identifying what must be developed to get there. Originating in defense and aerospace planning and codified in Glenn and Gordon's Futures Research Methodology, the technique remains a standard tool for research-and-development priority-setting and mission analysis.
Key highlights
- Imposes a clear, auditable structure on a complex objective, making the path from goals to specific technologies explicit.
- Produces commensurable priority scores that sum to one, supporting both ranking and proportional resource allocation.
- Localizes expert judgment to comparisons among siblings, keeping each elicitation cognitively manageable.
- Supports transparent sensitivity analysis by re-running the tree under alternative criteria weights to test robustness.
Intuition
This section is available to Pro members. Upgrade to Pro
How it works
This section is available to Pro members. Upgrade to Pro
When to use it
Use relevance tree analysis when you face a normative planning problem — a clearly stated objective that must be reached — and need to decide which subordinate technologies, tasks, or research programs deserve priority. It is well suited to mission analysis, R&D portfolio planning, and any setting where a complex goal can be decomposed into a reasonably stable hierarchy of contributing elements and where experts can judge the relative importance of branches against explicit criteria. It is less appropriate for exploratory questions about what the future might bring rather than how to reach a chosen future, for problems whose elements are so interdependent that a tree's assumption of separable, non-overlapping children badly distorts reality, or for situations where no agreed top-level objective exists. Because the output is only as credible as the structure and the relevance judgments, it is best used transparently and combined with methods such as Delphi to elicit the underlying numbers.
Strengths & limitations
- Imposes a clear, auditable structure on a complex objective, making the path from goals to specific technologies explicit.
- Produces commensurable priority scores that sum to one, supporting both ranking and proportional resource allocation.
- Localizes expert judgment to comparisons among siblings, keeping each elicitation cognitively manageable.
- Supports transparent sensitivity analysis by re-running the tree under alternative criteria weights to test robustness.
- Assumes a node's children are exhaustive and non-overlapping, which strains for goals with strongly interdependent elements.
- Final scores are only as sound as the tree structure and the subjective relevance numbers feeding it.
- The hierarchical form suppresses cross-branch interactions and feedback that may be central to real systems.
- Building and maintaining a large tree is labor-intensive, and the apparent precision of the numbers can mask deep uncertainty.
Common pitfalls
This section is available to Pro members. Upgrade to Pro
Applications
This section is available to Pro members. Upgrade to Pro
Frequently asked
What makes relevance tree analysis a 'normative' method?
Normative forecasting starts from a desired future or objective and asks what is needed to reach it, in contrast to exploratory forecasting, which starts from the present and projects what is likely to happen. A relevance tree is normative because it begins with a top-level goal at its root and decomposes downward into the sub-objectives and technologies required to achieve that goal. The relevance numbers then measure how much each element contributes to the goal. The whole analysis is oriented toward planning the means to a chosen end rather than predicting an unguided future, which is why it is used for R&D priority-setting and mission planning.
Why are relevance numbers normalized to sum to one at each node?
Normalization turns raw importance judgments into shares of the parent's relevance. By forcing the children of every node to sum to one, each number becomes the fraction of that parent's importance flowing down a particular branch, with nothing created or destroyed. This makes the figures interpretable and commensurable across the tree, and it gives the method its key property: when the normalized numbers are multiplied down each path, the resulting leaf scores themselves sum to one, so the tree cleanly partitions the top objective's total importance among all the candidate technologies. That partition is what lets the scores drive proportional budget allocation, not just ranking.
How are the relevance numbers themselves obtained?
They are expert judgments, but good practice makes them disciplined and transparent rather than arbitrary. Analysts usually define explicit criteria — such as significance, feasibility, and timing — and score each child of a node against those criteria, then combine the criterion scores into a single relevance value before normalizing. Because comparisons are made only among siblings under one parent, the task stays manageable. The elicitation is frequently run through a structured expert process such as Delphi to pool and converge judgments, and the resulting numbers are subjected to sensitivity analysis so that the team can see how much the final priorities depend on any particular contestable judgment.
Sources
- 1.Glenn, J. C., & Gordon, T. J. (Eds.). (2009). Futures Research Methodology, Version 3.0. The Millennium Project.ISBN 9780981894119
You have read it. What now?
Cite this page
ScholarGate. (2026, June 23). Relevance Tree Analysis. ScholarGate. https://scholargate.app/futures-foresight-studies/relevance-tree-analysis