InteractiveMap of Operations Research
Back to Uncertainty & Stochastic Systems
TheoryIntermediate03.04
Uncertainty & Stochastic Systems

Decision Analysis

Structured choice under uncertainty and multiple criteria.

Overview

Decision Analysis focuses on structured choice under uncertainty and multiple criteria. In the map of OR, it connects Decision trees, Utility, Value of information to decisions that must be modeled, solved, explained, and revised as evidence changes.

Decision trees, utility theory, value-of-information, and multi-criteria methods support transparent, defensible choices. The practical use case is clearest in adjacent OR applications, where the method helps turn constraints and tradeoffs into a decision artifact someone can inspect.

Core ideas

Decision trees

Decision trees is a core checkpoint for Decision Analysis: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Utility

Utility is a core checkpoint for Decision Analysis: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Value of information

Value of information is a core checkpoint for Decision Analysis: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Multi-criteria

Multi-criteria is a core checkpoint for Decision Analysis: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Risk preferences

Risk preferences is a core checkpoint for Decision Analysis: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

How to use it

  1. 1Start with a concrete case from the surrounding OR area: write the decision, time horizon, actors, and objective in operational language.
  2. 2Translate the problem into Decision trees, Utility, and Value of information; define units and data sources for each one.
  3. 3Build a small instance of Decision Analysis that can be solved or simulated by hand inspection before using full production data.
  4. 4Compare the recommendation against a baseline policy, not just against mathematical optimality.
  5. 5Document assumptions, sensitivity results, and the conditions under which the recommendation should be revisited.

Applications

Use this topic as a building block in nearby OR models; connect it to a concrete decision before treating it as a standalone application area.

Common pitfalls

  • Applying Decision Analysis because the label sounds appropriate while leaving the actual decision boundary vague.
  • Treating Decision trees as a technical detail instead of a modeling choice that affects the recommendation.
  • Reporting one answer without showing sensitivity to demand, capacity, costs, or behavioral assumptions.
  • Ignoring implementation details such as data quality, explainability, ownership, and how users will override bad recommendations.

Resources