Methods · Ranking
LMAW (Logarithm Methodology of Additive Weights)
LMAW first standardises every cell in a way sensitive to both direction and magnitude, then passes it through a logarithmic transformation. It then sums these values through a weighted, bounded aggregation function to rank the alternatives. Its purpose is to stop extreme values from dragging the ranking to excess.
Base method's data type: Classical
What Is the Method?
LMAW is a ranking method for when you have a decision table filled with numbers and want the alternatives placed in a single order. Its output is a total utility score for every alternative and a rank built on that score. Pamučar, Žižović, Biswas and Božanić proposed it in 2021, with an application to logistics service provider selection. It offers an alternative to classical weighted-sum methods such as SAW and WASPAS: it first moves cell values onto a logarithmic scale, then passes them through a bounded aggregation function (in the 0–2 range). Like SAW and TOPSIS, it does not produce weights; it takes them from outside. Being a recent method, its literature is still limited. Its main areas of application are supplier and logistics service provider selection.
The Philosophy Behind It
The idea behind LMAW is to keep the logic of a weighted sum, SAW's philosophy, while limiting how far extreme values in the raw data can drag the ranking. In a classical weighted sum, a very large number on one criterion can dominate the result even after normalisation. LMAW first standardises every cell according to direction information, taking the best or worst value as the reference depending on the criterion's direction. It then moves this standardised value onto a logarithmic scale. A logarithm shrinks large differences while leaving small differences comparatively more visible, compressing the data. In the final step these compressed values are passed, together with the weight, through a function bounded between 0 and 2 and summed. This bound stops a single criterion from inflating the total score without limit.
A consequence follows: LMAW, like TOPSIS and SAW, is compensatory. A weakness on one criterion can be offset by strength on another, because every criterion's contribution is combined into a single total score. What sets LMAW apart from SAW is how this compensation happens. In SAW contributions are directly proportional. In LMAW, because of the logarithmic compression and bounded summation, a very large advantage translates into a proportionally smaller contribution. Where no compromise on a criterion can ever be accepted, that is, where a non-compensatory logic is needed, LMAW's philosophy will not match the decision's own.
How It Works
The method proceeds through four steps.
First, direction-sensitive standardisation. Every cell is standardised differently depending on the criterion's direction. In a "higher is better" criterion, values are scaled against the largest value; in a "lower is better" criterion, against the smallest. This step is a form of standardisation distinct from TOPSIS's vector normalisation and is specific to LMAW.
Second, the logarithmic transformation. Every standardised value is converted into a logarithm normalised against the product of the values in its own column. This step shrinks large differences and moves the data onto a common, bounded scale, preventing extreme values from gaining disproportionate weight in the next step.
Third, weighted aggregation. The logarithmic value is passed, together with the criterion's weight, through a function bounded between 0 and 2. This function amplifies the contribution of a heavily weighted criterion while stopping a single cell from inflating the total score without limit.
Fourth, summation and ranking. The compressed values across all criteria for each alternative are summed to give a single total utility score. Alternatives are ranked from the highest score to the lowest.
The formulas behind each step, the intermediate tables and citation formats are given on the DecisionMind method page; this card carries no formulas.
How to Read the Output
The total utility score tells you how high a weighted, logarithmically aggregated total an alternative achieved relative to the others in this particular analysis, and nothing more. The score itself is not a directly interpretable proportion, as it is in SAW; it is a scale specific to LMAW. It does not sit between 0 and 1, and it cannot be compared with scores from a different analysis, because standardisation is built anew from each analysis's own alternative set. The ranking can change if the alternative set or the weights change.
Thus instead of writing:
"LMAW found the best supplier"
the report should read:
"With these weights and this alternative set, the alternative with the highest total utility is this one; the ranking is sensitive to the weight on these criteria"
Data Type and Inputs
LMAW works with crisp data: a single number per cell, accepting neither zero nor negative values, because the logarithmic transformation requires a positive value. You need alternatives in rows, criteria in columns, a positive number in every cell with no empty cells; direction information for every criterion; and criterion weights summing to 1. LMAW does not produce weights, it requires them; you can derive them from expert opinion (AHP, BWM, SWARA) or from the data itself (Entropy, CRITIC, MEREC, DEMATEL). DecisionMind holds three LMAW members alongside the base method, including fuzzy extensions. A minimum of two alternatives and two criteria is required; three to twelve criteria work comfortably.
When to Use It, When Not To
LMAW is a suitable choice where your criteria can be measured numerically, your table has no gaps, you accept that a weakness on one criterion may be offset by strength on another, and your data carries some very large extreme values on certain criteria. If you do not want these extreme values to drag the ranking to excess, LMAW limits this. Its typical fields are supplier and logistics service provider selection; its logic does not depend on the field.
It should not be used in the following situations. Where no compromise is acceptable on a criterion, LMAW is unsuitable, because it is compensatory like TOPSIS and SAW and carries the same limitation. Where your data contains zero or negative values it is also unsuitable, because the logarithmic transformation cannot accept this; the data must first be transformed. Where criteria are strongly linked, this needs handling first.
Numerical table, compensation accepted, you want to limit the effect of extreme values → LMAW
No problem with extreme values, a simple weighted sum will do → SAW, WASPAS
No compromise allowed on one criterion, elimination logic is needed → the ELECTRE family
Not a ranking but weights are needed → AHP, BWM, SWARA (subjective); Entropy, CRITIC, MEREC (objective)
Data contains zero/negative values → transform the data first, or choose a method that does not require a logarithm (TOPSIS, SAW)
Strengths
LMAW's most important strength is that it limits, through logarithmic compression, how far extreme values in the raw data can drag the ranking to excess. This is particularly useful in data sets where criteria carry a large difference in magnitude, for instance where one criterion sits at an order of 10 while another sits at an order of 10,000. The computational burden is small and the steps can be followed on the table. The weighted aggregation function keeps the result within a bounded range, making it harder than in SAW for a single criterion to dominate the total score disproportionately.
Weaknesses
Its limitations stem from this same structure. First, because the method was proposed in 2021, its literature is still limited; it lacks the breadth of independent scrutiny built up around rank reversal and sensitivity to criterion count that TOPSIS or the ELECTRE family enjoy. Second, the logarithmic transformation does not accept zero or negative values; a data set containing these must first be transformed. Third, the assumption of full compensation is the same as in SAW and TOPSIS: a serious weakness on one criterion can be papered over by others. Fourth, criteria are treated as independent; where criteria influence one another, weight can be implicitly counted twice (Božanić, Pamučar, Milić, Marinković and Komazec, 2022).
Common Mistakes
The most common mistake is applying LMAW without noticing a zero or negative value in the data set; the logarithmic transformation is then undefined. A second mistake is marking criterion direction wrongly. The standardisation step works differently by direction: "higher is better" is scaled against the largest value, "lower is better" against the smallest. A direction error therefore corrupts the ranking directly. A third mistake is assigning equal weights without justification; this is itself a claim that must be defended in the report. A fourth is comparing LMAW's score directly with a score produced by SAW or TOPSIS; each method's scale is its own. A fifth is expecting two methods to give the same ranking on the same data set without recognising that LMAW reflects an extreme advantage on a single criterion more mildly than SAW does.
The governing principle is this:
An LMAW result is a logarithmically compressed summary of the directions, weights and alternative set you chose. If you want to limit the effect of extreme values in the data, this is an advantage. But if one of the inputs is contested, the ranking stays contested too.
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 drawn from DecisionMind's own validation record and is an illustrative example; the rest are illustrative constructions.
1. Logistics: A business choosing among three suppliers (illustrative example)
A business will choose among three suppliers. Three criteria apply: delivery-speed score and product-quality score ("higher is better"), and unit cost ("lower is better"). The business set its weights so that delivery speed carries the most (0.40), product quality comes next (0.35), and cost carries the least (0.25).
| Supplier | Delivery speed | Product quality | Unit cost |
|---|---|---|---|
| T1 | 3 | 5 | 4 |
| T2 | 5 | 3 | 2 |
| T3 | 4 | 4 | 3 |
| Direction | higher is better | higher is better | lower is better |
| Weight | 0.40 | 0.35 | 0.25 |
The method first standardises every cell according to its direction, moves it onto a logarithmic scale, and then passes it through the weighted aggregation function and sums it.
| Supplier | Total utility score | Rank |
|---|---|---|
| T2 | 2.252 | 1 |
| T3 | 2.212 | 2 |
| T1 | 2.166 | 3 |
The result reads as follows. T2 has the highest delivery speed and the lowest cost, but the lowest score on product quality. Despite this, it takes first place because it is strong on the two most heavily weighted criteria: delivery speed and cost together carry a combined weight of 0.65, and this weighted aggregation carries T2 to the top. T3 sits at a mid-level on every criterion and takes second place. T1 has the highest product quality but comes third, because product quality's weight (0.35) is lower than delivery speed's (0.40), and T1 has the lowest delivery speed.
The business's hesitation: the gap between T2 and T3 is small (2.252 − 2.212 = 0.040). Whether raising the product-quality weight and lowering the delivery-speed weight would flip this ranking is a question that should be tested before the weights are finalised. T2's weakness on product quality, its lowest score of 3, has also fed through into the total score only to a limited degree, because of LMAW's compensatory structure. If quality falls below a threshold, say a minimum acceptable quality limit, LMAW does not capture this on its own; such a limit, if one exists, must be handled separately.
In the report: "With the weights given, T2 has the highest total utility among the suppliers (2.252); the gap to T3 (2.212) is small and sensitive to the weights on delivery speed and product quality. T2's weakness on product quality should be assessed separately if the business has a minimum quality threshold."
Source: An illustrative validation example prepared for DecisionMind's LMAW engine (based on the method of Pamučar, Žižović, Biswas and Božanić, 2021; not the paper's own numerical example). The total utility scores were independently calculated in Python by this card's author (T1=2.1659; T2=2.2519; T3=2.2117); DecisionMind's internal manifest audit confirms the same ranking and the same figures to a tolerance of 1e-6.
2. Agriculture: A cooperative's choice of tractor model
An agricultural cooperative will choose among three tractor models. Four criteria apply: engine power and fuel efficiency ("higher is better"), and purchase price and annual maintenance cost ("lower is better"). The cooperative set its weights by member vote, giving the highest weight to fuel efficiency.
The method standardises the three models by direction, moves them onto a logarithmic scale, and sums them through the weighted aggregation. Suppose the model with the most powerful engine also has the highest price and the highest maintenance cost, with mid-level fuel efficiency. The result places first the model that is balanced on fuel efficiency and price, rather than the one with the most powerful engine.
The cooperative's hesitation: the fact that the most powerful model falls behind may clash with some members' expectations of "power". It should be clearly reiterated that the weights were set by vote and that fuel efficiency was given priority weight. If there is also a strong relationship between price and maintenance cost, for instance if the more expensive model generally needs less maintenance, treating these two criteria as independent could affect the result.
In the report: "With the weights set by the members, the model balanced on fuel efficiency and price has come out first. The model with the most powerful engine falls behind because of its high price and maintenance cost. The possible relationship between price and maintenance cost should be assessed separately."
3. Human resources: A company's promotion assessment for field sales representatives
A company will assess three candidates from its field sales team for promotion to regional manager. Three criteria apply: annual sales-target achievement rate and customer satisfaction score ("higher is better"), and number of customer complaints ("lower is better"). The human resources unit has given weight predominantly to sales performance.
The method standardises the three candidates by direction, moves them onto a logarithmic scale, and sums them. Suppose the candidate with the highest sales rate has also received the most complaints, with mid-level customer satisfaction. The result places first a candidate with a slightly lower sales rate but fewer complaints and higher satisfaction, because the gap in complaint numbers translates into a proportionally larger penalty than the gap in sales rate.
The human resources unit's hesitation: the candidate with the highest sales figure dropping to second place may raise the question "why wasn't the top seller promoted". The answer is that, despite LMAW giving high weight to sales performance, the large gap in complaint numbers has affected the total score. This is a computational choice and should be explained clearly to the team before the promotion decision. In addition, the number of complaints being an absolute figure may not account for differently sized customer portfolios; measuring it as a rate (complaints per customer) might be fairer.
In the report: "With the weights set, the candidate with low complaints and high satisfaction has come out first; the candidate with the highest sales rate is second because of the gap in complaint numbers. Whether the complaint count has been normalised against the size of the customer portfolio should be checked separately."
4. What Not to Do
Had the unit cost criterion in the supplier table been marked "higher is better" by mistake, the most expensive supplier would also be treated as advantaged on this criterion, and the result would become meaningless because of the direction error. A second error is entering a zero or negative value into a cell in the table. LMAW's logarithmic transformation is then undefined and the engine should raise an error; masking the situation with "a small number close to zero" is wrong. A third error is comparing T2's score of 2.252 directly with a score produced by SAW or TOPSIS and saying "LMAW gave a better/worse result". Every method's score scale is its own; the two cannot be compared.
Extensions: for different data types
LMAW has 2 extensions in the library. Same decision logic, different data type: if your data is not a classical number, read the relevant data type card, then open that member.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/lmaw
Pamučar, D., Žižović, M., Biswas, S., & Božanić, D. (2021). A new logarithm methodology of additive weights (LMAW) for multi-criteria decision-making: Application in logistics. Facta Universitatis, Series: Mechanical Engineering, 19(3), 361–380. DOI: 10.22190/FUME210214031P
Božanić, D., Pamučar, D., Milić, A., Marinković, D., & Komazec, N. (2022). Modification of the Logarithm Methodology of Additive Weights (LMAW) by a Triangular Fuzzy Number and Its Application in Multi-Criteria Decision Making. Axioms, 11(3), 89. DOI: 10.3390/axioms11030089
Demir, G., Pamučar, D., & Simić, V. (2026). LMAW: Logarithm methodology of additive weights for multi-attribute decision-making. In: Encyclopedia of Multi-Attribute Decision Making (MADM) (pp. 479–488). Elsevier. DOI: 10.1016/b978-0-443-33275-3.00044-0