Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How the Curse of Knowledge Sabotages Your Emails
Transcript
- Lucas: So I was reading through a post-mortem from a product team last week, and it hit me that we've never actually talked about one of the sneakiest biases in the office. It's called the curse of knowledge. Luna: The curse of knowledge. That's the one where once you know something, you can't imagine not knowing it, right? Lucas: Exactly. And it's not just a party trick from a psychology textbook. It's the reason your carefully worded email gets misunderstood, why that training session falls flat, and why the senior engineer's 'quick fix' turns into a two-week disaster. Luna: I feel like I've been on both sides of that. I remember once I was explaining our onboarding process to a new hire, and I thought I was being crystal clear. Then they asked a question that showed they had no idea what I was talking about. Lucas: That's the classic moment. The research comes from a 1990 study by Colin Camerer and two colleagues. They had participants tap out famous melodies on a table. The tappers expected listeners to guess the tune about fifty percent of the time. In reality, listeners got it only two and a half percent of the time. Luna: Two and a half percent. That's brutal. The tappers were hearing the tune in their own heads, so they thought it was obvious. Lucas: Right. And that gap — between what you know and what you can imagine others not knowing — is the curse. In the office, it shows up everywhere, but I think the most damaging place is in written communication, because there's no immediate feedback. You fire off an email assuming your reader shares your context, and they don't. Luna: Do you have a concrete example? Because I feel like we need one that isn't just 'the engineer was confusing.' Lucas: So there was this incident I read about from a fintech company. A senior backend engineer needed to explain to a junior developer how to handle a database migration. In his head, it was a simple two-step process: 'just run the script and then verify the checksum.' But he didn't mention that the script had to run in a specific order, or that the checksum verification required a specific tool that wasn't in the standard setup. Luna: And the junior developer, who's fresh out of bootcamp, has no idea what a checksum even is, let alone how to verify it. So they run the script, skip the verification, and the whole thing goes sideways. Lucas: Exactly. The senior engineer wasn't being malicious. He just couldn't step back into the shoes of someone who doesn't have ten years of context. The fix ended up costing the team three days of rework and a delayed launch. Luna: And the worst part is, the junior developer is probably too afraid to ask questions because they don't want to look stupid. Lucas: That's the other half of it. The curse of knowledge isn't just about the person explaining. It's also about the power dynamic in the room. When you're the new person or the less experienced one, admitting you don't understand something feels risky. Luna: So what's the fix? I mean, we can't just say 'explain it like I'm five' every time, because that gets old fast. Lucas: There's a technique I picked up in my consulting days. When I had to present complex findings to a client, I would force myself to explain the whole thing to a friend who knew nothing about the industry. If my friend couldn't follow the logic, I knew I wasn't ready to present. It's brutal, but it works. Luna: That's like a dress rehearsal for clarity. I bet it also helps you identify which parts of your explanation are actually load-bearing and which are just jargon you're hiding behind. Lucas: Exactly. And there's a simpler version you can do in the moment. Before you hit send on that email, ask yourself: 'If the reader has never seen this project, will they know what I'm asking them to do?' If the answer is no, go back and add context. Luna: But even that's hard because you're so immersed in your own head. That's why I think it helps to have a designated 'dumb question' person on your team. Someone who's willing to ask the obvious questions that everyone else is too embarrassed to ask. Lucas: That's a great point. And it ties into something else: managers can actually create an environment where it's safe to say 'I don't get it.' If a leader admits when they're confused, it gives everyone else permission to do the same. Luna: I've seen that work. My old boss used to say 'I'm sure this makes sense to you, but I'm lost. Can we back up?' And every time, it was like a collective sigh of relief. Lucas: And that's not just about morale. That's about catching costly misunderstandings before they happen. The curse of knowledge is expensive. Luna: Speaking of expensive, I know this is a totally random pivot, but we've been talking about how hard it is to communicate clearly, and I just want to say — a few of you out there have been making sure we can keep doing this show ad-free, and that genuinely matters. If you've ever gotten something out of these episodes, buying us a coffee at buy me a coffee dot com slash fexingo is what keeps the lights on. No pressure, just an honest thing. Lucas: Yeah, it really does go straight into production time. And it's not about perks or rewards — it's just that a small group of listeners already chip in, and that's literally what funds us making this many episodes. Okay, back to the curse. Luna: Right. So we've talked about emails and training. Where else does this bias bite? Lucas: The big one is in cross-functional meetings. When you have marketing, engineering, and sales in the same room, each group has its own jargon. The marketer says 'we need to increase our CAC efficiency,' and the engineer hears 'they want us to build a new dashboard,' which is not at all what the marketer meant. Luna: So the curse of knowledge isn't just about expertise level. It's also about different domains of expertise. Lucas: Exactly. Everyone is an expert in their own silo, and we all assume that the other person's jargon means the same thing to them. It's a recipe for misalignment. Luna: What about the reverse? When you're the one who doesn't know something, how do you protect yourself from the curse? Lucas: That's a good question. The first step is to realize that if you're confused, it's probably not because you're stupid. It's because the other person is failing to bridge the gap. So you have to proactively ask for clarification, even if it feels awkward. Luna: And you can frame it as a you problem, like 'I'm a little slow on this, can you walk me through it again?' That way you're not challenging their expertise. Lucas: Right. And there's a specific technique I love called 'teaching back.' After someone explains something, you say 'so what I heard is...' and you repeat it back in your own words. That forces the other person to hear where you're at, and it often reveals exactly where the gap is. Luna: That's like a mini mirror for understanding. I've used that in code reviews — I'll ask a junior dev to walk me through their approach, and if they can't, it tells me they're copying and pasting without understanding. Lucas: And that's the thing — the curse of knowledge isn't just about words. It's about hiding the underlying logic. When you teach back, you're forcing the logic to the surface. Luna: So where does this leave us? Are we doomed to be misunderstood at work forever? Lucas: Not doomed, but we have to be deliberate. The bias is automatic, so the fix has to be intentional. That means slowing down, checking for understanding, and creating a culture where not knowing is okay. Luna: And maybe we should all channel our inner five-year-old and ask 'why' a little more often. Lucas: That's actually a great takeaway. The next time you're explaining something and you get that glazed-over look, stop and ask 'what part of that didn't make sense?' You might be surprised how often the answer is 'all of it.' Luna: And on that note, I think we've given everyone plenty to chew on. Thanks for hanging out with us.