The name was coined in 1987 by Dale Miller and Cathy McFarland, who were studying a different puzzle: why everyone in a room can privately feel confused while assuming they’re the only one. Part of the answer was that people believe their own confusion is showing when it isn’t.
But the research that put the bias on the map came in 1998, from Thomas Gilovich, Kenneth Savitsky, and Victoria Husted Medvec at Cornell. They ran three experiments that all pointed the same direction.
In one, participants told lies to a group and then guessed how many people caught them. Liars consistently believed they’d been spotted far more often than they had. In another, people sipped drinks on camera, some of them foul, and tried to hide their disgust. They assumed observers could tell which drinks were nasty way more often than observers actually could. In a third, a planted actor started breaking the rules during a task, and participants were convinced their alarm was written all over their faces. It wasn’t.
Three totally different situations. Same result. People believe their insides are showing.
So why does this happen?
The explanation Gilovich and his colleagues landed on is something called egocentric anchoring. When you try to figure out what someone else perceives, you don’t start from nothing. You start from your own experience, which is intense and immediate and impossible to ignore. Then you try to adjust away from it. And you never adjust far enough.
Your nervousness feels like a siren. So you assume it looks like one. The vividness of the feeling gets mistaken for the visibility of the feeling.
That’s the whole bias in one sentence: we confuse how strongly we feel something with how clearly we’re showing it.
This puts the Illusion of Transparency in a family of related biases. The spotlight effect is its sibling: we think people notice our appearance and behavior more than they do. The curse of knowledge is a cousin: once we know something, we can’t imagine what it’s like not to know it. That’s the tapping study. Tappers couldn’t un-hear the song, so they couldn’t picture the listener’s experience. All three come from the same root. We’re trapped inside our own head, and we keep forgetting that nobody else is in there with us.
In 2003, Savitsky and Gilovich tested whether you could break the spell. They had people give impromptu speeches, and as expected, speakers thought they looked far more nervous than the audience saw. Then they ran it again, and this time they told some speakers about the Illusion of Transparency beforehand. Just explained it. “Your nerves probably aren’t as visible as they feel.”
The informed speakers were less anxious. They rated their own speeches higher. And the audience rated them as more composed.
Knowing about the bias was the fix. Which is a pretty good argument for this series.
The Illusion of Transparency sounds like a public-speaking problem. It’s a team problem. It’s running underneath most of the miscommunication on a product team, and it hides well because it feels like other people’s fault.
Start with Slack. In 2005, Justin Kruger and Nicholas Epley ran a series of studies on how well people communicate tone over email. Senders predicted that readers would correctly pick up their tone, sarcastic or sincere, about 78 percent of the time. Actual accuracy was close to a coin flip. The reason is the same egocentric anchor. When you type a message, you hear it in your head in exactly the voice you intend. The reader gets text. Your dry joke lands as a jab. Your quick “sure” reads as cold. And you walk away certain you were clear, because to you, you were.
This gets sharper across generations, and the thumbs-up emoji is the example everyone’s heard about. A millennial fires off a 👍 meaning “got it, all good,” and is completely confident that reads as warm and friendly. To a younger teammate, it can land as cold, clipped, even passive-aggressive. Worth being clear here: the generational stuff is more reported trend than settled science, so hold it loosely. But notice the actual bias underneath it. The sender isn’t wrong about what the thumbs-up means to them. They’re wrong about how certain they are that it transported. They never find out it landed wrong, because from inside their head it was obviously friendly. That’s the illusion. Your confidence in the signal doesn’t care whether the other person shares your dictionary.
Now take design critique. A designer presents a direction and skips most of the rationale, because the reasoning feels obvious. It’s been living in their head for two weeks. The room, which has been living in that head for zero weeks, fills the gap with its own assumptions. “Did they consider the mobile case?” “Is this just a preference?” The designer leaves thinking the work spoke for itself. It didn’t. It never does.
Feedback is where this gets expensive. Research on performance appraisals found that managers overestimate how clearly they deliver negative feedback. The manager thinks the concern came through, because they felt it strongly and they alluded to it. The report hears “a few things to tighten up” and walks out believing they’re basically fine. Months later, the manager is frustrated that nothing changed, and the report is blindsided. Nobody lied. The feedback just never fully left the manager’s head.
Stakeholder negotiations have the same shape. Studies of negotiators found that people trying to hide their priorities thought they’d leaked them, and people trying to signal their priorities thought they’d landed. Both groups were wrong in the same direction. So the PM who believes their constraints are “clearly” driving the roadmap, and the designer who believes their pushback was “clearly” registered, are often both talking to people who caught none of it.
Remote and async work turns the volume up on all of this. Every nonverbal cue you’re unconsciously relying on, your face, your pacing, the slight edge in your voice, gets stripped out of a Slack thread or a Loom comment. The signal gets thinner. Your confidence in the signal doesn’t budge.
The pattern across every one of these is the same. Someone feels something clearly, assumes it’s visible, and then gets quietly resentful when the other person doesn’t respond to it. The other person, meanwhile, has no idea there was anything to respond to. That’s how a team ends up with a lot of unspoken frustration and a lot of surprised people.
The fix is almost insultingly simple, and the 2003 study backs it up. Name it. Say the quiet part out loud. Explain the reasoning you think is obvious. Flag the concern you’re sure everyone noticed. Over-communicate the thing that feels redundant. It will feel redundant, because from inside your head, it already got said. From everyone else’s seat, it’s the first they’re hearing of it.
🎯 Here are some key takeaways:
Assume you're harder to read than you feel
The strength of a feeling tells you nothing about how visible it is. Your nerves, your disagreement, your intended tone, all of it feels loud from the inside and arrives as a faint signal on the outside. The default assumption should be that nobody caught it. That sounds pessimistic, but it's accurate, and it changes your behavior in a useful way. Instead of waiting for people to respond to what you're feeling, you say it. And remember the speech study: simply knowing this bias exists made people calmer and more composed. Awareness is doing real work here.
Say the obvious thing out loud
If you think your reasoning is clear from the work, explain it anyway. If you think the room can tell you're not on board, say "I'm not on board, and here's why." If you think your Slack message is obviously a joke, add the signal that makes it obviously a joke. The things that feel redundant to say are usually the things that never got said. The test is simple: could someone who wasn't inside your head for the last two weeks get there from your words alone? If not, you're tapping on a desk.
Make feedback impossible to misread
The performance-appraisal research is a warning for anyone who manages people. Indirect feedback feels delivered to the person giving it and feels fine to the person receiving it. Those are not the same message. When something needs to change, state the gap plainly, say what good looks like, and ask the person to repeat back what they heard. It's awkward for about ten seconds. The alternative is a report who thinks they're doing great until the day they find out they aren't.
Read their words, not their face
The illusion runs both ways. We also overestimate how well we can read everyone else. A quiet teammate reads as fine. A short reply reads as annoyed. A nod reads as agreement. Most of that is you filling in blanks. When you catch yourself concluding what someone thinks from a facial expression or a tone you inferred, treat it as a hypothesis and check it. "I got the sense you had reservations. Did you?" Asking costs almost nothing. Guessing wrong costs a week.
Build check-backs into async work
Written channels strip out the cues you're relying on without telling you. So add a step that replaces them. End decision-heavy messages with "Does that land the way I mean it?" Close reviews with a round of "what did you hear?" rather than "any concerns?" Follow a tense thread with a two-minute call. None of this is about being precious. It's about putting back the feedback loop that a face-to-face conversation gives you for free and a Slack thread quietly deletes.
📚 Keep exploring
To dive deeper into the topic of attentional bias and its implications for decision-making, check out these resources: