Methods · Subjective weighting
Fuzzy Delphi
Fuzzy Delphi asks experts not for a single number but for a triangular range in the form "at least, most likely, at most"; it pools the opinion across experts by combining these triangles and reduces them to a single central value that becomes a weight.
Base method's data type: Classical
What Is the Method?
Fuzzy Delphi is an extension of classical Delphi and a method that converts expert opinion on criterion importance into a weight. Its output is a weight vector summing to one; it does not rank alternatives, and it works independently of ranking. In classical Delphi, every expert gives a single score for a criterion; in Fuzzy Delphi, an expert may instead give this score as a range, because even the uncertainty inside a single expert's own mind cannot be fully captured by one number. Introduced in Kaufmann and Gupta's 1988 book, the method has a wide range of applications, from criterion weighting to technology foresight, from education-programme evaluation to health-policy prioritisation.
The Philosophy Behind It
The problem classical Delphi solves is disagreement between experts: as rounds proceed, experts converge on one another. Fuzzy Delphi adds a second layer of uncertainty to this. An expert may say, about a criterion, not "exactly 7" but "between 6 and 9, probably 7"; this is not the expert's indecision but an ambiguity inherent in the nature of judgement itself. The method handles these two kinds of uncertainty separately. It first pools each expert's own triangular range, then looks at how wide the range between experts is (whether they have converged), and finally reduces a wide triangle to a single number.
This carries a consequence: Fuzzy Delphi keeps the uncertainty in expert opinion hidden at the start of the calculation, carries it right to the end, and reduces it to a single number only when converting it into a weight. Reversing this order, reducing each expert's range to a single number first and then averaging, defeats the method's actual purpose, which is not to lose uncertainty too early.
How It Works
The method proceeds through four steps.
First, expert assessment. Every expert gives every criterion a triangular fuzzy number: a worst case, a most likely value, a best case. If an expert feels no uncertainty, all three can be made the same number; in that case the triangle collapses to a single point and behaves like a crisp score.
Second, combining across experts. For every criterion, the smallest of all experts' worst-case values and the largest of their best-case values are taken; the most-likely values are combined through a geometric mean. This produces a single group triangle for each criterion. If the experts have given a single crisp number (no triangles), this step reduces to a geometric mean.
Third, checking for consensus. If the width of the group triangle (the gap between its largest and smallest end) falls below a pre-set threshold, consensus is considered reached. If the threshold is exceeded, a new Delphi round is needed; this card describes the single-round combination step.
Fourth, defuzzification and conversion to weight. The group triangle's three corners are averaged to reduce it to a single number (the centroid method). These figures are then divided by their own total to convert them into criterion weights summing to one.
The formulas behind each step are given on the DecisionMind Fuzzy Delphi method page; this card carries no formulas.
How to Read the Output
The weight is the experts' triangular ranges combined and reduced to a single number; this single figure no longer shows the uncertainty that lay beneath it. If two criteria's weights are close (even 0.365 against 0.365, exactly equal), this does not mean the experts truly saw these two criteria as equally important; the group triangles' widths may differ, and this width is lost in the final weight. A high weight does not mean "certainly important" but "the central value the experts reached in this round is high."
Thus instead of writing:
"Fuzzy Delphi measured this criterion's importance precisely"
the report should read:
"The centre of the experts' triangular ranges has given this criterion the highest weight; the width of the ranges (the tightness of the consensus) must be reported separately"
Data Type and Inputs
Fuzzy Delphi fundamentally works with fuzzy (triangular) data, but it also accepts a crisp number if an expert wants to give one; in that case the triangle collapses to a single point. In DecisionMind's Delphi family, Fuzzy Delphi is the fuzzy member alongside classical Delphi; within this two-member family, Fuzzy Delphi itself has no further extension. You need: at least two experts, at least two criteria, a triangular (or crisp) assessment from every expert for every criterion, and a consensus threshold. The method produces weights, it does not ask for weights from outside. Three to twelve criteria are typical, and at least five experts are typical for the statistical summary to be meaningful.
When to Use It, When Not To
If experts struggle to give a single number for a criterion, say "roughly around this much, but I am not certain," and you want to factor this uncertainty in rather than ignore it, Fuzzy Delphi is a suitable choice. If experts already give clean, single-number scores and the only difference between them is group consensus, classical Delphi is sufficient; adding a fuzzy range adds unnecessary complexity. If experts can make a pairwise comparison in a single round, faster methods such as AHP, BWM or LBWA give a quicker result.
Expert uncertainty is expressed as a range, round-by-round consensus is sought → Fuzzy Delphi
Experts give a precise score, only group consensus matters → Classical Delphi
No time for round-by-round feedback, pairwise comparison is sufficient → AHP, BWM, LBWA
What is actually needed is not group consensus but the data's own variability → Entropy, CRITIC
Strengths
Fuzzy Delphi's greatest strength is that it makes visible, separately, two different sources of uncertainty in expert opinion, disagreement between experts and an expert's own internal indecision. Classical Delphi measures only the first; Fuzzy Delphi carries both together and reduces them to a single number only at the last step. When an expert wants to say "I do not know exactly, but within this range," it does not force this into a single number, and this in turn allows a more honest collection of input, particularly on new or little-known topics.
Weaknesses
The method's most contested point is the defuzzification step. When a fuzzy range is pooled and finally reduced to a single number, part of the information the range carried is lost in the report; some researchers criticise this as the method's "creating fuzziness at the start only to discard it at the end" (Saffie, Shukor and Rasmani, 2016). Second, the choice of the consensus threshold is subjective and carries the risk of being adjusted to fit the result if it is not fixed before the analysis begins. Third, taking the smallest and largest ends when combining across experts can let a single expert at one extreme widen the group range more than it should. Fourth, like classical Delphi, this method carries a cost in time and participant fatigue; when more than one round is required, the process can take weeks.
Common Mistakes
The most common mistake is collecting a single number instead of a triangular range from experts and then calling it "Fuzzy Delphi" after the fact; if uncertainty was never genuinely expressed as a range, the method's real contribution never comes into play. A second mistake is setting the consensus threshold after the analysis, by looking at the results. A third mistake is reporting the defuzzified weight without ever stating the width of the triangle beneath it (how tight the consensus is); two criteria can end up with the same weight even though one comes from a wide consensus and the other from a narrow one. A fourth mistake is leaving a single expert's extreme value untouched at the combination step, as is, without questioning how much it is skewing the group range.
The governing principle is this:
Fuzzy Delphi's weight is a central summary of the experts' triangular ranges; the wider the range behind this summary, the more fragile the weight, and the report must show this.
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 validation example; the others are constructed.
1. Method Validation: Three experts, a single-round three-criterion example (DecisionMind's validation example)
Three experts score three criteria on a 0-10 scale, in this round with a single crisp number rather than a triangle; that is, every expert's own uncertainty is taken as zero, and only the opinion across experts is combined.
| Expert | C1 | C2 | C3 |
|---|---|---|---|
| U1 | 3 | 5 | 4 |
| U2 | 5 | 3 | 2 |
| U3 | 4 | 4 | 3 |
The method takes the geometric mean of the three experts' scores for every criterion: the cube root of (3×5×4) for C1, the cube root of (5×3×4) for C2, the cube root of (4×2×3) for C3. Because the experts gave a single number, the group triangle collapses to this single central value; the centroid comes out equal to the same figure. Finally, these three central values are divided by their own total to convert them into weights.
| Criterion | Central value | Weight |
|---|---|---|
| C1 | 3.915 | 0.365 |
| C2 | 3.915 | 0.365 |
| C3 | 2.884 | 0.269 |
The result reads as follows. C1 and C2 receive the same weight because the geometric mean of the experts' scores comes out equal for both; C3 is both scored lower and shows less spread among the experts, and it is left with a lower weight. In this case, because the experts gave a single number, the method's actual strength, "carrying a range," is not in play; this is a test case showing the engine also works consistently with crisp input.
The team hesitates here: a geometric mean calculated from three experts can shift noticeably once a fourth expert is added. Also, because the experts gave a single number here rather than a range, the "width of consensus" information expected from a genuine Fuzzy Delphi application is not produced in this case.
In the report: "The geometric mean of the three experts' single-number scores has given C1 and C2 an equal weight (0.365) and C3 a lower weight (0.269); this case shows the engine's consistency with crisp input, not the width of expert ranges."
Source: Figures based on the method introduced by Kaufmann and Gupta (1988); this case is an illustrative validation example, not the book's own numerical example. The figures were produced and verified by running DecisionMind's engine.
2. Public Sector: Weighting smart-city investment criteria for a municipality
A metropolitan municipality will set the prioritisation criteria for its smart-city investments. There are four criteria: contribution to citizen satisfaction, implementation cost, technical maturity and environmental impact. A panel of eight experts gives every criterion a triangular importance score in the form "at least, most likely, at most"; some experts report narrow ranges (for example, 6-7-8), others wide ones (for example, 3-6-9).
The method builds a group triangle for every criterion by taking the smallest lower end and the largest upper end across the experts and the geometric mean of the most-likely values. For citizen satisfaction, the experts have both given high scores and kept their ranges narrow; for cost, the scores are moderate but the ranges are wide, because the experts think cost can vary greatly by project.
The municipality hesitates here: even though citizen satisfaction and cost end up with similar weights after defuzzification, one comes from a narrow consensus and the other from a wide one. The municipality decides to add a "less certain" note in the report next to the wide-ranged cost criterion's weight.
In the report: "The citizen-satisfaction criterion has both scored highly and been derived from a narrow expert range; the cost criterion carries a similar weight but rests on a wider spread of opinion among the experts."
3. Agriculture: Weighting irrigation-technology selection criteria for a cooperative
An agricultural cooperative will determine the weight of the criteria used in choosing the irrigation technology to recommend to its members. There are three criteria: water saving, installation cost and ease of maintenance. Twelve producers each give a triangular importance score for every criterion.
In the first round, a wide range of opinion emerges for the water-saving criterion; producers newly switching to the irrigation technology see this criterion as very important, while those who have long used the same system find it less important. The group triangle's width exceeds the consensus threshold, and a second round is required. In the second round, having seen one another's views, the producers narrow their ranges and the threshold is met.
The cooperative hesitates here: whether the rapid narrowing of the ranges in the second round reflects a genuine change of opinion or group pressure is debated. The cooperative decides not to finalise the result without a third, confirmatory round.
In the report: "The water-saving criterion received the highest weight at the end of the second round, and the group triangle's width fell below the accepted threshold; because of the rapid narrowing, a third confirmatory round has been planned."
4. What Not to Do
In the first case's three-expert example, collecting a single number from experts instead of a range and then presenting it as "fuzzy" is wrong; in that case, the method's real contribution, carrying a range, never comes into play. A second error is reporting the defuzzified weight without ever stating the width of the group triangle; C1 and C2 receiving equal weight does not mean the consensus behind the two is equally tight. A third error is feeding a single expert's excessively wide range (for example, 1-5-10) into the combination step without data cleaning, widening the group range more than it should be.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/fuzzy-delphi
Kaufmann, A., & Gupta, M. M. (1988). Fuzzy Mathematical Models in Engineering and Management Science. North-Holland, Amsterdam. (no DOI)
Ishikawa, A., Amagasa, M., Shiga, T., Tomizawa, G., Tatsuta, R., & Mieno, H. (1993). The max-min Delphi method and fuzzy Delphi method via fuzzy integration. Fuzzy Sets and Systems, 55(3), 241-253. DOI: 10.1016/0165-0114(93)90251-c
Saffie, N. A. M., Shukor, N. A. M., & Rasmani, K. A. (2016). Fuzzy Delphi method: Issues and challenges. 2016 International Conference on Logistics, Informatics and Service Sciences (LISS), 1-7. DOI: 10.1109/liss.2016.7854490
Roldán López de Hierro, A. F., Sánchez, M., Puente-Fernández, D., Montoya-Juárez, R., & Roldán, C. (2021). A fuzzy Delphi consensus methodology based on a fuzzy ranking. Mathematics, 9(18), 2323. DOI: 10.3390/math9182323