Curse of Knowledge
Once you know how something works you cannot accurately imagine not knowing, which is why teams misjudge their own interfaces.
Definition
A bias in which better-informed people find it difficult to reason about a problem from the perspective of a less-informed person. Camerer, Loewenstein and Weber demonstrated it economically in 1989; Newton's 1990 tapping study is the best-known illustration.
Established research. Originates in published research and has been replicated. The effect is real. Its size in your product still needs measuring.
On this page
Why internal review is not usability testing
A team that built the product cannot evaluate its learnability. They know the vocabulary, the model and the location of everything, and that knowledge cannot be suspended by intending to. Confidence that something is obvious is not evidence that it is.
This is the strongest single argument for testing with five people who have never seen the product, and for treating any internal claim that a label is clear as a hypothesis rather than a finding.
Countermeasures
- Test with people outside the team, however informally.
- Watch a new user's first five minutes without helping them.
- Read support tickets and search logs directly, not summarised.
- Have someone unfamiliar with the domain review the copy.
- Ban internal vocabulary from user-facing text unless research shows users use it.
In practice
The obvious button nobody found
Usability testingTeams routinely watch participants fail to find a control the team considers unmissable. The reaction is usually disbelief, which is the bias operating in real time.
Missing first steps in documentation
Developer docsSetup guides commonly omit a prerequisite the author has had installed for years. New users stall at step zero, and the fix is a literal walkthrough by someone starting clean.
Sources
Where a source establishes something narrower than the popular reading of it, the note says so.
The curse of knowledge in economic settings: an experimental analysis
C. Camerer, G. Loewenstein and M. Weber, Journal of Political Economy, 1989
The rocky road from actions to intentions
E. Newton, Stanford University doctoral dissertation, 1990
The tappers and listeners study.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Explains
The mechanism underneath these entries.
- Help and DocumentationHeuristic
- Match Between System and the Real WorldHeuristic
Why this works
The reasoning this entry rests on.
- Usability TestingResearch method
Testing exists because you cannot un-know your own interface.
Applied through
Where this shows up as a concrete interface decision.
- Screenshot to UX AuditAI workflow
- Guerrilla TestingResearch method
- Heuristic EvaluationResearch method
- MicrocopyUX writing
- Design CritiqueWorkflow
Often used with
These usually appear in the same screen or the same decision.
- Design CritiqueTemplate
- Usability Test ScriptTemplate
Practical example
A worked decision where this was the deciding factor.
- Fixing a Search That Returned NothingCase study
Related concept
Connected closely enough to change how you apply this.
- Confirmation BiasCognitive bias
- Mental ModelsMental model
- Paradox of the Active UserPsychology