Methods · Ranking
Weight Sensitivity Analysis (Robustness of a Ranking to Weight Change)
Weight sensitivity analysis is a robustness test that computes how much the criterion weights behind a ranking can change, and at what point that change breaks the ranking.
Base method's data type: Classical
What Is the Method?
Weight sensitivity analysis does not produce a ranking on its own. It takes a ranking already produced by some base method (for instance TOPSIS, SAW, or another ranking method) and asks: does this ranking hold even if the criterion weights change a little, or can a small change break it? Its output is a "stability interval" for every criterion (the range within which that weight can move without changing the ranking) and the criterion whose interval is narrowest, that is, the criterion to which the ranking is most sensitive. This gives the decision-maker a direct answer to the question "how reliable is your result."
The Philosophy Behind It
Most ranking methods produce a single ranking from a single set of weights, and that ranking is then presented as if it were a settled fact. Weight sensitivity analysis takes the opposite view: a ranking is valid only for the weights it was given, and those weights are usually contested or approximate. The method asks "how robust is this first place" before it asks "which alternative is first." Its philosophical consequence is this: the value of a ranking is measured not by the ranking itself but by how easily it can be overturned. A narrow stability interval means that even a small disagreement over weight could change the result.
How It Works
The method proceeds through four steps.
First, the base ranking. A chosen base method (for instance TOPSIS) computes an initial ranking and score using the existing weights.
Second, searching for the critical tipping point. For every criterion, that criterion's weight is raised and lowered while the other criteria's weights are redistributed proportionally. The method finds, by binary search, the smallest weight change at which the top two alternatives swap places.
Third, the stability interval. For every criterion, the lowest and highest weight value at which the ranking stays intact is identified. How far the current weight sits within this interval is recorded as that criterion's "margin."
Fourth, the most critical criterion. The criterion with the smallest margin is flagged as the one most likely to break the ranking, and every criterion's stability profile is reported as a table.
The formulas behind each step, the intermediate tables and the citation formats are given on the DecisionMind method page; this card carries no formulas.
How to Read the Output
The stability interval tells you how much a criterion's weight can change without swapping the base ranking's top two alternatives. A wide interval means you can be relaxed about that criterion; a narrow interval means even a small disagreement over it could change the result. The most critical criterion is where the discussion should concentrate most; if agreement cannot be reached on this criterion's weight, the reported ranking should not be treated as reliable. This analysis does not tell you "what is the correct weight"; it tells you only "how fragile is the ranking produced with the current weights."
Thus instead of writing:
"The analysis proved the ranking is correct"
the report should read:
"The ranking produced with these weights is stable only within a narrow interval on this criterion; if this criterion's weight is contested, the ranking is contested too"
Data Type and Inputs
Weight sensitivity analysis is built on top of a base method that works with crisp data: a decision matrix, criterion directions and initial weights are required; the base method to be used (such as TOPSIS or SAW) must also be specified, since the stability intervals depend on it. The method does not itself produce weights and does not require an external weight source either; it tests weights that already exist. DecisionMind currently has no completed, selectable implementation of this method: since the system has not yet defined a general contract for which base method is tested against which rule set, it does not offer this method to users, and when a request comes in it states plainly "this method is not currently available"; it does not silently produce a wrong or incomplete result. The computational logic described on this card follows the definition in the literature and was computed separately for illustrative purposes by this card's author.
When to Use It, When Not To
This analysis is appropriate once you have a result from a ranking method and want to see how robust the weights are before using that result as the basis for a decision or report. It is a particularly critical checkpoint when the weights are the average of several people's opinions, or an estimate.
If the weights are already very clear and uncontested (for instance, coming directly from a legal regulation), this analysis may add no further information. Since the method does not itself produce a ranking, it cannot be used alone when the ranking itself is what is needed; it always works alongside a base method.
A ranking already exists, the robustness of the weights needs testing → weight sensitivity analysis
The weights are clear and uncontested → an additional sensitivity test may not be needed
The real question is "which alternative is first" → first use a base ranking method (TOPSIS, SAW, VIKOR)
The question is how the weights themselves should be determined → AHP, BWM, SWARA (subjective); Entropy, CRITIC (objective)
Strengths
This analysis's most important contribution is that it stops a ranking from being presented as "the one true result"; it shows the decision-maker which criterion needs more caution. Stability intervals tie a contested weight decision to an objective threshold: the sentence "if the weight falls below this value, the ranking changes" is stronger than an abstract argument. The method is designed to work alongside any base ranking method.
Weaknesses
The analysis tracks only the change between the top two alternatives; a swap between the third- and fourth-ranked alternatives may go unseen by this measure. Stability intervals depend on the base method; the same data can give different stability profiles under TOPSIS and SAW, and this difference comes not from the sensitivity method itself but from the base method's mathematics (Wolters and Mareschal, 1995). Redistributing the other weights proportionally while one criterion's weight changes is an assumption; if the decision-maker wants to change weights by another logic, the intervals lose their validity. DecisionMind does not currently offer this method as a product; the computation described on this card is an illustrative demonstration of how the method should work.
Common Mistakes
The most common mistake is reading a wide stability interval as "the result is certainly correct"; the interval only shows the region in which the top two positions are preserved, and proves nothing about the scientific correctness of the result. A second mistake is identifying the most critical criterion and then closing the report without opening its weight to discussion. A third is assuming that a different base method would produce the same stability intervals; the intervals are specific to the base method. A fourth is assuming that the weight change will occur in only one criterion at a time and never testing realistic scenarios where several criteria change together.
The governing principle is this:
A ranking is valid only for the weights it was given; if a debate over weight continues on a criterion with a narrow stability interval, the ranking is just as contested.
Cases
Each case opens with a decision table, describes in words what the method does to it, and shows how to read the result. The first case is an illustrative worked example. The remaining cases are illustrative constructions.
1. E-commerce: Robustness test for an infrastructure-provider choice
An e-commerce firm has chosen among three providers for its store infrastructure using TOPSIS. Three criteria apply: interface usability score (higher is better), number of plugins (higher is better), and monthly subscription fee, in thousand TL (lower is better). The firm set the weights at 0.40 for the interface, 0.35 for the number of plugins, and 0.25 for the fee.
| Provider | Interface score | Number of plugins | Monthly fee (thousand TL) |
|---|---|---|---|
| S1 | 3.0 | 5.0 | 4.0 |
| S2 | 5.0 | 3.0 | 2.0 |
| S3 | 4.0 | 4.0 | 3.0 |
| Direction | higher is better | higher is better | lower is better |
| Weight | 0.40 | 0.35 | 0.25 |
With these weights, TOPSIS ranks S2 first, S3 second, and S1 third (S1 = 0.403, S2 = 0.597, S3 = 0.500). Weight sensitivity analysis tests how robust this ranking is: each criterion's weight is raised and lowered while the other two are redistributed proportionally, and the threshold at which the first- and second-ranked alternatives swap is sought.
| Criterion | Current weight | Stability interval | Margin |
|---|---|---|---|
| Interface score | 0.40 | [0.17 – 1.00] | 0.232 |
| Number of plugins | 0.35 | [0.00 – 0.44] | 0.093 |
| Monthly fee | 0.25 | [0.00 – 1.00] | 0.250 |
The result reads as follows. The margin on the number-of-plugins criterion (0.093) is far smaller than on the other two criteria; once this criterion's weight rises above 0.44, S2 and S3 swap places. The ranking stays intact even if the weight on interface score or fee moves across a wide range.
The firm hesitates here: the 0.35 weight given to the number of plugins is an estimate from the marketing team and does not rest on a firm measurement. If this weight were revised upward past 0.44, S3 would be expected to move ahead.
In the report: "The ranking produced by TOPSIS (S2 first) is most sensitive to a change in the number-of-plugins weight; if this weight rises above 0.44, S3 moves into first place."
Source: this case is an illustrative worked example. DecisionMind currently has no selectable implementation of weight sensitivity analysis; the system disables this method because it has not yet defined a general contract for which base method is tested against which stability rule. The figures here were computed independently by this card's author, following the method's definition in the literature (finding the critical weight point on a base ranking by binary search).
2. Testing centre: Robustness test for an assessment-method choice
A testing centre has chosen among three candidate assessment methods using SAW. Three criteria apply: validity score, reliability score, and administration time (lower is better). The centre has set the weights to give the most to validity, and less to reliability and time.
Weight sensitivity analysis finds that the stability interval on the validity weight is narrow, while the intervals on the reliability and time weights are wide. Suppose that once the validity weight drops slightly below its set value, the second-ranked method moves into first place.
The centre hesitates here: the validity weight was set not by consensus among assessment experts but on a single expert's recommendation. The narrowness of this weight's stability interval shows that the decision is excessively dependent on one person's opinion.
In the report: "A small change in the validity weight could change the ranking; confirming this weight with several experts' opinions is recommended."
3. Parks and gardens: Robustness test for green-space projects
A municipality's parks and gardens department has decided, using VIKOR, which green-space project to prioritise under a limited budget. Three criteria apply: estimated number of users, maintenance cost (lower is better), and ecological-contribution score. The department has set the weights to give more to the number of users and the ecological contribution, and less to cost.
Weight sensitivity analysis finds that the stability interval on the ecological-contribution weight is very narrow. Suppose that once this weight is reduced by a small amount, the project serving the most users moves ahead.
The department hesitates here: the ecological-contribution score is a subjective measure resting on expert opinion, and council members disagree over how much weight it should carry. The narrowness of the stability interval shows that this disagreement can directly affect the result.
In the report: "A small difference in the ecological-contribution weight could change the ranking; the final decision should be postponed until the council reaches agreement on this weight."
4. What Not to Do
In the same e-commerce table, it would be wrong to say, of a criterion whose stability interval comes out wide (for instance, interface score), "there is no risk at all here, let us not discuss it further"; a wide interval only shows that a change in that criterion's weight does not break the top two positions, and says nothing about changes further down the ranking. A second error is assuming that a different base method (for instance VIKOR instead of SAW) would produce the same stability intervals; the intervals depend on the base method. A third error is presenting the result of this method, which DecisionMind does not currently offer, as though it were a report generated by the product; this card's Case 1 is explicitly marked as an illustrative computation.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/weight-sensitivity
Mareschal, B. (1988). Weight stability intervals in multicriteria decision aid. European Journal of Operational Research, 33(1), 54–64. DOI: 10.1016/0377-2217(88)90254-8
Triantaphyllou, E., & Sanchez, A. (1997). A Sensitivity Analysis Approach for Some Deterministic Multi-Criteria Decision-Making Methods. Decision Sciences, 28(1), 151–194. DOI: 10.1111/j.1540-5915.1997.tb01306.x
Wolters, W. T. M., & Mareschal, B. (1995). Novel types of sensitivity analysis for additive MCDM methods. European Journal of Operational Research, 81(2), 281–290. DOI: 10.1016/0377-2217(93)e0343-v
Saltelli, A., Tarantola, S., Campolongo, F., & Ratto, M. (2004). Sensitivity Analysis in Practice. Wiley. DOI: 10.1002/0470870958