Curse of Knowledge Mental Model… | Faster Than Normal
Psychology & Behavior
Curse of Knowledge
Once you know something, you cannot imagine what it is like not to know it — creating systematic blind spots in communication, product design, and leadership.
Model #0132Category: Psychology & BehaviorSource: Colin Camerer / George Loewenstein / Martin WeberDepth to apply:
In 1990, Elizabeth Newton earned her PhD at Stanford with an experiment so simple it almost seems trivial — and so revealing it reshaped how psychologists think about communication. She divided participants into two groups: tappers and listeners. Tappers were asked to tap out the rhythm of a well-known song — "Happy Birthday," "The Star-Spangled Banner," "Mary Had a Little Lamb" — on a table. Listeners had to identify the song from the tapping alone. Before the listeners guessed, Newton asked the tappers to predict how often the listeners would recognise the song. The tappers predicted 50%. The actual success rate was 2.5%. The tappers were wrong by a factor of twenty. And when the listeners failed, the tappers were visibly frustrated — baffled that anyone could miss something so obvious. The tappers could hear the melody in their heads as they tapped. They literally could not imagine what the tapping sounded like without the melody. That gap — between what the knower experiences and what the audience receives — is the Curse of Knowledge.
The Curse of Knowledge is a cognitive bias in which a person who possesses information finds it nearly impossible to reconstruct the mental state of someone who lacks that information. It is not a failure of empathy, effort, or intelligence — it is a structural limitation of human cognition that affects experts more severely than novices precisely because experts have more knowledge to be cursed by. Once you know something, you cannot un-know it. The knowledge rewires how you perceive the problem, the explanation, and the audience — making it systematically difficult to communicate with, teach, design for, or sell to people who do not share your knowledge. The bias was formally named by economists Colin Camerer, George Loewenstein, and Martin Weber in a 1989 paper, though Newton's tapping study became its most famous illustration. The mechanism is not arrogance or laziness. It is a genuine cognitive limitation: the brain uses its current knowledge state as the default lens for interpreting all situations, including situations where the audience operates from a fundamentally different knowledge state. Imagining ignorance from a position of expertise is one of the hardest things a human brain can do.
The consequences of this bias extend far beyond awkward explanations at dinner parties. In product design, the Curse of Knowledge is the reason engineers build interfaces that make perfect sense to engineers and baffle everyone else. The engineer knows where the settings menu is because she built it. She cannot perceive the screen as a first-time user would — cannot see the cognitive load, the ambiguous labels, the missing affordances — because her knowledge of the system's architecture fills in every gap automatically. In medicine, the Curse of Knowledge explains why doctors routinely overestimate patients' understanding of diagnoses and treatment plans. A physician who says "you have a benign neoplasm" is communicating with perfect clinical accuracy and near-zero patient comprehension. The physician hears a reassuring message. The patient hears "neoplasm" and thinks cancer. The same words, decoded through different knowledge states, produce opposite emotional responses.
For founders, the Curse of Knowledge is arguably the most expensive bias in the startup lifecycle. A founder who has spent three years immersed in a problem space cannot remember what it was like not to understand the problem. Their pitch deck assumes knowledge the investor does not have. Their product onboarding assumes familiarity the user does not possess. Their hiring conversations assume context the candidate has never encountered. Every communication failure — the investor who "didn't get it," the user who churned after day one, the new hire who floundered for months — traces back to the same root cause: the founder communicated from their own knowledge state rather than the audience's. The tragedy is that the founder's depth of knowledge, which should be their greatest asset, becomes the very thing that prevents them from transferring that knowledge to the people who need it most.
What makes the Curse of Knowledge particularly insidious is that it is invisible to the person suffering from it. The tapper does not feel like she is communicating poorly — she feels like the listener is failing to hear something obvious. The expert does not feel like his explanation is impenetrable — he feels like the audience is being dense. The founder does not feel like the pitch is unclear — she feels like the investor is not paying attention. The bias generates a self-serving explanation for every communication failure: the problem is with the audience, not the message. This attribution error prevents the correction that would fix the problem, because the expert never questions whether their knowledge is the obstacle rather than the solution. The most knowledgeable person in the room is often the worst communicator in the room — not despite their expertise, but because of it.
The bias scales with expertise in a way that makes it progressively more damaging the more successful you become. A first-time founder has a modest Curse of Knowledge — they have been thinking about the problem for months, perhaps a year. A serial founder on their fourth company, with deep domain expertise and pattern recognition accumulated across decades, has a severe Curse of Knowledge — every conversation is filtered through layers of context that no audience shares. The paradox is cruel: the founder best equipped to solve the problem is the founder least equipped to explain why the problem matters, because the depth of their understanding has made the problem's importance invisible — as self-evident to them as the melody is to the tapper.
The economic consequences are staggering, though largely invisible in any single instance. Every failed pitch meeting where the investor "didn't get it" represents not just a lost funding opportunity but months of runway consumed pursuing a communication strategy that was never tested on an unknowing audience. Every product feature that requires a help article represents not just a documentation cost but an adoption barrier that compounds across every new user who encounters it. Every strategic directive that the organisation misinterprets represents not just a lost quarter of execution but a compounding misalignment between what leadership intended and what the organisation built. The Curse of Knowledge is not a dramatic, visible failure. It is a slow, invisible tax on every interaction between the knowledgeable and the unknowing — and in a world where founders must sell to investors, products must sell to users, and leaders must sell strategy to organisations, that tax is levied on every consequential communication a company makes.
Section 2
How to See It
The Curse of Knowledge operates wherever expertise meets an audience that does not share it — which is nearly every consequential communication in business, from pitch meetings to product launches to team onboarding. The bias is hardest to detect in yourself because, by definition, you cannot perceive the gap between what you know and what your audience knows. The most reliable diagnostic is not self-examination but audience response: when intelligent people consistently fail to understand something you consider straightforward, the Curse of Knowledge is almost certainly the cause.
The signals below surface the specific pattern: a knowledgeable communicator producing confusion in an otherwise capable audience, and attributing that confusion to the audience's limitation rather than to their own inability to exit their informed perspective. The Curse of Knowledge is operating not when communication fails once — anyone can have a bad meeting — but when the same communicator produces the same failure pattern across different audiences, different contexts, and different formats.
You're seeing Curse of Knowledge when experts describe their frustration with audiences who "just don't get it" — and that frustration recurs across multiple audiences, suggesting the problem is the communication, not the comprehension.
Product & Design
You're seeing Curse of Knowledge when a product team launches a feature they consider intuitive and watches adoption stall because users cannot figure out how to use it. Slack's early workspace-switching interface made perfect sense to the engineers who designed it — they understood the data model of workspaces, channels, and permissions. New users, who had no mental model for workspace hierarchy, found the interface bewildering. Stewart Butterfield mandated user testing sessions where the team watched real people struggle with flows the designers considered self-evident. The gap between designer intent and user experience was not a design flaw — it was the Curse of Knowledge made visible. Every "intuitive" interface that requires a tutorial is evidence that the designers' knowledge state has contaminated their perception of usability.
Fundraising & Pitching
You're seeing Curse of Knowledge when a founder's pitch produces confusion in the first three minutes because it assumes context the audience lacks. The founder opens with the solution — the technical architecture, the novel algorithm, the product differentiator — before establishing the problem, because the problem is so obvious to the founder that explaining it feels redundant. The investor, who has no context for why this problem matters or who experiences it, cannot process the solution because the mental scaffolding for understanding it has not been built. The most common feedback founders receive after failed pitches — "I didn't really understand what you do" — is almost always a Curse of Knowledge symptom, not an investor intelligence problem.
Leadership & Management
You're seeing Curse of Knowledge when a CEO communicates a strategic shift and is shocked that the organisation does not align behind it. The CEO has spent six months in board discussions, competitive analyses, and customer conversations that led to the decision. She announces the new direction in an all-hands meeting, expecting immediate understanding because the logic feels self-evident to her. The team, which has none of that six-month context, hears a jarring change with no visible rationale. The CEO interprets the team's confusion as resistance. The team interprets the CEO's sparse explanation as arbitrariness. Both are wrong — the gap is not in willingness but in knowledge state. The CEO cannot reconstruct what the decision looks like without the six months of context that made it feel inevitable.
Teaching & Writing
You're seeing Curse of Knowledge when technical documentation is written in language that only someone who already understands the system could parse. API documentation that says "pass the idempotency key in the header to ensure at-most-once delivery semantics" is perfectly clear to the engineer who wrote it and incomprehensible to the developer trying to integrate for the first time. The writer cannot perceive the jargon as jargon — it is simply the precise language for describing the concept. But precision without accessibility is not communication. It is the expert talking to themselves and mistaking it for teaching.
Section 3
How to Use It
Decision filter
"Before communicating anything consequential — a pitch, a product flow, a strategy memo, a job description — ask: what does this look like to someone encountering it for the first time, with none of my context? If I cannot answer that question, I need to test it on someone who fits that description before I ship it."
As a founder
The Curse of Knowledge is the hidden tax on every founder communication. The corrective is systematic: assume your audience knows nothing you have not explicitly told them in the last five minutes, and build every message from that baseline.
In pitch meetings, this means starting with the problem — described in concrete, human terms — before introducing the solution. A founder who opens with "we've built a distributed inference engine that reduces latency by 80% through speculative execution" has lost the room before the second slide. A founder who opens with "every time you ask an AI a question, you wait four seconds for an answer — we've made that wait disappear" has given the investor a mental model they can build on. The information content is identical. The knowledge assumption is opposite.
In product design, the corrective is mandatory user testing with people who have never seen the product. Not colleagues. Not friends who have heard you describe it. Actual strangers who represent your target user, encountering the product for the first time. Watch them without speaking. The moments where they hesitate, squint, or click the wrong button are the Curse of Knowledge made visible — the places where your team's knowledge filled a gap that the user's knowledge could not.
In hiring, the Curse of Knowledge manifests as job descriptions that read like internal documentation — full of acronyms, assumed context, and company-specific terminology that means nothing to the candidate market. A job posting for a "Senior Platform Engineer to own the CQRS pipeline and maintain our event-sourced aggregates" is perfectly clear to the hiring manager and invisible to 90% of the qualified candidates who would excel in the role but do not use that vocabulary. Rewrite every external communication — job postings, product descriptions, investor updates — as if the reader is encountering your company for the first time. Because they are.
As an investor
The Curse of Knowledge creates a systematic blind spot in due diligence: once an investor understands a founder's thesis, they lose the ability to evaluate whether the market will understand it. An investor who has spent three hours in deep-dive sessions with the founder now "gets it" — and unconsciously assumes that customers, partners, and future investors will also "get it" with similar ease. This is the Curse of Knowledge operating on the investor's own comprehension.
The corrective is to add a communication audit to every diligence process. After you understand the business, ask: how long did it take me to understand it? Could the founder explain this in two minutes to someone with no context? Can the product sell itself without a founder-led demo? If the answer to any of these is no, you have identified a distribution risk that is independent of product quality. Many technically superior products fail because the founders cannot escape their own knowledge state long enough to explain the value proposition to people who do not already understand it.
The investor's own susceptibility to the Curse of Knowledge also creates portfolio management risk. After months of working with a portfolio company, the investor understands the business so deeply that they lose the ability to evaluate whether the company's public communications — its website, its sales materials, its recruiting pitch — are actually comprehensible to outsiders. The investor who says "the positioning is fine, I understand it perfectly" is exhibiting the exact bias they should be testing for. The strongest diligence practice is to show the company's landing page or one-pager to someone with no context and measure their comprehension — a ten-minute test that reveals more about distribution risk than ten hours of financial modelling.
As a decision-maker
The Curse of Knowledge is the primary reason organisational communication fails at scale. The executive team, immersed in strategic context, makes decisions that feel obvious and communicates them in shorthand. The rest of the organisation, lacking that context, receives directives that feel arbitrary and unexplained. The resulting misalignment is attributed to "communication problems" or "cultural issues" when the root cause is structural: the people with the most context are the worst equipped to communicate with people who have the least.
The corrective is to mandate context-setting as a non-negotiable component of every strategic communication. Before stating any decision, state the problem it solves, the alternatives that were considered, and the reasoning that led to this choice over those alternatives. This feels redundant to the decision-maker — who has already processed all of this information — but it is essential for the audience, who has not. Jeff Bezos's practice of requiring six-page narrative memos before meetings is partly a Curse of Knowledge countermeasure: the memo format forces the writer to build the argument from first principles rather than from assumed shared context.
A second structural intervention is the "new hire test": before sending any company-wide communication, route it through an employee who joined within the last 30 days. New hires are the organisation's best Curse of Knowledge detectors — they have just enough context to understand the company's language but not enough to fill in the gaps that long-tenured employees fill unconsciously. If the new hire cannot explain back what the communication means and what action it requires, the message has not escaped the leadership team's knowledge state. Revise until the new hire understands it without supplementary explanation.
Common misapplication: Believing that simplifying your language means dumbing down your ideas.
The Curse of Knowledge correction is not about reducing intellectual sophistication — it is about building a bridge between your knowledge state and your audience's. Richard Feynman, arguably the greatest physics communicator of the twentieth century, explained quantum electrodynamics to lay audiences without sacrificing accuracy. He did not simplify the physics. He simplified the entry point — using analogies, concrete examples, and progressive complexity to bring the audience to the insight rather than assuming they could meet him where he already stood. The goal is not to say less. It is to build the scaffolding that allows the audience to understand what you are saying. Founders who resist this correction — insisting that "anyone serious" should understand their pitch as delivered — are choosing their ego over their outcome.
Second misapplication: Assuming the Curse of Knowledge only affects technical communication.
The bias operates on emotional and experiential knowledge with equal force. A founder who has felt the pain of a problem for years cannot imagine that a potential customer might not recognise the problem at all. An executive who has lived through a company crisis cannot understand why new hires do not share the urgency that the crisis created. A designer who has internalised the brand's aesthetic cannot see why a new user finds the interface cold or confusing. In each case, the "knowledge" is not technical information but lived experience — and the inability to reconstruct the pre-experience state produces the same communication failures as technical jargon.
Third misapplication: Using jargon-free language and assuming you have solved the problem.
Removing jargon is necessary but not sufficient. The Curse of Knowledge operates at the level of conceptual structure, not just vocabulary. A founder who replaces "we leverage machine learning to optimise supply chain logistics" with "we use AI to make shipping faster" has simplified the language but may still be skipping essential conceptual steps: who has the shipping problem, why is it slow, what does "faster" mean in concrete terms, and why should the listener care? The Curse of Knowledge is not about words. It is about the assumptions embedded in the argument's structure — the logical steps the expert skips because each step feels self-evident to someone who has already taken it. De-cursing a message requires rebuilding the argument from the audience's starting point, not just translating the expert's argument into simpler words.
Section 4
The Mechanism
Section 5
Founders & Leaders in Action
The founders who overcome the Curse of Knowledge share a common discipline: they systematically distrust their own perception of clarity. They assume that what feels obvious to them is opaque to others, and they build processes — user testing, narrative memos, relentless editing, customer feedback loops — to close the gap between their knowledge state and their audience's. The result is not simpler thinking but clearer communication: products that explain themselves, pitches that land on first hearing, and organisations that align around strategy without requiring every employee to have sat in every meeting.
The opposite pattern is equally visible. Founders who succumb to the Curse of Knowledge build brilliant products that nobody understands, deliver pitches that require a PhD in the problem space, and lead organisations where "communication" is a perennial complaint because every directive assumes context that only the leadership team possesses. The difference between these two outcomes is not intelligence or effort — it is whether the founder treats their own knowledge as a lens that clarifies or a filter that distorts.
The five cases below span product design, organisational communication, strategic pivots, category creation, and growth marketing — demonstrating that the Curse of Knowledge is not confined to pitch meetings but operates across every domain where an expert must make an unknowing audience understand, care about, and act on something the expert considers self-evident.
Jobs understood the Curse of Knowledge as a product design problem, not a communication problem. His central insight was that the people who build technology are constitutionally incapable of perceiving it as a first-time user would — and that this gap is not a minor inconvenience but the primary reason most technology products fail. Apple's design process under Jobs was structured as a systematic Curse of Knowledge countermeasure. Engineers were required to present features not as technical achievements but as user experiences. The question was never "what does this do?" but "what does this feel like to someone who has never seen it before?" When Apple introduced the iPhone in 2007, Jobs did not open with the processor speed, the operating system architecture, or the multi-touch patent portfolio. He opened with a story about how every existing smartphone was terrible to use — anchoring the audience in the user's frustration before introducing the solution. The entire keynote was structured to transfer Jobs's knowledge state to the audience incrementally, building comprehension in the order a newcomer would need it. This was not natural talent. It was the product of weeks of rehearsal specifically designed to strip out every assumption about what the audience already knew.
Bezos institutionalised the Curse of Knowledge corrective through Amazon's six-page memo format. PowerPoint, Bezos argued, lets presenters hide behind bullet points that assume shared context — the audience fills in the gaps with their own interpretations, and everyone leaves the meeting thinking they agreed when they understood different things. The six-page narrative memo forces the writer to build the argument from a cold start, spelling out assumptions, reasoning, and evidence in complete sentences that a reader with no prior context could follow. The format is a structural antidote to the Curse of Knowledge: it forces the knower to reconstruct the unknowing perspective because narrative prose does not permit the cognitive shortcuts that bullet points allow. Bezos extended this principle to Amazon's "working backwards" product development process, which begins with a mock press release written for the end customer — not the engineer. The press release format forces the product team to describe the product in language the customer would use, solving the problem the customer would recognise, before any technical specification is written. The practice systematically prevents the team's growing technical knowledge from contaminating their perception of the customer's experience.
Hastings confronted the Curse of Knowledge directly during Netflix's catastrophic 2011 Qwikster announcement, when he attempted to split Netflix's streaming and DVD businesses into separate brands. The decision made perfect sense from inside Hastings's knowledge state: he had spent months analysing the diverging economics of physical media and streaming, understood that the DVD business was a melting ice cube, and saw the split as a necessary step in Netflix's evolution toward a streaming-only future. He communicated the decision as though the customer shared this context. They did not. Customers experienced the announcement as Netflix making their lives harder — two accounts, two charges, two queues — for no reason they could discern. Hastings later acknowledged that his immersion in the strategic rationale had blinded him to how the change looked from the customer's perspective. The reversal was swift, but the episode became Hastings's most referenced lesson in leadership communication. He restructured Netflix's internal communication practices to require that strategic decisions be explained not from the leadership's reasoning but from the audience's starting point — a direct Curse of Knowledge correction that shaped Netflix's culture memo and its subsequent strategic communications.
Butterfield faced an acute Curse of Knowledge problem: he was trying to sell a product in a category that did not yet exist. When Slack launched in 2013, "enterprise messaging" was not a recognised software category. Butterfield's team understood exactly what Slack was and why it mattered — they had built it as an internal tool for their game studio and experienced its transformation of team communication firsthand. But every potential customer lacked this experiential knowledge. Butterfield's solution was to ban his team from describing Slack in terms of what it was (a messaging platform with channels and integrations) and instead describe it exclusively in terms of what it replaced (the chaos of scattered email threads, lost attachments, and colleagues who never saw critical messages). The positioning was a deliberate Curse of Knowledge inversion: instead of starting from the product and working toward the problem, Butterfield started from the pain the customer already knew and worked toward the product as the relief. His internal memo to the Slack team before launch — titled "We Don't Sell Saddles Here" — is one of the clearest articulations of Curse of Knowledge awareness in startup history, arguing that Slack's job was not to explain its features but to help customers imagine a better version of their working life. The memo's most quoted line — "we are selling a reduction in the amount of information overload" — is Curse of Knowledge inversion in a single sentence: it describes Slack from the customer's pain rather than from the builder's architecture.
Brian CheskyCo-founder & CEO, Airbnb, 2008–present
Chesky discovered the Curse of Knowledge through Airbnb's early growth struggles. The founding team understood viscerally why staying in a stranger's apartment was better than a hotel — they had lived the experience, hosted guests, and seen the human connections that the platform enabled. Early marketing reflected this insider knowledge: it emphasised the platform's mechanics (list your space, book a stay, pay securely) rather than the emotional transformation that distinguished Airbnb from every alternative. Conversion rates were dismal. Chesky realised that potential hosts and guests did not share his experiential knowledge of what an Airbnb stay felt like — and no amount of feature description could bridge that gap. The correction was Airbnb's pivot to storytelling: professional photography that let potential guests see the space as they would experience it, host profiles that humanised the transaction, and a brand narrative centred on "belonging anywhere" rather than "rent a room." Chesky later institutionalised this insight through Airbnb's "11-star experience" framework, which forced product teams to describe features from the guest's emotional journey rather than from the engineering team's implementation perspective — a systematic practice of exiting the builder's knowledge state to inhabit the user's. The framework asked: "what would a five-star experience look like? A six-star? A seven-star?" Each level forced the team to imagine the experience from the guest's perspective at progressively higher fidelity — a structured exercise in overcoming the Curse of Knowledge by making the user's experience, not the builder's intent, the unit of analysis.
The pattern across all five cases is consistent: the founders who overcame the Curse of Knowledge did so not by thinking harder about their audience but by building processes that removed their own knowledge from the evaluation. User testing, narrative memos, customer-language positioning, and fresh-eyes reviews all share a common structure — they replace the expert's simulation of the audience with the audience itself. The expert who tries to imagine what the user experiences will always fail, because the imagination is contaminated by the knowledge it is trying to set aside. The expert who watches the user experience it directly bypasses the contamination entirely.
Section 6
Visual Explanation
Section 7
Connected Models
The Curse of Knowledge does not operate in isolation — it is a gateway bias that activates and amplifies a network of cognitive distortions and communication failures. It interacts with a network of cognitive biases and communication frameworks that together determine whether expertise enhances or impedes understanding. The most consequential communication failures in business — the pitch that misses, the product that confuses, the strategy that fails to align — are rarely caused by the Curse of Knowledge alone. They are caused by the cascading interaction between the Curse of Knowledge and the biases it activates downstream. The expert who cannot see the gap also cannot see the confirmation bias that validates their belief that the gap does not exist. They cannot feel the empathy gap that prevents them from experiencing the audience's confusion. They cannot detect the framing effect that makes their knowledge state feel like the only reasonable lens through which to view the subject. The Curse of Knowledge is the first domino. The connected models below are the chain of dominoes that fall after it.
Understanding these connections transforms the Curse of Knowledge from a single bias to be aware of into a diagnostic framework for identifying why expertise so reliably fails to transfer — and what structural interventions actually work. The six connections below map how the Curse of Knowledge reinforces biases that protect it from correction, creates productive tension with frameworks that force the expert out of their knowledge state, and leads to broader patterns of organisational and market dysfunction that emerge when the bias operates at scale.
Reinforces
Confirmation Bias
The Curse of Knowledge and confirmation bias form a loop that makes communication failures self-sustaining. The expert, cursed by their knowledge, delivers a message that assumes context the audience lacks. The audience's confused response is filtered through confirmation bias: the expert interprets the confusion as evidence that the audience is unprepared, inattentive, or insufficiently intelligent — rather than as evidence that the message was poorly calibrated. Each failed communication attempt confirms the expert's belief that the problem lies with the audience, not with their own inability to exit their knowledge state. A founder who pitches to ten investors and hears "I didn't really understand what you do" ten times will, under the influence of this loop, conclude that they need smarter investors rather than a clearer pitch. Confirmation bias protects the Curse of Knowledge from correction by reinterpreting every disconfirming signal — every confused face, every misunderstood directive, every churned user — as someone else's failure rather than the expert's communication deficit.
Reinforces
Empathy Gap
The Curse of Knowledge is, at its core, an empathy failure — the inability to reconstruct the emotional and cognitive state of someone who lacks your information. The empathy gap, first described by George Loewenstein, refers more broadly to the difficulty of predicting how one would feel in a different emotional or informational state. The two biases reinforce each other because the Curse of Knowledge eliminates the very signal that would trigger empathic correction. An expert who could accurately perceive how confusing their explanation sounded would naturally simplify it. But the expert's knowledge makes the explanation sound clear to them — suppressing the empathic alarm that would otherwise fire. The reinforcement is bidirectional: the Curse of Knowledge creates the communication gap, and the empathy gap prevents the expert from feeling the audience's experience of that gap. Together, they produce the characteristic pattern of expert communication: confident delivery, baffled reception, and mutual frustration — with neither party understanding why the other is reacting as they are.
Section 8
One Key Quote
"Once we know something, we find it hard to imagine what it was like not to know it. Our knowledge has 'cursed' us. And it becomes difficult for us to share our knowledge with others, because we can't readily re-create our listeners' state of mind."
— Chip Heath & Dan Heath, Made to Stick (2007)
Chip and Dan Heath placed this observation at the centre of Made to Stick — a book that became one of the most influential business communication texts of the twenty-first century — because their research into why some ideas survive and others die kept returning to the same root cause: the communicator's inability to exit their own knowledge state. The Heaths argued that the Curse of Knowledge is the single biggest barrier to effective communication — not lack of information, not poor speaking skills, not audience hostility, but the systematic failure of the knower to model the unknower's experience.
This finding aligned with Newton's tapping study, with Camerer's economic experiments, and with decades of communication research across disciplines. The convergence was striking: cognitive psychologists, economists, linguists, and communication researchers had all independently identified the same phenomenon — that knowledge, once acquired, fundamentally and permanently alters the knower's ability to communicate with the unknowing.
The quote's power lies in the word "cursed." It is not a metaphor chosen for drama. It describes a genuine cognitive imprisonment: the expert is trapped inside their knowledge, unable to escape it even temporarily, unable to perceive the world as their audience perceives it. Every founder who has watched an investor's eyes glaze over during a pitch, every teacher who has watched a student's face go blank during an explanation, every product designer who has watched a user struggle with something "obvious" has experienced this curse firsthand. The knowledge that makes you the right person to build the product, explain the concept, or lead the organisation is the same knowledge that makes you the wrong person to communicate as if you hadn't built, explained, or led anything yet.
The practical implication is that communication excellence is not a talent to be discovered but a discipline to be engineered. The Curse of Knowledge cannot be overcome through effort or awareness alone — it must be circumvented through structural practices: testing on unknowing audiences, writing in narrative rather than shorthand, starting from the audience's knowledge state rather than your own, and treating every moment of audience confusion as diagnostic information about your communication rather than about their comprehension.
The quote also illuminates why the Curse of Knowledge is a tier-one bias rather than a curiosity: it operates on every communication, in every domain, at every level of expertise. The physicist explaining quantum mechanics, the founder explaining a product, the manager explaining a reorganisation, the doctor explaining a diagnosis, and the teacher explaining long division are all trapped in the same cognitive prison. They know the melody. They are tapping. And they genuinely cannot understand why the listener hears only noise. The gap between the tapper's experience and the listener's is the gap that determines whether ideas spread or die, whether products are adopted or abandoned, and whether organisations cohere or fragment. It is the most consequential communication variable in business, and it is invisible to the person who controls it.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
The Curse of Knowledge earns Tier 1 placement because it is the cognitive bias most directly responsible for the gap between what founders know and what they can make others understand — and that gap determines fundraising outcomes, product adoption, team alignment, and market positioning more than any other single variable. A founder with a superior product and an inferior ability to communicate it will lose to a founder with an inferior product and a superior ability to communicate it. Every time. The Curse of Knowledge is the mechanism that creates this asymmetry. It is the reason brilliant technologists build products that fail to find markets, the reason visionary leaders run organisations that cannot execute on the vision, and the reason investors pass on deals they later recognise as generational opportunities — because the person who understood the opportunity could not make them see it.
The core insight that most people miss is that the Curse of Knowledge is not about intelligence or effort — it is about the architecture of human cognition. This distinction is critical because most interventions target the wrong variable. The brain does not store "what I know" and "what I knew before I knew it" as separate accessible files. Knowledge is integrated into perception the moment it is acquired, permanently altering how the knower sees the world. An expert cannot access their pre-expert perception any more than an adult can access their pre-literate perception of a page of text. The letters are simply words now. The patterns are simply obvious now. The solution is simply self-evident now. This is not a failure of empathy or effort. It is a structural feature of how human memory and perception interact — and it means that no amount of trying harder will eliminate the bias. Only structural interventions work.
The most underappreciated dimension of the Curse of Knowledge is its compound effect on organisations. This compounding is what makes the bias a Tier 1 concern for any scaling company. Every new piece of shared context that a leadership team accumulates — every board meeting, every competitive analysis, every customer conversation — widens the knowledge gap between leadership and the rest of the organisation. The gap compounds over time, which is why communication problems in organisations tend to worsen as the company matures, not improve. Early-stage startups have small Curse of Knowledge gaps because everyone shares the same context. As the company grows and the leadership team's context diverges from the frontline's, the Curse of Knowledge produces an escalating series of communication failures that are diagnosed as "culture problems" or "alignment issues" when their root cause is cognitive: the people making the decisions cannot imagine what those decisions look like to people who were not in the room when the decisions were made.
Section 10
Test Yourself
The Curse of Knowledge is uniquely difficult to test for because the bias operates on the test-taker as well — if you understand the concept, you may overestimate how obvious the correct answer is. These scenarios are designed to surface the specific pattern: an expert whose knowledge prevents them from accurately modelling their audience's experience, leading to communication failures that the expert attributes to the audience rather than to themselves.
The critical distinction in each scenario is between two explanations for a communication failure: the audience lacked the capacity to understand (an audience problem) or the communicator lacked the ability to exit their knowledge state (a Curse of Knowledge problem). In practice, the Curse of Knowledge explanation is almost always correct when the audience is otherwise intelligent and motivated — because the bias is universal, automatic, and invisible to the person experiencing it. The audience-blaming explanation is the one that feels right to the expert. The Curse of Knowledge explanation is the one that is right.
The diagnostic question in every scenario is the same: is the communication failure caused by the audience's limitation or by the communicator's inability to exit their own knowledge state? The Curse of Knowledge is operating whenever an intelligent, well-intentioned communicator consistently fails to connect with an intelligent, well-intentioned audience. The telltale sign is the attribution: when the communicator blames the audience — "they didn't get it," "they weren't sophisticated enough," "they need to do more homework" — the Curse of Knowledge is almost certainly the actual cause.
Is the Curse of Knowledge shaping this outcome?
Scenario 1
A SaaS founder demos her product to a room of prospective enterprise customers. She moves briskly through the interface, pointing out the API integration panel, the webhook configuration, and the custom RBAC settings — features she knows are the product's key differentiators. After the demo, the feedback forms reveal that most attendees could not describe what the product does. The founder tells her team: 'We need to find more technical buyers — this audience wasn't sophisticated enough.'
Scenario 2
A senior engineering manager writes a technical design document for a new microservices architecture. She distributes it to the full engineering team — 40 people across four teams, ranging from senior architects to junior engineers hired in the last three months. At the review meeting, the senior architects engage productively. The junior engineers are silent. The manager interprets this as 'the juniors need to do more homework before these meetings.'
Scenario 3
An investor passes on a deal after a founder's pitch, telling a colleague: 'The product is interesting but I couldn't figure out the business model.' The founder had spent twelve of fifteen minutes explaining the technical innovation and three minutes on monetisation. The founder later tells a mentor: 'That investor just doesn't understand deep tech.'
Section 11
Top Resources
The Curse of Knowledge literature spans cognitive psychology, behavioural economics, communication theory, and design thinking. The strongest foundation begins with Camerer, Loewenstein, and Weber for the formal economic analysis, advances to the Heaths for the communication applications, and deepens with Pinker for the linguistic and cognitive dimensions. For practitioners, the most immediately useful resources are those that translate the psychological finding into actionable communication frameworks — how to structure a pitch, write a memo, design an onboarding flow, or lead an all-hands meeting in ways that systematically account for the audience's knowledge state rather than assuming it mirrors your own.
The combination of theoretical understanding (why the bias exists) and practical frameworks (how to design communications that circumvent it) is essential because the Curse of Knowledge cannot be overcome through awareness alone. The resources below are ordered from the most practically actionable to the most theoretically foundational, reflecting the priority for operators who need to improve their communication outcomes before they fully understand the cognitive science behind the bias.
For founders specifically, the Heaths and Butterfield provide the most immediately applicable frameworks — read these before your next pitch. For investors evaluating communication risk in portfolio companies, Pinker and Krug provide the diagnostic tools for assessing whether a company can communicate its value proposition to an unknowing market. For researchers and those who want the deepest understanding of the cognitive mechanism, Camerer, Loewenstein, and Weber provide the foundational evidence that makes the practical recommendations credible.
The investment in understanding this bias pays dividends across every communication the reader will ever deliver — because the Curse of Knowledge is operating in every one of them.
The most practically useful treatment of the Curse of Knowledge for communicators. The Heaths structure the entire book around a central question — why do some ideas stick and others die? — and identify the Curse of Knowledge as the primary villain. Their SUCCESs framework (Simple, Unexpected, Concrete, Credible, Emotional, Stories) is a direct antidote: each principle counters a specific way the Curse of Knowledge distorts communication. The chapter on "The Curse of Knowledge" uses Newton's tapping study as a launchpad for concrete, actionable advice on how to communicate complex ideas to unknowing audiences. Essential for any founder preparing a pitch, writing a strategy memo, or designing a product narrative.
Pinker, a cognitive scientist and linguist, devotes significant analysis to the Curse of Knowledge as the primary cause of bad writing — particularly academic and professional prose that is impenetrable to anyone outside the author's narrow expertise. His treatment is unique in connecting the cognitive bias to specific linguistic choices: jargon, abstraction, passive voice, and nominalisation are all symptoms of the Curse of Knowledge operating at the sentence level. Pinker provides a writer's toolkit for detecting and correcting Curse of Knowledge distortions in your own prose — making this the most useful resource for founders and leaders who communicate primarily through written documents, memos, and emails.
The original paper that named the bias and demonstrated its effect in economic decision-making. Camerer, Loewenstein, and Weber showed that better-informed agents in experimental markets systematically overestimated what less-informed agents knew — even when financially incentivised to predict accurately. The paper's contribution is the formal demonstration that knowledge creates a prediction bias that rational incentives cannot eliminate, challenging the standard economic assumption that agents can accurately model others' information states. Dense but foundational for anyone who wants to understand the bias's theoretical underpinnings and its implications for market design, negotiation, and organisational communication.
Krug's classic on web usability is, at its core, a book-length Curse of Knowledge intervention for product designers. His central argument — that every moment a user spends thinking about how to use an interface rather than what they want to accomplish is a design failure — directly targets the Curse of Knowledge's effect on product teams. The book's emphasis on usability testing with real users, its critique of design-by-committee (where everyone in the room shares the same knowledge state), and its practical frameworks for evaluating interface clarity make it the most actionable resource for product teams building for audiences who do not share the team's knowledge of the product.
Butterfield's internal memo to the Slack team before the product's public launch is one of the clearest articulations of Curse of Knowledge awareness in startup history. Butterfield argues that Slack's job is not to describe its features to potential customers but to help them imagine a transformed version of their working life — because the customer has no framework for understanding "channels," "integrations," or "searchable archives" until they have experienced the transformation those features produce. The memo is a masterclass in founder-level Curse of Knowledge correction: start from the customer's current pain, not your product's current capabilities. Brief, brilliant, and immediately applicable to any founder struggling to explain what their product does to people who have never used it.
Curse of Knowledge — The expert's internal experience is rich with context, melody, and meaning. The audience receives only the surface signal. The expert cannot perceive the gap because their knowledge automatically fills it.
Tension
First-Principles Thinking
First-principles thinking — decomposing a problem into its fundamental components and reasoning upward from them — is the most effective antidote to the Curse of Knowledge because it forces the thinker to rebuild their explanation from the ground up rather than from their current knowledge state. The Curse of Knowledge encourages top-down communication: the expert starts from their conclusion and works backward, assuming the audience can follow the chain of reasoning in reverse. First-principles thinking reverses this: start from the most basic truths the audience already accepts and build upward, adding one layer of complexity at a time. Richard Feynman's teaching method was pure first-principles communication — he began every explanation with something the student already understood and added exactly one new concept at a time. The tension is productive: the Curse of Knowledge pulls the communicator toward compression and assumption, while first-principles thinking pulls toward expansion and verification. The communicator who defaults to first principles will be slower and more methodical — but far more likely to be understood.
Tension
Beginner's Mind
Beginner's mind — the Zen Buddhist concept of shoshin, approaching a subject with openness and without preconceptions — is the direct psychological opposite of the Curse of Knowledge. Where the Curse of Knowledge locks the expert into their informed perspective, beginner's mind deliberately releases that perspective and attempts to perceive the subject as if encountering it for the first time. The tension is that beginner's mind is genuinely difficult for experts to achieve, because the Curse of Knowledge is automatic while beginner's mind is effortful. A software architect who has spent twenty years building distributed systems cannot simply decide to see a system architecture diagram as a junior developer would — the patterns, the risks, the optimisations are perceived involuntarily. But the deliberate practice of asking "what would I see if I knew nothing?" — however imperfect — creates a productive counterweight to the Curse of Knowledge's automatic compression. Teams that institutionalise beginner's mind practices — fresh-eyes reviews, new-hire feedback sessions, customer shadowing — create structural opportunities for the uncursed perspective to enter the decision-making process.
Leads-to
Information Asymmetry
The Curse of Knowledge is the cognitive mechanism that creates and sustains information asymmetry in organisations and markets. When experts cannot perceive their own knowledge advantage, they cannot close the information gap — because they do not experience it as a gap. A CEO who understands the company's strategy, competitive position, and financial trajectory in granular detail operates from a fundamentally different information state than a mid-level manager — but the Curse of Knowledge prevents the CEO from perceiving just how different those states are. The result is systematic information asymmetry: the people with the most information communicate the least of it, not from secrecy but from the genuine inability to identify what others do not know. In markets, the same mechanism produces the "lemons problem" identified by George Akerlof: sellers who know the quality of their product cannot understand why buyers are sceptical, because the seller's knowledge makes the quality feel self-evident. The Curse of Knowledge does not merely contribute to information asymmetry — it is the primary cognitive mechanism through which information asymmetry persists even when all parties would benefit from its resolution.
Leads-to
[Framing Effect](/mental-models/framing-effect)
The Curse of Knowledge shapes how experts frame information — and that framing, in turn, shapes how audiences interpret it. An expert who understands a complex topic will unconsciously frame it in the language and conceptual structure of their expertise, producing a frame that is optimised for expert comprehension and hostile to novice understanding. A physician who frames a diagnosis as "a 95% five-year survival rate" versus "a 5% five-year mortality rate" is making a framing choice that the Curse of Knowledge influences: the physician's comfort with statistical language makes both frames feel equivalent, but patients experience them as profoundly different. The Curse of Knowledge leads to framing effects because the expert's choice of frame is informed by their knowledge state — and that knowledge state systematically differs from the audience's. The expert selects the frame that feels most natural to an expert, not the frame that would be most comprehensible or most useful to the audience. The result is that expert communication is doubly biased: the content assumes too much knowledge, and the frame assumes too much sophistication.
In fundraising, the Curse of Knowledge is the most common reason good companies fail to raise capital. The founder who cannot exit their knowledge state delivers a pitch that starts at step seven of a ten-step argument — because steps one through six feel so obvious that stating them seems redundant. The investor, lacking those six steps, cannot process step seven. The founder interprets the investor's confusion as a signal about the investor's quality rather than about the pitch's accessibility. The pattern repeats across twenty meetings, producing the founder's complaint that "investors just don't understand our space" — when the accurate diagnosis is that the founder has not built the cognitive bridge between their understanding and the investor's starting point. The fix is not a better deck. The fix is a pitch rehearsed in front of someone who has never heard of the company, with the explicit instruction: "stop me the moment something doesn't make sense." The first three minutes of that rehearsal will reveal more about the pitch's weaknesses than thirty hours of internal iteration.
In product design, the Curse of Knowledge is the primary driver of the gap between "designed for users" and "designed for builders." Every feature that requires a tooltip, every flow that requires a tutorial, every setting that requires documentation is evidence that the design team's knowledge contaminated their perception of usability. The corrective is not better design reviews — because the reviewers share the designers' knowledge state. The corrective is unmoderated user testing with people who have never seen the product. The five-second test (show a screen for five seconds, ask the user what it does) and the think-aloud protocol (watch a user attempt a task while narrating their thought process) are both Curse of Knowledge diagnostic tools: they reveal the gap between the designer's intent and the user's experience by removing the designer's knowledge from the evaluation entirely.
The operational defence is not "try to think like a beginner" — it is to put an actual beginner in the room. Simulation fails. Observation works. Every consequential communication — pitch decks, product launches, strategy memos, onboarding flows, marketing copy — should be tested on someone who represents the actual target audience's knowledge state before it ships. This is not a nice-to-have practice. It is the only reliable method for detecting the Curse of Knowledge's distortions, because the cursed cannot diagnose their own curse. The founder cannot evaluate their own pitch. The designer cannot evaluate their own interface. The CEO cannot evaluate their own strategy memo. In every case, the person with the knowledge is the least qualified person to judge whether the communication works for someone without it.
The Curse of Knowledge also explains why the best product onboarding experiences are built by companies that obsess over user testing rather than internal review. When a product team reviews their own onboarding flow, they are evaluating it from a knowledge state that makes every step feel logical and every label feel clear. The team cannot perceive the flow as a first-time user because their knowledge automatically fills every gap. Companies like Slack, Stripe, and Notion invested heavily in unmoderated user testing — watching real users encounter the product for the first time without any guidance — not because they lacked confidence in their design but because they understood that confidence was itself a symptom of the Curse of Knowledge. The user's confusion is the ground truth. The designer's confidence is the distortion.
One final observation: the Curse of Knowledge explains why the best communicators in any field are rarely the deepest technical experts. Feynman was exceptional precisely because he was both a first-rate physicist and a first-rate communicator — a combination so rare that we remember him for it decades later. In most fields, the deepest experts are the worst communicators, and the best communicators are people with enough expertise to understand the material but not so much that they have lost the ability to perceive it as a novice would. This is why great science journalists, product marketers, and sales engineers are so valuable — they operate in the narrow band of knowledge where understanding and communicability overlap. Founders who recognise this hire for it deliberately: they surround themselves with translators who can bridge the gap between the founder's knowledge state and every audience the founder needs to reach.
The ultimate test for any founder, leader, or communicator: take your most important message — your pitch, your product's value proposition, your strategic direction — and deliver it to someone who has no context. Not a colleague, not a friend who has heard you talk about it, not a board member who has been on the journey with you. A genuine outsider. Watch their face. Listen to their questions. The gap between what you intended to communicate and what they received is the size of your Curse of Knowledge. That gap is not a reflection of their intelligence. It is a measurement of your curse.
Scenario 4
A product team launches a new onboarding flow that they tested extensively with internal employees. The flow guides new users through workspace creation, team invitations, and integration setup in eight steps. After launch, analytics show that 60% of new users abandon the flow at step three. The product manager reviews the flow and says: 'The steps are clear and logical. Users must not be motivated enough to complete setup.'
