What is the halo effect in product design?
The halo effect is the bias where one strong impression shapes how people judge everything else about the same thing. In product design, it means the first moments of an app or website can colour how usable, credible and valuable people believe the rest of it to be, before they have tested any of it.
Where the term comes from
Psychologist Edward Thorndike named it in his 1920 paper, "A Constant Error in Psychological Ratings". He found that when people rated soldiers on separate qualities, the ratings ran together instead of being judged independently. A strong view on one quality spilled over into the others.
What the research says about software
- First judgments are very fast. Lindgaard and colleagues found that people can assess a homepage's visual appeal after seeing it for just 50 milliseconds, and that those ratings correlated strongly with ratings given at 500 milliseconds (2006, Behaviour & Information Technology). This was lab research on visual appeal, so it does not prove that every visitor decides in 50 milliseconds.
- Attractive interfaces can seem easier to use. Kurosu and Kashimura studied 26 cash machine layouts and found that apparent usability was more strongly affected by aesthetics than by inherent usability (CHI 1995).
- Speed is part of the impression, and it can change results. A study commissioned by Google and run by 55 and Deloitte covered 37 brand websites and more than 30 million sessions. It found that a 0.1 second improvement in four speed metrics could improve progression through the purchase funnel, and web.dev reports an 8.4% conversion increase for retail sites (web.dev). Google sells web tools and ads, so read that as a useful signal rather than a guarantee.
Where it applies in a product
| First moment | What people infer | What to get right |
|---|---|---|
| Homepage, first view | Is this company credible? | A clear statement of what you do and for whom, fast loading, one obvious next step |
| App store listing | Is this worth installing? | Screens that show the main task, not decoration |
| First session in an app | Will this be hard? | Reach the first useful result quickly and ask only for what that step needs |
| Dashboard, first load | Can I trust these numbers? | Correct data, a visible update time and one primary metric per view |
| Contact form | Will anyone answer? | Few fields, a stated reply time and a confirmation that the message arrived |
Where the halo stops helping
A halo buys patience, not forgiveness. If a beautiful product loses data or misses its promise, the impression will not survive real use. The effect also causes a practical research problem: people may rate a polished prototype as easy to use because it looks good. Test whether they can complete the task as well as asking what they think of it.
How to audit your own first impression
- Show your first screen to someone new for five seconds, then ask what you do and who it is for.
- Measure load speed on a mid-range phone on a mobile connection, not on your office laptop.
- Watch one new user try the main task without help, and note where they first hesitate.
- Check that the design makes only promises the product keeps.
- Fix the first point of doubt, then repeat.
This is the idea behind our name. HALO Studio designs that first moment and engineers the product behind it to live up to it. Our case studies show the screens from real working apps.