I once bet my PM a bottle of decent scotch that our users would revolt if we removed the command-line export feature. I argued that “everyone” uses the CLI for batch processing. It was obvious. It was intuitive. It was the only way I used the product.
We removed it. Support received exactly zero tickets. I bought the scotch.
This wasn’t a technical failure; it was a failure of imagination. I had projected my own workflow onto ten thousand strangers and assumed it was universal law.
If you lead a team, build a product, or write code, your intuition is likely lying to you about what is “normal.” This is a dissection of the False Consensus Effect, the psychological glitch that convinces us that our weird habits are the industry standard, and how it’s silently killing your product-market fit.
The Mirror House
The False Consensus Effect is the tendency to overestimate how much other people agree with our beliefs, behaviors, and preferences. We assume our internal narrative is the default setting for humanity.
It’s easy to spot in others. You see the junior dev who assumes everyone knows the obscure shortcuts in Vim. You see the CEO who thinks everyone is willing to work on Saturday because “we’re changing the world.”
It is terrifyingly hard to spot in yourself.
In 1977, Stanford psychologists asked students if they’d walk around campus wearing a sign that said “Eat at Joe’s.” The results were binary. Those who agreed to wear the sign estimated that 62% of their peers would also agree. Those who refused estimated that 67% of their peers would also refuse.
Both groups thought they were the majority. Both groups were statistically impossible to reconcile.
We anchor the world to our own position. If you think $100 is expensive for SaaS, you assume your customers do too. If you think privacy is dead, you assume your users don’t care about data tracking. You are looking in a mirror and calling it a window.
The Availability Trap
Why does a smart brain do this dumb thing? It comes down to the Availability Heuristic.
Your brain is a lazy pattern-matching machine. When asked to estimate what “most people” think, it doesn’t run a SQL query on the global population. It queries the cache.
And what’s in your cache?
- Your own thoughts (highest availability).
- Your friends and colleagues (high availability).
- That one article you read yesterday (medium availability).
In tech, this is exacerbated by our tendency to cluster. We build monocultures. We hire for “culture fit.” We live in San Francisco or hang out in the same subreddits. When everyone you know hates Facebook, you assume “Facebook is dying.” meanwhile, they add another hundred million users in markets you’ve never visited.
This creates a feedback loop. You validate your opinions with people who share your opinions, which solidifies the belief that your opinions are facts.
The Ego Component
There is a darker, more fragile element here: Self-Esteem Maintenance.
Acknowledging that our worldview is niche makes us feel isolated. If I believe that clean code is more important than shipping speed, and the rest of the world disagrees, I have to confront the possibility that I might be wrong. Or, at the very least, that I am weird.
To protect our ego, we project our values onto the masses. We convince ourselves that the “silent majority” agrees with us, and the dissenters are just a loud, irrational minority.
I’ve seen this destroy marketing campaigns. A founder writes copy that appeals to themselves. It’s witty, cynical, and full of jargon. They love it. Their team loves it. The market stares at it blankly because the market doesn’t have the founder’s context.
When the campaign fails, the founder rarely blames the copy. They blame the algorithm. They blame the timing. They blame the “stupidity” of the customer.
The “One Right Way” Fallacy
In engineering, false consensus manifests as dogmatism.
I watched a team rewrite a perfectly functional REST API into GraphQL because “everyone is moving to GraphQL.” They weren’t solving a performance problem; they were solving a social anxiety problem. They assumed that because their Twitter feed was talking about graph edges, the entire industry had shifted overnight.
The reality was that 99% of the industry was still running on boring, profitable REST endpoints.
When we assume consensus, we stop looking for alternatives. We stop A/B testing because we “know” the winner. We skip the user research because “I am the user.”
You are not the user. You are a power user with equity, insider knowledge, and a specific bias toward the solution you built. You are the least representative person in the room.
Breaking the Hallucination
You cannot cure yourself of this bias. It’s hardwired. But you can build systems to bypass it.
1. The Pre-Mortem Before launching a feature or a policy, ask the room: “Let’s assume this fails spectacularly. Why did the users hate it?” This forces the team to step outside their own optimism. It compels you to simulate a user who doesn’t think like you.
2. Seek Disconfirming Evidence The natural instinct is to look for data that supports your view. Invert it. If you believe your pricing is fair, explicitly hunt for data that suggests it’s too high. If you think the UI is intuitive, put it in front of a drunk person or a relative over 60. Watch them struggle. That struggle is reality; your Figma file is theory.
3. Diversify the Input Stream If all your news comes from Hacker News and all your friends are developers, your sample size is effectively 1. Read things written by people who hate your industry. Talk to customers who churned. The goal isn’t to agree with them, but to realize that they exist in large numbers.
4. The “100 People” Heuristic Whenever you make a generalization (“Nobody uses email anymore”), visualize a stadium of 100 randomly selected humans. Not 100 tech workers. 100 humans. How many of them use email? Suddenly, your “nobody” looks a lot like “everybody except my three friends on Discord.”
The Ambiguity of Leadership
There is a nuance here. Leadership requires vision, and vision often requires ignoring the consensus.
If Steve Jobs had listened to the consensus, he wouldn’t have removed the floppy drive. If Henry Ford asked people what they wanted, they would have said faster horses.
But there is a difference between betting against the consensus and falsely assuming the consensus is on your side.
The former is a calculated risk. The latter is a delusion.
Great leaders know they are outliers. They know their vision is weird. They know the market doesn’t “get it” yet. They accept the friction. They don’t pretend that the friction doesn’t exist.
Don’t confuse conviction with consensus. You can be right when everyone else is wrong, but you better be sure you aren’t just projecting your own shadow on the wall and calling it a crowd.
Final Thought
The next time you find yourself saying “It’s obvious that…” or “Surely everyone knows…”, stop.
That is the sound of your brain trying to save energy. It’s the sound of the False Consensus Effect taking the wheel.
Pause. Check the data. Ask someone who disagrees with you.
You might still be right. But at least you won’t be betting the company on a reflection in the mirror.