Methods · Aggregation and voting
WHM (Weighted Harmonic Mean)
WHM takes the reciprocal of each criterion score, averages those reciprocals with weights, then takes the reciprocal of that average; it is the most punishing aggregation form in the family, weighing a low score far more heavily than the others.
Base method's data type: Classical
What Is the Method?
WHM is the correct classical-statistics way of averaging ratios (speed, efficiency, cost per unit, and the like), and it is used in decision analysis as an aggregation building block. It is not an independent decision method in its own right; it comes into play when an alternative's scores across several criteria need collapsing into a single number in a way that foregrounds weakness on any one of them. Its output is one number, on the same scale as the inputs.
WHM's mathematical basis rests on the classical inequality of means: for positive numbers, the harmonic mean is always less than or equal to the geometric mean, and the geometric mean is in turn less than or equal to the arithmetic mean. This ordering is proved in detail in Bullen, Mitrinović and Vasić's comprehensive 1988 work, which defines WHM as the special case of the power-mean family where p equals minus one.
The Philosophy Behind It
WHM's philosophy is the most limited form of compensation in the family. Under the arithmetic mean, a loss on one criterion is offset exactly by an equal gain on another; under WHM, a low score grows once its reciprocal is taken, and so pulls the average down disproportionately. As a criterion score shrinks, its reciprocal grows rapidly and drags the WHM result towards it; WHM is thus the mean that "feels the weight of the weakest link" most keenly.
This trait makes WHM even more punishing than WGM. WGM punishes a weakness on one criterion through multiplication; WHM punishes that same weakness further by taking its reciprocal. The classical inequality of means fixes this ordering exactly: with the same scores, WHM is always less than or equal to WGM, and WGM is in turn less than or equal to WAM. Where a weakness on one criterion should almost determine the result outright, for instance where a system as a whole is taken to be only as strong as its weakest component, WHM is the correct tool.
How It Works
WHM takes two inputs: criterion scores greater than zero and weights that sum to 1.
First, validate the inputs. Check that every criterion score is greater than zero and that the weights sum to 1. A score of zero or below makes taking its reciprocal impossible or meaningless.
Second, average the reciprocals with weights. Take the reciprocal of each criterion score (1 divided by the score), multiply each by its own weight, and sum these.
Third, take the reciprocal of the result. The reciprocal of the sum obtained in the second step is taken; this final number is the WHM result.
Fourth, place it within the power-mean family. WHM is the special case of the power-mean family where r equals minus one; the same scores processed with different values of r produce a result somewhere between WHM and WAM.
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 WHM returns shows an overall performance dominated by the weakest point among the criteria. A score of 3.4 means the lowest criterion pulls the result down heavily; it reflects the weight of the most fragile criterion rather than, as under WAM, the criteria's average contribution.
WHM's most striking trait is that it can make a balanced but moderately scored alternative more favourable than one that swings between extremes (very high on one criterion, very low on another). This can be the exact opposite of what WAM would give; WAM fully offsets extreme scores, while WHM punishes that same extremity.
Thus instead of writing:
"The WHM score came out low, so this alternative is weak on every criterion"
the report should read:
"The WHM score came out low; this shows that the weakest of the criteria is pulling the result down strongly, and which criterion drove the fall should be examined separately"
Data Type and Inputs
WHM works with crisp, strictly positive data; a criterion score of zero makes taking its reciprocal impossible. DecisionMind holds no separate fuzzy, grey or intuitionistic extension of this building block.
You need criterion scores greater than zero for every alternative, on the same scale and comparable with one another, and criterion weights that sum to 1. WHM does not produce weights, it takes them from outside. A minimum of two criteria is required. WHM suits cases where ratio-type quantities (speed, efficiency, cost per unit) need averaging correctly, or where a system's weakest component is taken to determine the whole.
When to Use It, When Not To
WHM is a sound choice where criteria are ratio-type quantities, where a weakness on one criterion should strongly affect the result, or where the "a chain is only as strong as its weakest link" view is adopted. Its typical use is correctly averaging ratios such as per-unit efficiency or speed.
WHM should not be used where a criterion score can be zero; the result becomes undefined. Where full compensation is wanted, that is, where a weakness on one criterion is expected to be balanced by another, WAM is the better fit; WHM's punishment is harsher even than WGM's, so where a moderate penalty suffices, WGM should be preferred.
Ratio-type quantities, "the weakest link determines it" view → WHM
One of the criterion scores can be zero → WAM (or a pre-processing step that handles the zero first)
Full compensation wanted → WAM
A moderate penalty suffices, WHM's harshness is excessive → WGM
The degree of penalty should be tunable by a single parameter → Power mean, where r equals minus one is equivalent to WHM
Strengths
WHM's greatest strength is that it correctly averages ratio-type quantities; for quantities such as speed, efficiency or cost per unit, the arithmetic mean systematically gives the wrong answer, while WHM gives the correct one. WHM also does not hide the weakest point of a system or alternative; on the contrary, it reflects that weakness in the result more strongly than any other mean. This trait makes WHM a natural choice in fields such as safety or quality, where "weakest link" logic applies.
Weaknesses
WHM's weakness is its extreme severity. If one criterion score approaches zero, the WHM result shrinks rapidly too, which can create an unrealistic harshness in some applications (Bullen, Mitrinović and Vasić, 1988). WHM is also harder to interpret than even WGM for a decision-maker used to an additive average; "take the reciprocal, average it, then take the reciprocal again" is not an intuitive operation, and is misread if not explained carefully. Finally, like the other members of the family, WHM 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 WHM where one criterion score is zero or very close to it; the result then shrinks meaninglessly or becomes undefined. A second mistake is reading a WHM result on the same scale and in the same sense as a WAM result; the two methods can produce very different numbers from the same inputs, and this gap is not an error but the natural consequence of their different assumptions about compensation. A third mistake is using WHM on quantities that are not ratio-type, such as directly additive cost items, where the arithmetic mean is the more correct choice.
The governing principle is this:
WHM correctly averages ratio-type quantities and does not hide the weakest criterion; but this severity can shrink the result unrealistically once one criterion score approaches zero.
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 WHM changes the ranking relative to WAM.
1. Freight: Combining delivery performance across two fleet options (illustrative example)
Consider a freight company comparing two fleet options on delivery-performance scores across three periods (summer, winter, peak season), each on a 0–10 scale, "higher is better", with equal weight (one third) given to each.
| Fleet | Summer | Winter | Peak season |
|---|---|---|---|
| F1 | 2 | 4 | 8 |
| F2 | 3 | 4 | 5 |
| Direction | higher is better | higher is better | higher is better |
| Weight | 0.333 | 0.333 | 0.334 |
F1's performance varies widely between periods: very low in winter (2), very high in peak season (8). F2's performance is more balanced: 3, 4 and 5.
Under WAM: F1 = (2+4+8)/3 = 4.67. F2 = (3+4+5)/3 = 4.00. WAM puts F1 ahead, because its high peak-season score more than offsets its low winter score.
Under WHM: F1 = 3 / (1/2 + 1/4 + 1/8) = 3.43. F2 = 3 / (1/3 + 1/4 + 1/5) = 3.83. WHM now puts F2 ahead; the ranking reverses completely.
| Fleet | WAM score | WAM rank | WHM score | WHM rank |
|---|---|---|---|---|
| F1 | 4.67 | 1 | 3.43 | 2 |
| F2 | 4.00 | 2 | 3.83 | 1 |
The result reads as follows. WAM fully offsets F1's low winter performance with its high peak-season performance and puts F1 ahead. WHM instead amplifies the low winter performance by taking its reciprocal, and puts the balanced F2 ahead. The same three numbers produce a fully reversed ranking depending on which aggregation view is chosen.
The company hesitates here: if winter performance is genuinely critical (for instance, if the contract sets a minimum delivery speed for winter months), F1's winter weakness should not be offset by its peak-season success. In that case, the ranking WHM gives is closer to the company's real view of risk than WAM's.
In the report: "Under the full-compensation assumption (WAM), F1 comes out ahead; but under WHM, which foregrounds the weakness in winter performance, F2 comes out ahead. F2 should be preferred if winter performance is contractually critical."
Source: This table is an illustrative example, constructed by DecisionMind to validate its WHM engine against WAM; it is not drawn from a specific paper. The engine reproduces the same results.
2. Election Logistics: Combining processing speed for vote-counting equipment selection
An election board will evaluate three vote-counting device proposals against three criteria (votes processed per minute, an error-rate score, a set-up-time score), all scored "higher is better". The board chose WHM because it considers it essential that devices never fall below a certain speed, even at peak load.
The method averages the three proposals' scores via their reciprocals. Suppose one proposal scores very low on set-up time but high on the other two criteria; WHM amplifies and punishes that low set-up score disproportionately, placing that proposal further behind than WAM would.
The board hesitates here: set-up time really is a critical constraint on election day, because polling stations must open at a fixed hour. WHM's harsh punishment is therefore not a flaw here but a feature that correctly reflects a real risk.
In the report: "Under WHM, the proposal with a weak set-up time falls markedly behind; this outcome fits election day's time constraint and should be taken as decisive in the final decision."
3. Care Home: Combining performance for a maintenance-staff service-provider selection
A care home operator will evaluate three outsourced maintenance service providers against three criteria (a service-continuity score, a staff-training-level score, an emergency-response-time score), all "higher is better". The operator preferred WHM because it considers it essential that a provider not be seriously weak on any single criterion.
The method combines the three providers' scores via WHM. Suppose one provider scores very low on emergency response time but high on the other two criteria; WHM pushes this provider markedly behind, whereas WAM applied to the same data might have left it in first place.
The operator hesitates here: emergency response time may be more critical to residents' safety than the other criteria. If WHM's harsh punishment of weakness on this criterion matches the operator's safety priority, WHM is the right choice; if it does not, WAM or the moderately severe WGM should be reconsidered.
In the report: "Under WHM, the provider with a weak emergency-response time falls markedly behind; this outcome is consistent with an assessment that treats resident safety as more critical than the other criteria."
4. What Not to Do
Had F1's winter score in the freight table been 0, WHM would have been undefined, because 1 divided by 0 cannot be computed; this is the risk of using WHM with scores at or very close to zero. A second error is placing WHM and WAM results side by side and drawing a blanket conclusion such as "WHM is always more reliable" 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 0.40-point gap between F1's and F2's WHM scores (3.43 against 3.83) as a minor numerical detail; this gap is a direct consequence of the weakness in winter performance and can be decisive where it relates to a critical constraint.
Sources
For the formulas behind the step, the intermediate tables and citation formats (BibTeX, RIS, APA), see the DecisionMind method page: decisionmind.app/library/whm
Bullen, P. S., Mitrinović, D. S., & Vasić, P. M. (1988). Means and Their Inequalities. D. Reidel Publishing (Springer). DOI: 10.1007/978-94-017-2226-1
Hardy, G. H., Littlewood, J. E., & Pólya, G. (1934). Inequalities. Cambridge University Press. ISBN: 978-0-521-35880-4 (no DOI)