Methods · Aggregation and voting
WGM (Weighted Geometric Mean)
WGM raises each criterion score to the power of its own weight and multiplies the results; an alternative that scores very low on a single criterion is punished severely, whatever its performance elsewhere.
Base method's data type: Classical
What Is the Method?
WGM is an aggregation operator that multiplies criterion scores rather than adding them. It is not an independent decision method in its own right; it is a building block that operates inside subjective weighting methods such as AHP and inside group decisions. In AHP, WGM is the standard way of collapsing several experts' pairwise-comparison judgements into a single group judgement: each expert's judgement is raised to the power of that expert's weight, and the resulting values are multiplied together. The same operation can also collapse an alternative's scores across several criteria into a single result score. Its output is one number, on the same scale as the inputs.
WGM's mathematical basis rests on Aczél and Saaty's 1983 work. That paper proved that the only consistent way of combining ratio-scale judgements is the geometric mean; the arithmetic mean does not preserve this consistency. This result makes WGM, in effect, the required step in AHP's synthesis of group decisions.
The Philosophy Behind It
WGM's philosophy is partial compensation, and that compensation is multiplicative. Under the arithmetic mean, a loss on one criterion is cancelled exactly by an equal gain on another; under WGM, a low score enters a product and so pulls the result down proportionally. As one criterion score approaches zero, WGM's result approaches zero too, however high the other criteria run. This places WGM close to a decision philosophy that says "I will not accept total collapse on any criterion."
This trait puts WGM at the opposite pole from WAM. WAM compensates a weakness on one criterion fully with strength on another; WGM limits that compensation and punishes weakness proportionally. The gap between the two widens further once ratio judgements are in play (how many times better one thing is than another): as Aczél and Saaty showed, WGM, not WAM, is the consistent way of combining judgements of that kind.
How It Works
WGM takes two inputs: positive criterion scores and weights that sum to 1.
First, validate the weights. Check that no weight is negative and that they sum to 1; normalise the weights if necessary.
Second, take the weighted product. Each criterion's score is raised to the power of its own weight, and these values are then multiplied together. For numerical stability, this step is usually computed by taking logarithms, summing them, then exponentiating again; the result is the same.
Third, apply it in a group decision. Where several decision-makers have supplied judgements on the same pairwise-comparison matrix, each cell is combined via WGM using its own decision-maker's weight, yielding a single group matrix.
The formulas behind the 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 number WGM returns reflects a proportional balance across criteria; where one criterion scores very low, that low score does not carry through to the result in proportion to its weight but more harshly, because of the nature of multiplication. A result of 4.0 means the criteria's multiplicative contribution reaches 4.0; it is not a simple sum, as under WAM.
WGM's most striking trait is its extreme sensitivity to a score of zero or close to zero. If one criterion is 0, or very close to 0, the WGM result collapses towards 0 too, however high the other criteria run. A low WGM score for an alternative therefore does not mean that alternative is "poor overall"; it can be an amplified reflection of collapse on a single criterion.
Thus instead of writing:
"The WGM score came out low, so this alternative is weak overall"
the report should read:
"The WGM score came out low; this may be the amplified result of an extremely low value on a single criterion via multiplication, and which criterion drove the fall should be checked separately"
Data Type and Inputs
WGM works with crisp, positive data; a criterion score of zero or below renders the product undefined or meaningless. DecisionMind holds no separate fuzzy, grey or intuitionistic extension of this building block.
You need positive criterion scores for every alternative, on the same scale and comparable with one another, and criterion weights that sum to 1. WGM does not produce weights, it takes them from outside. A minimum of two criteria is required. WGM is mathematically better suited than WAM specifically where ratio judgements are involved (how many times better one thing is than another), such as in AHP's pairwise-comparison matrices.
When to Use It, When Not To
WGM is a sound choice where criterion scores sit on a ratio scale (where "how many times more than the other" is meaningful), where several decision-makers' ratio judgements need combining, or where an extreme low on one criterion should pull the result down sharply. Its most common use is building the group pairwise-comparison matrix in AHP.
WGM should not be used where a criterion score can be zero or very close to it; the result collapses meaninglessly to zero. Where full compensation is wanted, that is, where a weakness on one criterion is expected to be fully balanced by another, WAM is the better fit than WGM.
Ratio judgements, group-decision synthesis → WGM
One of the criterion scores can be, or is, zero → WAM (or a pre-processing step that handles the zero first)
Full compensation wanted → WAM
A penalty for weakness harsher even than WGM's is wanted → WHM
The degree of penalty should be tunable by a single parameter → Power mean, which equals WGM as r approaches zero
Strengths
WGM's greatest strength is its mathematical consistency with ratio judgements. As Aczél and Saaty proved, where ratio-scale judgements are involved, the geometric mean is the only consistent way to combine them; this makes WGM a necessity rather than an arbitrary preference. WGM also does not hide an extreme weakness on one criterion; unlike WAM, it reflects that weak point visibly in the result. This trait, as Forman and Peniwati showed, makes group decisions in AHP less exposed to individual extremes (Forman and Peniwati, 1998).
Weaknesses
Its limitations stem from the same structure. WGM's weakness is its extreme sensitivity to zero. If one criterion score is zero or very close to it, the result approaches zero too, however high the other criteria run; this creates an unwanted harshness in some applications (Saaty and Vargas, 2007). WGM is also harder to interpret than WAM; how "good" a multiplicative result is proves less intuitive than an additive one, and takes more effort to explain to a decision-maker. Finally, like WAM, WGM depends on the quality of the weights; the weights come from outside, and a poorly determined set of weights corrupts the result directly.
Common Mistakes
The most common mistake is using WGM where one criterion score is zero or very close to it; the result then collapses almost automatically to zero, and the information carried by the other criteria is lost. A second mistake is comparing WGM and WAM results directly and asking "which is correct"; the two carry different assumptions, neither is right or wrong, and which fits the decision question must be chosen beforehand. A third mistake is using WGM outside AHP, in a context where an arithmetic sum is more natural, such as directly additive cost items.
The governing principle is this:
WGM is the mathematically consistent way of combining ratio judgements; but where one criterion score sits close to zero, this consistency comes at the cost of pushing the result to an extreme.
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 a teaching construction, built by DecisionMind for validation, that shows concretely how WGM changes the ranking relative to WAM.
1. Food Safety: Combining an inspection score across two suppliers (illustrative example)
Consider a food inspection unit evaluating two suppliers on two criteria (a hygiene score and a documentation score, both on a 0–10 scale, both "higher is better"), with equal weight (0.50) given to each.
| Supplier | Hygiene | Documentation |
|---|---|---|
| G1 | 1 | 9 |
| G2 | 4 | 4 |
| Direction | higher is better | higher is better |
| Weight | 0.50 | 0.50 |
G1's hygiene score is very low (1), its documentation score very high (9). G2's two scores are both middling (4 and 4).
Under WAM: G1 = 0.50×1 + 0.50×9 = 5.00. G2 = 0.50×4 + 0.50×4 = 4.00. WAM puts G1 ahead, because the high documentation score fully offsets the low hygiene score.
Under WGM: G1 = 1^0.50 × 9^0.50 = 3.00. G2 = 4^0.50 × 4^0.50 = 4.00. WGM now puts G2 ahead; the ranking reverses completely.
| Supplier | WAM score | WAM rank | WGM score | WGM rank |
|---|---|---|---|---|
| G1 | 5.00 | 1 | 3.00 | 2 |
| G2 | 4.00 | 2 | 4.00 | 1 |
The result reads as follows. WAM fully offsets G1's very low hygiene score with its high documentation score and puts G1 ahead. WGM instead punishes the very low hygiene score through multiplication and puts the balanced G2 ahead. The two methods draw opposite conclusions from the same data, because their assumptions about compensation differ.
The inspection unit hesitates here: whether a supplier with a very low hygiene score should be approved at all, however high its documentation score, is a policy question. If no supplier falling below a certain hygiene threshold should ever be approved, the right tool is neither WAM nor WGM; suppliers below the threshold should be screened out first, and only the remainder ranked. Using WGM can serve as an approximation of that threshold logic, but it does not substitute for it.
In the report: "Under equal weighting and the full-compensation assumption (WAM), G1 comes out ahead; but under WGM, which punishes the extreme low hygiene score, G2 comes out ahead. The ranking depends on which aggregation assumption is chosen."
Source: This table is an illustrative example, constructed by DecisionMind to validate its WGM engine against WAM; it is not drawn from a specific paper. The engine reproduces the same results.
2. Public Transport: Evaluating bus-fleet renewal proposals
A municipal public transport operator will evaluate three bus manufacturers' proposals against three criteria (fuel efficiency, maintenance-cost efficiency, delivery-time score), all "higher is better". The operator set the weights through a ratio comparison ("this manufacturer is this many times better than that one") and chose WGM for the aggregation.
Suppose one manufacturer scores very low on delivery time but scores fairly high on the other two criteria. WGM amplifies and punishes that low delivery-time score proportionally, placing that manufacturer further behind than WAM would.
The operator hesitates here: it is not known whether the shortfall in delivery time stems from a temporary supply problem or a structural weakness in the manufacturer. WGM cannot make that distinction; it only punishes the number. The manufacturer should therefore not be eliminated outright before the reason for the low score has been investigated further.
In the report: "Under WGM, the manufacturer with the low delivery-time score falls behind; the final decision should not proceed until the reason for this shortfall has been confirmed with the supply-chain team."
3. Textiles: Combining quality scores in fabric-supplier approval
A textile manufacturer will evaluate three fabric suppliers against three quality criteria (colour fastness, weave density, shrinkage-rate score), all "higher is better". The quality team preferred WGM because it considers a very low score on any criterion for a supplier unacceptable.
The method combines the three suppliers' scores via a weighted product. Suppose one supplier scores very low on colour fastness but high on the other two criteria; WGM pushes this supplier markedly behind, whereas WAM applied to the same data might have left it in the middle of the ranking.
The quality team hesitates here: does WGM's low score mean the supplier genuinely should be rejected, or is it only an amplified picture of weakness on one criterion? The team should remember that WGM deliberately punishes weakness on this criterion harshly, that this is precisely why the method was chosen, and should defend its decision accordingly.
In the report: "Under WGM, the supplier with the low colour-fastness score falls markedly behind; this outcome is consistent with the team's policy of accepting no serious weakness on any criterion."
4. What Not to Do
Had G1's hygiene score in the food-safety table been 0, the WGM result would have come out exactly 0, even with a documentation score of 9; this shows the risk of using WGM with scores near zero. A second error is placing WGM and WAM results side by side and drawing a blanket conclusion such as "WGM is always more correct" or "WAM is always fairer"; the two carry different decision philosophies, and which is correct depends on the decision question, not the data. A third error is treating the 1.00-point gap between G1's and G2's WGM scores (3.00 against 4.00) as a minor numerical detail; this gap is a direct consequence of the extreme low hygiene score and signals a policy decision.
Sources
For the formulas behind the step, the intermediate tables and citation formats (BibTeX, RIS, APA), see the DecisionMind method page: decisionmind.app/library/wgm
Aczél, J., & Saaty, T. L. (1983). Procedures for synthesizing ratio judgements. Journal of Mathematical Psychology, 27(1), 93–102. DOI: 10.1016/0022-2496(83)90028-7
Forman, E., & Peniwati, K. (1998). Aggregating individual judgments and priorities with the analytic hierarchy process. European Journal of Operational Research, 108(1), 165–169. DOI: 10.1016/s0377-2217(97)00244-0
Saaty, T. L., & Vargas, L. G. (2007). Dispersion of group judgments. Mathematical and Computer Modelling, 46(7–8), 918–925. DOI: 10.1016/j.mcm.2007.03.004