The Curse of Knowledge
The "curse of knowledge" is a cognitive bias where you unconsciously assume that others have the same background and context that you do. It's the primary reason technical explanations fail. The key to overcoming it is to be deliberate about your audience.
The ELI5 (Explain Like I'm 5) Technique
This isn't about being condescending; it's about stripping away jargon and focusing on the core concept. Before explaining something, ask yourself: "What is the absolute simplest way I can describe this?"
- Start with the "Why": Why does this matter? What problem does it solve?
- Use Analogies: Compare complex systems to simple, real-world concepts (e.g., "An API is like a restaurant waiter—it takes your order and brings you what you requested from the kitchen.").
- Avoid Acronyms and Jargon: If you must use a technical term, define it immediately.
Structuring Your Explanation
A well-structured explanation is easier to follow. Use the "What, So What, Now What" framework:
- What? - "Here is the situation. We have a bug where users can't reset their passwords." (State the core fact clearly).
- So What? - "This is important because it's locking users out of their accounts and increasing support tickets by 50%." (Explain the impact).
- Now What? - "My proposal is to patch the authentication service. I estimate it will take four hours." (Propose the next step or solution).
Practice: The next time you're on a call, consciously listen for jargon. When you hear an acronym you don't know, ask for clarification. This helps build a culture of clarity.