Illusion of Transparency: Why Your Design Rationale Isn’t as Obvious as You Think
Det gick inte att lägga till artiklar
Titeln kunde inte läggas till i kundvagnen.
Titeln kunde inte läggas till i Önskelistan.
„Ta bort från Önskelista“ misslyckades.
„Följ podcast“ misslyckades
„Sluta följa podcast“ misslyckades
-
Berättare:
-
Av:
If your disagreement feels obvious to you, why does everyone keep walking out of the meeting thinking you’re on board?
A Stanford researcher once had people tap out familiar songs on a desk and predict how often listeners would name the tune. Tappers guessed about half the time. Listeners got three out of 120. That gap has a name: the illusion of transparency. It’s our tendency to overestimate how much other people can see what’s going on inside us, like our nerves, our disagreement, our intentions, and our tone.
Thomas Gilovich, Kenneth Savitsky, and Victoria Husted Medvec put this bias on the map in 1998, building on earlier work by Dale Miller and Cathy McFarland. Across lying, hiding disgust, and reacting to someone breaking the rules, the result was the same. People believed their insides were showing, and they mostly weren’t. We confuse how strongly we feel something with how clearly we’re showing it.
On product teams, this one hides well because it feels like everyone else’s fault. I share a roadmap review where I was sure my crossed arms and pointed questions made my concerns obvious, and my PM walked away thinking I was totally fine with it.
This week, we look at how the same bias shows up in Slack tone, design critiques, performance feedback, stakeholder negotiations, and async work, and why the fix is almost insultingly simple: say the quiet part out loud. So if you’ve ever been blindsided by “but you didn’t say anything,” give this one a listen.
Topics:
• 00:00 - Tap out Happy Birthday on your desk
• 01:00 - What is the illusion of transparency?
• 03:00 - The roadmap review where nobody knew I disagreed
• 04:25 - Why we think our feelings are visible
• 04:55 - The research behind the bias
• 05:55 - Egocentric anchoring: why this happens
• 06:30 - The spotlight effect and the curse of knowledge
• 07:00 - Can knowing about the bias fix it?
• 07:45 - Why your Slack tone gets misread
• 08:10 - The thumbs up emoji problem
• 08:55 - Design critiques and "obvious" rationale
• 09:15 - Why your feedback isn't landing
• 9:40 - Stakeholder negotiations
• 10:00 - Remote and async work turns it up to 11
• 10:45 - The insultingly simple fix
• 11:05 - Assume you're harder to read than you feel
• 11:45 - Say the obvious thing out loud
• 12:15 - Make feedback impossible to misread
• 12:50 - Read their words, not their face
• 13:20 - Build check-backs into async work
—
Thanks for listening!
We hope you dug today’s episode. If you liked what you heard, be sure to like and subscribe wherever you listen to podcasts! And if you really enjoyed today’s episode, why don’t you leave a five-star review? Or tell some friends! It will help us out a ton.
If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.
• Get a FREE audiobook AND support the show
• Support the show on Patreon
• Check out show transcripts
• Check out our website
• Subscribe on Apple Podcasts
• Subscribe on Spotify
• Subscribe on YouTube
• Subscribe on Stitcher