Have you ever tried to explain something you know extremely well, only to discover that the other person looks completely lost? Maybe you skipped steps you didn’t realize were important. Maybe you used terms you didn’t think needed explaining. Or maybe you jumped straight to the “advanced” part because the basics felt too obvious.
There’s a name for that.
What Is the Curse of Knowledge?
The curse of knowledge is a well-known psychological phenomenon where knowing something so well actually makes it harder to explain to people who are new to it. Once we master a subject, it becomes difficult to remember what it was like not to know it. We unconsciously assume others have the same background, experience, or vocabulary.
In forums, tutorials, and technical discussions, this can create confusion — not because the teacher is doing anything wrong, but because their expertise makes it easy to skip essential steps.
The good news? It’s completely fixable.
How to avoid the Curse of Knowledge
1. Write for “you from 20 years ago”
A simple trick: imagine you’re explaining the topic to a much younger version of yourself, before you learned everything you now take for granted.
This naturally helps you slow down, clarify steps, and avoid assumptions.
2. Remove hidden assumptions
Even small assumptions can trip up beginners. When giving instructions, don’t assume readers know:
- which directory they should be in
- whether a command requires root or sudo
- what a package does
- which application they should be using
- where configuration files are located
Making fewer assumptions makes your writing clearer for everyone.
3. Explain concepts before commands
People learn more effectively when they understand why they’re doing something.
Instead of simply listing commands, add one sentence explaining the purpose behind each step. It requires almost no extra effort but makes your explanations dramatically more accessible.
4. Use examples
Examples turn abstract ideas into something concrete. If you’re writing about Linux, coding, woodworking, or anything technical, include:
- sample commands
- expected outputs
- before-and-after comparisons
- brief code or configuration snippets
Examples reduce confusion and give readers confidence.
5. Start with the destination
Before diving into details, tell readers what they will achieve.
For example:
“By the end of this guide, you’ll have Bluetooth working in LXQt, auto-connecting at login, and managed by PipeWire.”
When people know where they’re headed, the steps make more sense.
6. Ask beginners where they get stuck
If you run a forum or help others often, you have an incredible advantage: beginners will tell you exactly where your explanations are unclear. Use their feedback to refine what you wrote.
Teaching improves fastest when you learn from the people you teach.
7. Assume the reader is smart but uninformed
This helps avoid two traps:
- talking over their head
- talking down to them
Think of your reader as fully capable — they just haven’t been exposed to the material yet.
8. Share your own learning process
When you’re doing a task, keep notes on:
- steps that surprised you
- places you hesitated
- things you had to look up
- mistakes you made along the way
These are the exact points a beginner will struggle with. Turning them into part of your explanation makes your writing vastly more helpful.
9. Use “incremental disclosure”
Give information in layers:
- A simple, working solution for beginners
- Additional options for intermediate users
- Advanced tweaks for experts
Everyone reads the part they need, and no one feels overwhelmed.
Why this matters
Whether you’re writing a tutorial, explaining a process, or posting on a forum, keeping the curse of knowledge in mind helps you communicate more clearly — especially with newcomers. It lowers frustration, builds confidence, and encourages more participation from people who might otherwise feel intimidated.
In short: being an expert is valuable, but being able to share that expertise clearly is even more powerful.