What it is
The halo effect causes a single salient positive attribute - an impressive track record, a well-known brand, a confident presentation - to raise the perceived quality of all other attributes, even those that have not been evaluated independently. It operates automatically and is especially strong under time pressure. Once a favourable overall impression forms, contradictory evidence is harder to register.
Where it shows up
In vendor selection for build-vs-buy decisions, the halo effect means a vendor with a prestigious client list receives the benefit of the doubt on integration complexity, pricing transparency, and support quality - areas that warrant independent scrutiny. The team evaluates the brand rather than the product. A less well-known vendor offering a better technical fit may be eliminated early because it lacks the reputational halo.
What Rubicon Probity does
When Rubicon Probity detects a decision record at the Decide stage where vendor or candidate evaluation criteria are not scored independently before an overall impression is formed, it flags the record with a CAUTION and recommends a structured attribute-by-attribute scoring pass. Scoring each dimension blind to overall ranking is suggested before the final comparison is assembled.
Detection questions
- Have you scored each evaluation criterion independently, before comparing options overall?
- Which attributes of this vendor or candidate have you actually verified, versus inferred from their reputation?
- If this option had no brand recognition, would the documented evidence still support the same ranking?