← Back to the principles list

False Consensus Effect in ecommerce

Next principle →

Owners who assume shoppers think like them often build stores for themselves.

A founder who skips product details may leave them off the page, sure that nobody reads them. Meanwhile a shopper about to spend $1,500 may want exactly those details before buying.

False consensus effect
Made-up example: one plain spec line changes the choice once the founder stops assuming shoppers are like them.

The false consensus effect leads people to overestimate how many others share their own opinions, tastes and habits.

Most of us do this without noticing, and a store owner is only one shopper. So check your guesses against what customers really say and do. A short chat with a few recent buyers can show what you have been leaving out.

False consensus effect example: “Nobody reads specs” on a $1,500 espresso machine

Imagine a made-up store selling two espresso machines: the Classic at $900 and the Pro at $1,500. Each has a product video, a name and a price. The founder says, “I never read specs. Nobody does,” so the page has no written details. With nothing to explain the $600 gap, most shoppers pick the Classic, and the typical sale is $900. The store then adds one line under each name: Aluminum boiler for the Classic and Steel boiler for the Pro. The videos stay. Now the Pro outsells the Classic, and the typical sale is $1,500. Your habits are only one person's habits, so ask shoppers what they need.

How the false consensus effect works with other principles: 4 store examples

False consensus has several lookalikes, and each one needs a different fix. Three of these pairs tell them apart and the last shows how it can team up with overconfidence. Every store below is made up to show the idea.

False consensus effect vs curse of knowledge

Often confused with: The false consensus effect assumes others share your tastes and habits, while the curse of knowledge assumes they share what you know.

Illustrative store example: A kitchen knife store owner loves black-and-gold pages and assumes every shopper does too, and that part is false consensus. Writing “VG-10 core, 60 HRC” and assuming shoppers can read it is the curse of knowledge, so ask about the look and explain the terms.

Curse of knowledge: why expert words can lose new shoppers →

False consensus effect vs spotlight effect

Often confused with: The false consensus effect overrates how similar others are to you, while the spotlight effect overrates how much they notice you.

Illustrative store example: A wedding-invitation store owner always phones before buying anything, assumes every couple does too and leaves out an online way to order samples, which is false consensus. Losing a week over a logo that sits slightly off, when few shoppers would ever spot it, is the spotlight effect.

Spotlight effect: why owners think everyone notices small flaws →

False consensus effect vs bandwagon effect

Often confused with: The false consensus effect assumes others already do what you do, while the bandwagon effect is doing something because others seem to be doing it.

Illustrative store example: A sunglasses store owner wears only round frames and assumes most shoppers want them too, which is false consensus. A shopper who buys round frames because everyone seems to wear them is on the bandwagon, so check your own orders before buying more stock.

Bandwagon effect: why shoppers follow what others are buying →

False consensus effect and the Dunning-Kruger effect

Works with: An owner new to design can overrate their eye, which fits the Dunning-Kruger effect, and then assume shoppers share their taste, which is false consensus.

Illustrative store example: A new T-shirt store owner picks a thin script font for every product name, sure it looks great and sure shoppers will agree. Ask five customers to read a product page on their phones, and change the font if they struggle.

Dunning-Kruger effect: why beginners can overrate their own skill →

Put it into practice

How do I find out what my shoppers actually want?

Talk to five people who bought in the last month and ask what they checked before buying. Listen for words and worries that surprise you. Read your support messages and the search terms people type into your store. Then list every page decision you made from personal taste, such as no written details or tiny type, and check each one against what you heard.

Should I stop trusting my own taste?

No. A strong point of view is often why a store is worth visiting, and copying everyone else has its own risks. The line sits between style and information. Keep your taste in the look and the voice. For practical matters, such as sizes, materials, delivery and how the page works on a phone, check with shoppers first. You can't please everyone, so listen most closely to the people you want to serve.

How does false consensus show up in the way I look at my own store?

You assume shoppers see what you see. You probably review it on a big screen with fast internet, knowing where everything is. Your shoppers may be on an older phone with a weak signal, seeing the page for the first time. Try your store that way once a month: use your phone, turn off Wi-Fi and try to buy something. Ask a friend who has never seen it to do the same while you watch quietly.

How is the false consensus effect different from social proof?

They run in opposite directions. Social proof is looking at what other people do and following it, and it rests on something you can see, such as reviews. False consensus runs from you to others: you start with your own habit and assume it is common. A useful check is to ask what the belief is based on. If the answer is “I would do this,” treat it as a guess.

How do I test an assumption I'm sure about?

Write it down as a plain guess, such as “Nobody reads specs.” Then look for evidence against it. Check how many shoppers open the details section, and show live shoppers a page with details or a page without, picked at random. Compare orders and the questions sent to support. Ask someone on your team who disagrees with you to help read the results.