---
name: Multi-Criteria Decision Analysis
status: draft
territory: decision-making-under-uncertainty
msi_territory: decisions-under-uncertainty
sources:
  - title: "Keeney, Ralph L. & Raiffa, Howard (1976), Decisions with Multiple Objectives: Preferences and Value Tradeoffs, Wiley"
    url: https://openlibrary.org/works/OL4107460W
  - title: Saaty, Thomas L. (1980), The Analytic Hierarchy Process, McGraw-Hill
    url: https://openlibrary.org/works/OL2996560W
  - title: "Hwang, Ching-Lai & Yoon, Kwangsun (1981), Multiple Attribute Decision Making: Methods and Applications, Springer"
    url: https://openlibrary.org/works/OL8057448W
---

# Multi-Criteria Decision Analysis

## Why it matters

Some choices are easy because one thing settles them: cheapest wins, fastest wins, safest wins. The hard ones are hard because several things you care about pull in different directions at the same time — the cheaper vendor is slower, the faster one is riskier, the safest is dearest — and no single yardstick can break the tie. The instinct is to "weigh it all up" in your head and go with a gut feeling that sounds like a reason. Multi-criteria decision analysis is the discipline of doing that weighing out loud: name the things that matter, say how much each one matters, score every option on each, and combine them into one transparent comparison you can interrogate instead of a verdict you have to trust.

For example: you are choosing between three job offers. One pays the most but means a brutal commute and a shaky-sounding team. One pays less but is remote with great people and slower growth. One sits in the middle on everything. Decide by salary alone and the first wins; decide by gut over a weekend and you'll talk yourself into whichever felt best on Sunday night. Lay them out instead — pay, commute, team, growth, stability — score each offer on each, weight the criteria by what actually matters to *you*, and the comparison stops being a mood and becomes a structure: you can see *why* one leads, and exactly which preference would have to change to flip it.

- **What it reveals.** How a set of options genuinely stacks up across every criterion at once — not the one dimension that happens to be easiest to measure, but the full picture, with the tradeoffs made visible instead of resolved in the dark.
- **How it changes the read.** You stop asking *"which option feels best?"* and start asking *"on the things I've said I care about, and weighted the way I've said I care about them, which option actually comes out ahead — and how close is the race?"*
- **When to foreground it.** A choice among a handful of discrete options where three or more criteria really trade off, no single one can settle it, and you want your weighting made explicit rather than smuggled in by feel.
- **What you'd miss without it.** That the *weights* — not just the scores — quietly decide the winner; that a great score on one criterion can secretly buy back a fatal score on another; and that a ranking which looks settled may flip under a small, defensible change to how much one thing matters.
- **Where it misleads.** Pushed too hard it manufactures false precision — gut-feel weights and shaky scores dressed up as an authoritative number; and because the weights encode values, anyone who sets them can steer the answer, so a ranking is only as honest as the preferences feeding it.

## Realtime examples

