Methods · Subjective weighting
B-WENSLO (Fuzzy WENSLO Method)
B-WENSLO converts the linguistic scores experts assign to criteria into triangular fuzzy numbers, then measures the disagreement among experts and derives criterion weight from that disagreement.
Base method's data type: Fuzzy
What Is the Method?
B-WENSLO is a weighting method for situations where a panel of experts rates criteria with linguistic terms such as "very important," "medium" or "unimportant," and these ratings are converted not into numbers but into fuzzy (triangular) numbers. Its output is a crisp weight vector that sums to one; it does not rank alternatives and does not evaluate options, it only computes the relative weight of criteria. Demir and Ulusoy (2024) proposed B-WENSLO by extending the crisp WENSLO method to work with triangular fuzzy numbers; the method is still new and its range of application remains limited.
The Philosophy Behind It
The idea behind crisp WENSLO is this: the more disagreement raters show on a criterion, the more that criterion discriminates between decisions, and the higher its weight should be. This is a relative of the "variability carries information" idea that underpins objective weighting methods such as Entropy and CRITIC. WENSLO captures this variability with two separate measures: the envelope shows how much the experts fluctuate relative to one another, and the slope shows how steep the average level is relative to that fluctuation. When the ratio of envelope to slope is high, the criterion carries rich information and its weight increases. B-WENSLO extends the same logic so that it works when the input is a linguistic or fuzzy expression rather than a number.
This carries one consequence: B-WENSLO is neither a fully subjective method, as AHP or BWM are, nor a fully objective one, as Entropy is. Its input is subjective because it rests on expert opinion; but its weighting logic is objective, because it looks at the data's own variability rather than at an expert declaring "this criterion matters." When experts agree completely on a criterion, the method cannot compute a weight for it. This is not a flaw but the natural consequence of the logic that "if everyone says the same thing, this criterion carries no discriminating information."
How It Works
The method proceeds through eight steps.
First, linguistic scoring. Every expert chooses a label from a nine-level linguistic scale (from "definitely low" to "definitely high") for every criterion. That label is converted into a triangular fuzzy number with a lower, middle and upper bound.
Second, scale equalisation. Each criterion column is equalised by dividing it by its own sum, so that every criterion ends up on the same scale and can be compared with the others. This step needs no direction sign, because every criterion measures "importance" in the same direction.
Third, defuzzification. The equalised triangular fuzzy values are reduced to a single number through a weighted average that gives more weight to the midpoint than to the lower and upper bounds. From this step on, the calculation proceeds with crisp numbers.
Fourth, class interval. For every criterion, the gap between the highest and lowest defuzzified value across experts is divided into a fixed step, set by a rule that depends on the number of experts (Sturges' rule). This fixed step becomes the common unit for the next two measures.
Fifth, slope. The mean of the criterion's defuzzified values is divided by this fixed step to obtain the "slope." Slope shows how steep the average level is relative to the spread.
Sixth, envelope. The straight-line distances between experts' consecutive defuzzified values, taken at this fixed horizontal step, are summed. This total shows how much the experts fluctuate, that is, how much they disagree, on that criterion.
Seventh, ratio. The envelope is divided by the slope. A larger ratio means the criterion carries richer information and should therefore receive a higher weight.
Eighth, normalisation. The ratios are divided by their own sum to become criterion weights that total one.
The formulas behind each step are given on the DecisionMind B-WENSLO method page; this card carries no formulas.
How to Read the Output
The weight shows not how important a criterion "really" is, but how much the experts diverged on it. A high weight means the experts scored this criterion visibly differently from one another, and that difference carries rich information. A low weight means the experts were nearly unanimous on this criterion; it does not show the criterion is unimportant, only that it was not discriminating within this expert group. A weight close to zero should be read not as "drop this criterion" but as "expert opinion on this criterion was already settled, so weight moved to the other criteria."
Thus instead of writing:
"B-WENSLO showed that this criterion is the most important"
the report should read:
"The experts' linguistic scores diverged most on this criterion; that divergence converted into the highest weight in B-WENSLO"
Data Type and Inputs
B-WENSLO works with fuzzy (triangular fuzzy number) data: every expert–criterion cell is a lower–middle–upper triple derived from a linguistic label. DecisionMind holds no separate registered extension member within B-WENSLO's own family; its crisp counterpart, WENSLO, stands as a separate method. You need at least two experts, at least two criteria, a shared nine-level linguistic scale, and a label for every expert–criterion cell. B-WENSLO produces weights, it does not require weights supplied from outside. Five to fifteen criteria and three to ten experts work comfortably. If all experts give the same label on a criterion, that criterion's class interval falls to zero and the slope becomes undefined; this must be checked in the input beforehand.
When to Use It, When Not To
B-WENSLO is a suitable choice when expert opinion has been collected in linguistic terms, converting those terms into numbers is difficult, and the disagreement among experts is itself meant to be reflected in the weight as information. If experts already give direct numerical scores or can make pairwise comparisons, methods that lose less information are preferable. If the panel is expected to reach full consensus on a criterion and that consensus is meant to be rewarded, B-WENSLO is unsuitable, because it cannot compute a weight for full consensus.
Expert opinion linguistic/fuzzy, disagreement should carry information → B-WENSLO
Expert opinion numerical pairwise comparison → AHP, BWM, FUCOM
Data crisp (numerical), weight should come from the data itself → Entropy, CRITIC
The actual goal is group consensus, round-by-round opinion gathering → Delphi
Strengths
B-WENSLO is one of the few weighting methods that works directly with linguistic/fuzzy data; unlike AHP, it needs no pairwise comparison matrix, each expert gives a single label per criterion, and the computational load is low. By explicitly feeding inter-expert disagreement into the weight, it builds in the intuition that "if everyone says the same thing, this criterion is not discriminating," information that simple averaging methods overlook.
Weaknesses
The method is sensitive to expert order. Because the envelope calculation sums the differences between consecutive experts, the order in which experts are listed can change the result; Demir and Ulusoy (2024) note this point themselves. This is a fragility different from, but similar to, rank reversal in TOPSIS: input order should not be part of the decision, yet it affects the outcome. A second limitation is that the method breaks down when all experts agree on a criterion. A third is that the nine-level linguistic scale is borrowed from Božanić et al. (2021); whether this scale fits every application context still needs separate testing.
Common Mistakes
The most common mistake is fixing the expert order arbitrarily without noticing that the result is sensitive to it. Expert order should be stated in the report, and where possible the result should be checked against a few different orderings to see how much it shifts. A second mistake is running the analysis without noticing that all experts gave the same label on a criterion; in that case the slope stays undefined and the engine is expected to raise an error, not to paper over it with a silent default value. A third mistake is reading a low weight as "unimportant criterion"; a low weight usually means "the experts agreed on this criterion." A fourth mistake is letting different expert groups use different linguistic scales (say, one five-level and one nine-level) and then merging the results into a single table.
The governing principle is this:
A B-WENSLO weight measures how much the experts diverged on a criterion, not how important that criterion is; confusing the two produces a misreading.
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 DecisionMind's own validation example; the rest are illustrative constructions.
1. Method Validation: Two experts, two criteria, a symmetric test (DecisionMind's validation example)
The simplest way to test B-WENSLO's engine is a symmetric input whose answer is known in advance. Two experts rate two criteria: the first expert calls C1 "definitely high" and C2 "medium"; the second expert does the exact opposite, calling C1 "medium" and C2 "definitely high."
| Expert | C1 | C2 |
|---|---|---|
| E1 | Definitely high | Medium |
| E2 | Medium | Definitely high |
This table sets up a perfect symmetry between the criteria: swapping C1 and C2 leaves the table unchanged. The method equalises each column, defuzzifies, finds the class interval, and computes slope and envelope. Because of the symmetry, the envelope found for C1 (approximately 0.364) and the slope (approximately 6.19) come out identical for C2; the ratio (approximately 0.059) is likewise equal for both criteria.
| Criterion | Weight |
|---|---|
| C1 | 0.500 |
| C2 | 0.500 |
The result is a direct reflection of the table's symmetry: since there is no structural difference between the two criteria, the weights come out equal too. This is an internal-consistency check showing that the B-WENSLO engine behaves true to its own definition; it is not taken from a real application.
In the report: "On the symmetric test input, the weights B-WENSLO produced (0.500 / 0.500) match the expected closed-form result exactly; this confirms that the engine runs the envelope/slope/ratio chain in line with the definition."
Source: DecisionMind_v3 internal validation fixture (2026); the method's definition follows Demir and Ulusoy (2024). This case is an illustrative validation example, not taken from a published application.
2. Library Science: Weighting digitisation criteria at a university library
A university library must decide which criterion to prioritise in its project to digitise rare holdings. Four criteria are set: the item's risk of physical deterioration, researcher demand frequency, digitisation cost, and copyright status. Five librarians each choose a label from the nine-level linguistic scale for every criterion.
The method equalises each criterion's column, defuzzifies it, and measures the disagreement among the five librarians' opinions. Suppose the librarians are largely in agreement on the deterioration-risk criterion (all say "definitely high"), but opinions on the cost criterion range from "medium" to "definitely low." B-WENSLO then gives the cost criterion a higher weight than deterioration risk, because there is more disagreement on the cost criterion.
The library director hesitates here: deterioration risk received a low weight because everyone agreed on it, but that does not mean the criterion is unimportant; on the contrary, it means consensus on it already exists. The director must explain to the team that a low-weighted criterion should not be dropped from the project, it merely appears low in the weighting table.
In the report: "Disagreement among the librarians' opinions was greatest on the cost criterion, so B-WENSLO assigned it the highest weight; the low weight on deterioration risk shows not that the criterion is unimportant but that consensus already existed among the librarians."
3. Textiles: Weighting supplier-selection criteria at a factory
A textile factory must set the weight of the criteria it will use to evaluate cotton suppliers. There are three criteria: delivery time, quality consistency, and price flexibility. Seven members of the procurement team each give a linguistic score for every criterion.
The method equalises the columns, defuzzifies them, and computes the envelope and slope of the seven members' opinions on each criterion. Suppose opinions on quality consistency are widely scattered: some say "definitely high," others "medium." On delivery time, by contrast, the team is nearly unanimous. The result gives quality consistency the highest weight.
The team hesitates here: two of the seven notice that the ranking changes depending on which member the list starts and ends with, because the envelope calculation sums the differences between consecutive opinions. The team reorders the survey and recomputes the result; it finds a small but visible shift in the weights. The report must therefore state explicitly in which order the calculation was made.
In the report: "Disagreement among procurement team members was greatest on the quality-consistency criterion, and this criterion received the highest weight; the result is sensitive to the order in which the survey was collected, so that order has been fixed in the report."
4. What Not to Do
In the symmetric test table of the first case, changing the order in which the two experts' labels are shown, and assuming "the result will come out the same regardless," is wrong; the envelope calculation is order-sensitive, and the intermediate steps (such as the envelope of approximately 0.364) can change once the order changes. A second error is running the analysis without noticing that all experts gave the same label on a criterion, and mistaking the engine's resulting division-by-zero error for a "software bug"; this is in fact a sign that the input fails to meet B-WENSLO's precondition. A third error is dropping a low-weighted criterion from the report entirely as "unimportant"; in B-WENSLO, a low weight usually means consensus, not unimportance.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/b-wenslo
Demir, G., & Ulusoy, S. K. (2024). Bulanık WENSLO Yöntemi ile Kriter Ağırlıklarının Belirlenmesi: Dijital Bankacılık Uygulaması. Computer and Decision Making — An International Journal, 1, 211-234. (no DOI)
Pamucar, D., Ecer, F., Gligorić, Z., Gligorić, M., & Deveci, M. (2024). A Novel WENSLO and ALWAS Multicriteria Methodology and Its Application to Green Growth Performance Evaluation. IEEE Transactions on Engineering Management, 71, 9510-9525. DOI: 10.1109/TEM.2023.3321697
Demir, G. (2025). Bulanık WENSLO Yöntemi. In G. Demir (Ed.), Sosyal Bilimlerde Stratejik Karar Verme: Çok Kriterli Karar Verme Yöntemleri ile Uygulamalar (Chapter 2). Özgür Yayınları. DOI: 10.58830/ozgur.pub768 (DOI covers the whole book; the chapter has no separate DOI)
Demir, G. (2026). WENSLO: Weights by envelope and slope for multi-attribute decision-making. In Encyclopedia of Multi-Attribute Decision Making (MADM). Elsevier. DOI: 10.1016/b978-0-443-33275-3.00061-0
Božanić, D., Tešić, D., Marinković, D., & Milić, A. (2021). Modeling of neuro-fuzzy system as a support in decision-making processes. Reports in Mechanical Engineering, 2(1), 222-234. DOI: 10.31181/rme2001021222b