Extension card · Fuzzy
Fuzzy CRITIC
Fuzzy CRITIC is the form of CRITIC used when criterion values are given as triangular fuzzy numbers. It runs crisp CRITIC separately on each of the triangle's three corners and averages the three resulting weight vectors into a single fuzzy-derived weight vector.
Base method
CRITIC →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Fuzzy →
What this data type is, when to use it, how to write it in a cell: the family's full account is here.
What Changes from the Base Method?
Three things change; CRITIC's "spread × distinctiveness" logic does not.
Cells. In crisp CRITIC every cell is a single number. Here every cell is three numbers: lowest, most likely, highest. The output is still a weight vector, not a ranking; this is CRITIC's own identity, and it does not change in fuzzy form either.
Scale equalisation, spread and correlation. Crisp CRITIC runs these three steps (min–max scaling, standard deviation, correlation) once, on a single crisp table. Here the same five steps (scale equalisation, spread, correlation, information content, weight) are run three times, independently of one another: once on a crisp table built only from the triangles' lowest components, once on a table built only from the most likely components, and once on a table built only from the highest components. None of the three calculations sees the others' result; each is crisp CRITIC in its own corner.
Result and defuzzification. The three weight vectors produced by the three independent calculations (the lowest corner's weights, the most likely corner's weights, the highest corner's weights) are averaged criterion by criterion, and the sum is renormalised to 1; this is DecisionMind's defuzzification step, carried out only after the three independent calculations are complete. The triangle's width (the gap between the highest and lowest) does not enter the calculation directly; only the crisp weight each of the three points (lowest, most likely, highest) produces on its own is averaged. This is a fixed implementation choice made by DecisionMind; other fuzzy CRITIC forms also exist in the literature (for instance, forms that compute spread and correlation directly on the triangles using triangular arithmetic), and no single canonical form is claimed here.
How to Read the Output
As with base CRITIC, the weight measures the share of distinctive information a criterion adds to the table; it is read the same way (see the CRITIC card).
The difference is this. The weight is now the average of three separate crisp calculations. If the triangle's lowest and most likely components carry the same pattern, for instance if they are shifted by a constant amount in every cell, the two corners' weights come out identical, and only the highest corner produces a different weight; the final weight is then driven mainly by the triangle's upper end. The report should show clearly how close the three corners' weights are to one another, that is, whether the fuzzy range changes the result.
Thus instead of writing:
"Fuzzy CRITIC analysis showed that C1 was the most important criterion"
the report should read:
"C1 received weights of 0.461, 0.461 and 0.430 respectively in the crisp CRITIC calculations run separately on the three corners (lowest, most likely, highest); its average is 0.451, and the three corners are consistent apart from a small dip at the upper end, so the weight rests on a shared tendency across all three corners rather than on the triangle's width"
When to Prefer This over the Base Method
This extension is suitable when the criterion list is long and contains repetitive indicators, the weights are wanted to derive objectively from the data, and the criterion values themselves come from a judgement or estimate, that is, are verbal or approximate rather than measured. If CRITIC's objectivity is wanted alongside fuzzy input, this extension is preferred.
If the criterion values are measured, fuzzification adds nothing to CRITIC; base CRITIC is sufficient. Base CRITIC's exit conditions apply unchanged: if the number of alternatives is small (fewer than five), correlation becomes unreliable, and this unreliability is repeated separately in each of the three corners; if criteria were chosen to be independent beforehand, the second measure (correlation) adds nothing at any corner.
Mistakes Specific to This Extension
Using a uniform, proportional fuzzification without noticing it. If the same constant width has been added to every cell (for example, a non-proportional shift such as +1 or +2 to every value), the normalised tables for the lowest and most likely corners can come out identical after min–max scaling, and these two corners then produce the same weight; this is not an error, but if unnoticed it leads to the false impression that "all three corners were computed differently". The report should state this overlap explicitly.
Claiming there is a single "canonical" fuzzy CRITIC. The form DecisionMind applies here (running the three corners independently and averaging) is one of several possible formulations; another implementation might carry triangular arithmetic directly into the spread and correlation calculation and produce a different weight. Which form was used must be stated in the report.
Expanding a measured criterion into a fuzzy CRITIC input without justification. A measured value should remain a triangle with all three components equal; an unjustified width should not be added.
Direction error. If a "lower is better" criterion is marked "higher is better", the sign of the correlations reverses in each of the three corners, and the repetition penalty is applied consistently to the wrong criterion, three times over.
The governing principle is this:
Fuzzy CRITIC repeats crisp CRITIC independently across the triangle's three corners and averages the result; any application that fails to show which corner is driving the final weight, or that claims a single canonical form, conceals the method's real behaviour.
Cases
These examples are not a literature case; they are the validation constant of the source code (the analyse_asisance repository, mcdm_engine.py) that implements this weighting profile in DecisionMind, and are flagged at evidence level C. They are not an example from a published, page-citable article. The first case is this validation constant; the second case is an illustrative construction.
1. Illustrative example: Four alternatives, three criteria (DecisionMind validation constant)
Four alternatives are assessed with triangular fuzzy numbers on three criteria; the first and third criteria are marked higher is better, the second lower is better (a cost type).
| Alternative | C1 | C2 (cost) | C3 |
|---|---|---|---|
| A1 | (1; 2; 3) | (4; 5; 6) | (7; 8; 9) |
| A2 | (2; 3; 5) | (7; 8; 10) | (3; 4; 6) |
| A3 | (5; 6; 7) | (2; 3; 4) | (8; 9; 10) |
| A4 | (4; 5; 6) | (6; 7; 8) | (1; 2; 3) |
| Direction | higher is better | lower is better | higher is better |
The method takes each corner (lowest, most likely, highest) as a separate crisp table and runs crisp CRITIC's five steps (scale equalisation, spread, correlation, information content, weight) independently on each.
| Criterion | Lowest-corner weight | Most-likely-corner weight | Highest-corner weight | Average weight |
|---|---|---|---|---|
| C1 | 0.461 | 0.461 | 0.430 | 0.451 |
| C2 | 0.201 | 0.201 | 0.237 | 0.213 |
| C3 | 0.338 | 0.338 | 0.333 | 0.336 |
The result can be read as follows. The lowest and most likely corners' weights are identical (0.461/0.201/0.338), because in this table the most likely value was constructed by adding a constant unit to the lowest value in every cell, and this constant shift changes nothing after min–max scaling. Because the highest corner carries a different pattern (the shift is not constant), it slightly lowers C1's weight (0.430) and slightly raises C2's (0.237); the final average reflects this small difference.
The panel has a hesitation. Had CRITIC been run treating only the most likely corner, the triangle's modal value, as a crisp table, C1's weight would have come out at 0.461; this differs from the final fuzzy average (0.451) by only 0.010. The gap is small in this example, but it comes entirely from the highest corner's different correlation pattern and could be much larger in a table with a different width. The report should show whether the weight rests on a shared tendency across the three corners or on a single corner alone.
In the report: "The weights are the average of the CRITIC calculations run independently on the triangle's three corners (C1=0.451; C2=0.213; C3=0.336); because the lowest and most likely corners give identical results, the small differences in the weight come entirely from the upper-end values."
Source: Validation constant of DecisionMind's Fuzzy CRITIC engine (the analyse_asisance repository, mcdm_engine.py, _weights_fuzzy_critic); it is not an example from a published article, its evidence level is C, and the card states this as it is.
2. Sport: A football club's scouting team weighting player-evaluation indicators
A football club's scouting team must decide how much weight to give each of the eight indicators (ball-involvement count, pass-completion percentage, expected-goal contribution, sprint speed, tackle count, aerial-duel win percentage, foul count and injury-history score) it uses to compare prospective players. Because most of the indicators rest on scouts' match-by-match verbal notes such as "good / average / poor", they have been recorded as triangular fuzzy numbers; the team wants the weights to derive from the data rather than from its own priorities, because it suspects that expected-goal contribution and ball-involvement count measure the same thing.
The method runs the three corners of the eight indicators separately and computes the spreads and correlations. Suppose expected-goal contribution and ball-involvement count come out highly correlated at all three corners and both receive a low weight; injury-history score, moving independently of the other indicators, receives a high weight.
The scouting team has a hesitation. Expected-goal contribution receiving a low weight does not mean this indicator is unimportant; it has shared its informational contribution because it carries the same information as ball-involvement count. The team should also check how close the three corners' weights are to one another; if only the highest corner brings out an indicator, this means the indicator is sensitive to the scouts' most optimistic notes and should also be confirmed against the most likely-value notes.
In the report: "The eight indicators' weights have been derived from the average of the CRITIC calculations run independently on the three corners; expected-goal contribution shared its informational contribution owing to its high correlation with ball-involvement count, while injury-history score received the highest weight because it carries independent information."
3. What Not to Do
The first error is reporting only the most likely corner's (the modal value's) weight (C1=0.461) as the final weight in the illustrative example. This means ignoring the contribution of the lowest and highest corners; the gap is small in this example but could be large in another table, and the report should show that this was checked.
The second error is marking C2 (cost) as "higher is better". This reverses the sign of the correlations at each of the three corners, and the repetition penalty is then wrongly applied to C2 rather than C1.
The third error is assuming that "fuzzy CRITIC" refers to a single canonical calculation and declaring a different piece of software's differing result "wrong". More than one native fuzzy CRITIC form exists in the literature.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/fuzzy-critic
Diakoulaki, D., Mavrotas, G., & Papayannakis, L. (1995). Determining objective weights in multiple criteria problems: The CRITIC method. Computers & Operations Research, 22(7), 763–770. DOI: 10.1016/0305-0548(94)00059-H
Zadeh, L. A. (1965). Fuzzy sets. Information and Control, 8(3), 338–353. DOI: 10.1016/S0019-9958(65)90241-X
Zavadskas, E. K., & Podvezko, V. (2016). Integrated determination of objective criteria weights in MCDM. International Journal of Information Technology & Decision Making, 15(2), 267–283. DOI: 10.1142/S0219622016500036
Žižović, M., Miljković, B., & Marinković, D. (2020). Objective methods for determining criteria weight coefficients: A modification of the CRITIC method. Decision Making: Applications in Management and Engineering, 3(2), 149–161. DOI: 10.31181/dmame2003149z