See real, dated analyses where this mode ranked competing options across weighted criteria in the news → **[Multi-Criteria Decision Analysis on Main Street Independent](https://mainstreetindependent.com/analyses/technique/decisions-under-uncertainty/multi-criteria-decision)**

## How to invoke it in Ora

You're choosing among a handful of discrete options, several things you care about pull in different directions, and no single one can settle it — you want to see how the options stack up across all the dimensions, with your weights made explicit rather than left to feel.

List the options and what matters, and ask:

> "Run a multi-criteria decision analysis on these options — here are the criteria I care about and roughly how much each matters; rank them and show me how stable the ranking is."

The phrases *multi-criteria*, *MCDA / MCDM*, *weighted criteria*, *rank these options across*, *criteria matrix*, *AHP*, *what matters most*, and *how do they stack up* are what route you here. Bring the options as a concrete shortlist — three to five is the sweet spot — name the criteria, and say roughly how much each one matters, because the analysis is judged on whether the weights came from *your* preferences rather than an analyst default. If you genuinely have no weights yet, it will hand you a pairwise-comparison scaffold to fill in instead of inventing weights and passing them off as a verdict.

Two boundaries worth knowing. With only one or two criteria the machinery is overhead — a lighter single-criterion read fits better, and the mode will say so. And when the real difficulty is *probability and timing* under a single dominant criterion — an uncertain payoff over time rather than a tradeoff across criteria — that is the decision-under-uncertainty mode's job, not this one. This mode compares discrete options on competing criteria at one moment; it does not model the odds.

## How it works

Suppose you're choosing a family car, and you do the sensible-looking thing. You pick what matters — price, fuel economy, safety, cargo space — give each car a score out of ten on each, multiply each score by how much you care about that criterion, and add it all up. One number per car; highest total wins. It feels rigorous, and most of the time it's a real improvement over arguing in circles. But notice what just happened in three quiet steps, because each one is doing more work than it looks.

The first step is the **matrix**: criteria down one side, options across the top, a score in every cell. That alone is most of the value, because it forces you to look at every option on every criterion instead of fixating on the one that's loudest in your head. The second step is the **weights** — saying that safety matters more to you than cargo space, and by how much — and this is where the real power and the real danger both live. The third is the **combine**: roll the weighted scores into a single comparison. Do those three things honestly and a fuzzy "it depends" turns into something you can point at and argue with.

Here is the catch that makes the weights so consequential. Picture a car that's cheap, sips fuel, and swallows a month of luggage — but scores a 2 out of 10 on crash safety. In a plain weighted sum, that fatal 2 is just one term among four; its glittering scores on the other three can *outweigh* it, and the spreadsheet will cheerfully crown the unsafe car the winner. The method didn't malfunction — you asked "which car has the highest total?" and it answered honestly. But that wasn't the question you meant. You meant "which good car is also *safe enough*," and for you safety isn't something the other strengths are allowed to buy back. The plain weighted sum quietly assumes everything is tradeable against everything else, and that assumption — not the scores — picked the winner.

That is why there's a small family of methods rather than one, each making a slightly different assumption about how the scores should combine. The simplest, **weighted scoring** (and its disciplined cousin SMART), is exactly the multiply-and-add above — perfect when the criteria really are independent and really are tradeable, and transparency to everyone in the room is the priority. The **Analytic Hierarchy Process** (AHP) refuses to let you pull weights out of the air: instead of asking "how important is safety, 0 to 100?", it asks you to compare criteria two at a time — "how much more does safety matter than price?" — and then checks your answers for *consistency*, catching you if you've said safety beats price, price beats cargo, and cargo beats safety, a circle that can't be true. **TOPSIS** takes a geometric view: define the ideal car (best value on every criterion) and the worst imaginable one, and rank each real option by how close it sits to the ideal and how far from the worst. None of these is "the correct one"; you match the method to the shape of the decision.

And then the move that separates an honest analysis from a confident one: **test sensitivity.** Because the weights carry your values, a ranking is only as solid as those weights, so you nudge them — what if safety mattered a little less, price a little more? — and watch whether the winner holds or flips. If the top choice survives every reasonable nudge, you can lean on it. If a small, defensible change in one weight reorders the top two, the ranking is *fragile*, and that fragility is itself the finding: it tells you the decision really turns on that one preference, so that's the judgment to examine hardest rather than the spreadsheet to trust hardest. A crisp number that flips under a gentle push is more dangerous than no number at all — and the whole point of doing the weighing out loud is that you can give it that push and see.

## Framework & implementation

*This section uses Ora's own terms for the parts of an analysis, so that if you open the actual mode file they line up. Each is glossed in plain language on first use.*

### Pipeline execution

Multi-Criteria Decision Analysis is the **complexity-axis mode** of the **decision-making-under-uncertainty** territory — the one for choices that trade off across several criteria the decision-maker cares about, where no single criterion settles it and explicit weighting is wanted. It runs at **Gear 4**, Ora's most thorough setting: a **Depth analyst** and a **Breadth analyst** build the matrix in parallel and then critique each other (**cross-adversarial evaluation**) before a consolidator integrates the result.

The pass moves through the analysis in order. It **inventories the options** (the discrete alternatives in play), **defines each criterion operationally** (how a score would actually be assigned, in what units, and which direction is better), then **elicits the weights from the decision-maker's stated preferences** rather than imposing an analyst default. It **scores every option-by-criterion cell**, **names the aggregation method and why it fits** the decision's shape, produces the **aggregated ranking**, runs a **sensitivity analysis** to find the weight or score change that would flip the top choice, and identifies **dominant and dominated options** — pruning any option beaten on every criterion, and flagging any option that wins on every criterion as a choice that may need no further ceremony.

The mode's reasoning tools ride in its **`ANALYTICAL PERSPECTIVES`** block — the lenses it loads as it works. The load-bearing one is the **`mcdm-methods`** lens, which sits in the mode's **`lens_dependencies.required`** (it supplies the analysis's actual method, not just background): the catalog of AHP, SMART, ELECTRE, PROMETHEE, and TOPSIS, whose defining job is **method-matching** — choosing the aggregation method whose built-in assumption fits the decision instead of defaulting to one approach for everything. It works alongside always-loaded models including **trade-offs** (the no-free-lunch discipline underneath the whole matrix), **Arrow's impossibility theorem** (the deep limit on collapsing many criteria into one ranking), **prospect theory** and **loss aversion** (which surface when weight elicitation is anchored or framed), and **decision trees**.

### Output contract

The deliverable is a fixed MCDM matrix-with-ranking, so the comparison is auditable rather than a narrative verdict: **Options Inventory** (the discrete alternatives, with a completeness flag if the shortlist is missing), **Criteria Definitions** (each criterion operationally defined, with units and preference direction), **Weights with Rationale** (each weight, the elicitation method behind it, and why — flagging any weight that was imposed rather than elicited), **Scoring Matrix** (a score in every option-by-criterion cell), **Aggregated Ranking** (the named aggregation method, why it fits, and the resulting order, with a **stability flag** when the top choice is fragile), **Sensitivity Analysis** (the weight or score perturbation that would flip the ranking, and the pivot criterion the decision really turns on), **Dominant and Dominated Options** (options that win or lose on every criterion, with dominated ones pruned), and **Confidence per Finding** — kept as three separate kinds (**scoring** uncertainty, **weight** uncertainty, and **method-fit** uncertainty), because each has a different remedy and blending them into one number would hide that.

### Origin and evidence

The discipline grew out of decision theory's mid-century turn from single-objective optimization to choices with many objectives at once. Ralph Keeney and Howard Raiffa's *Decisions with Multiple Objectives: Preferences and Value Tradeoffs* (1976) supplied the foundational multi-attribute utility theory — the rigorous account of how preferences across several criteria can be represented and combined, and of the value tradeoffs that combining always implies. Thomas Saaty's *The Analytic Hierarchy Process* (1980) introduced AHP, with its pairwise-comparison elicitation and its consistency check, as a way to derive weights from structured human judgment rather than raw assertion. Ching-Lai Hwang and Kwangsun Yoon's *Multiple Attribute Decision Making: Methods and Applications* (1981) catalogued the field and introduced TOPSIS and its distance-from-ideal geometry. The throughline is methodological rather than empirical: each method is a coherent procedure with known strengths and known pathologies (AHP's rank-reversal, the weighted sum's silent compensation), and the accumulated lesson is that matching the method to the decision's structure — and testing the result's sensitivity to the weights — matters more than any single method's sophistication.

### Applications and common uses

- **Procurement and vendor selection.** The classic use: scoring bids on cost, capability, risk, and support, with the method chosen to reflect whether any criterion (security, compliance) is a true dealbreaker.
- **Siting and facility decisions.** Ranking candidate cities, plant sites, or distribution centers across talent, cost, tax climate, access, and risk, where stakeholders bring different weights.
- **Engineering and design tradeoffs.** Choosing an architecture or supplier across performance, cost, maintainability, and risk, with sensitivity analysis showing which preference would have to change to switch the choice.
- **High-stakes personal choices.** Job offers, homes, relocations, schools, or a care facility for a relative — making the weights explicit so the choice reflects considered preferences rather than whichever option felt best last.
- **Policy and grant prioritization.** Comparing options across economic, environmental, and social criteria where no single measure captures the decision and the weighting is itself contested.

### Failure modes and when not to use it

- **Weight-gaming and false precision.** Because the weights drive the answer, anyone setting them can steer the result — and gut-feel weights over shaky scores produce an authoritative-looking ranking no better than its inputs. The guards are eliciting weights from stated preferences (not analyst default), surfacing any imposed weights, and keeping scoring, weight, and method-fit confidence separate so the precision isn't overstated.
- **Silent compensation.** A fully compensatory method (a plain weighted sum) will happily rank a dealbreaker option first because its strengths average out its fatal flaw. When a criterion is really a veto, the mode reaches for an outranking method (ELECTRE / PROMETHEE) with explicit veto thresholds instead.
- **Aggregation-method opacity.** Emitting a ranking without saying which method produced it hides the assumption that drove it; the mode always names the method and ties the choice to the decision's shape.
- **Manufactured consensus.** Where criteria genuinely conflict and no option satisfies all of them, smoothing the tradeoff with weighting tricks until a clean winner emerges is a failure; the artifact surfaces the tradeoff instead, and where two analysts disagreed on which method fits, both rankings survive as a finding.

**When not to reach for it.** When **probability and timing dominate** — an uncertain payoff over time under a single criterion rather than a tradeoff across criteria — route to **decision-under-uncertainty**. When the task is **structuring the whole decision** across stakeholders, scenarios, and sequencing rather than ranking a fixed option set, that is **decision-architecture**. When the choice resolves once you simply **map the constraints** and no genuine weighted tradeoff remains, that is **constraint-mapping**. And with only one or two criteria, the full apparatus is overhead — a lighter read fits.

## Related

- **Decision Architecture** — the molecular sibling in the same territory: when the task is structuring the whole decision across stakeholders, scenarios, and sequencing, not ranking a fixed set of options on weighted criteria.
- **Decision Under Uncertainty** — the depth-thorough sibling for when probability and timing dominate under a single criterion — the boundary this mode hands off across when the difficulty is the odds, not the tradeoff.
- **Constraint Mapping** — the depth-light sibling for when the choice resolves once the constraints are mapped and no genuine multi-criteria tradeoff remains.
- **MCDM Methods** — the required lens this mode loads: the catalog of AHP, SMART, ELECTRE, PROMETHEE, and TOPSIS, and the discipline of matching the combining method to the shape of the decision.

## Sources

- [Keeney, Ralph L. & Raiffa, Howard (1976), Decisions with Multiple Objectives: Preferences and Value Tradeoffs, Wiley](https://openlibrary.org/works/OL4107460W)
- [Saaty, Thomas L. (1980), The Analytic Hierarchy Process, McGraw-Hill](https://openlibrary.org/works/OL2996560W)
- [Hwang, Ching-Lai & Yoon, Kwangsun (1981), Multiple Attribute Decision Making: Methods and Applications, Springer](https://openlibrary.org/works/OL8057448W)