How to Explain Something Complicated (Without Making the Other Person Feel Stupid)
To explain something complicated without making someone feel stupid, start from what they already know, say 'we' about the hard parts, and call the topic hard rather than the person slow. Ask 'where does this get fuzzy?' instead of 'does that make sense?', and let them finish your thoughts.
- Start from something they already know.
- Say 'we' about the parts that are hard.
- Call the topic hard, not the person slow.
- Ask 'where does this get fuzzy?' instead of 'does that make sense?'
- Leave room for them to finish your sentences.
Explaining something complicated without condescending depends more on framing than on content. Starting from a familiar idea, using 'we' for the difficult parts, describing difficulty as a feature of the material, and checking understanding with an open question ('where does this get fuzzy?') rather than a yes-or-no one ('does that make sense?') all keep the listener on equal footing. Pausing so they can complete the logic themselves is often the clearest sign the explanation has worked.
Halfway through, they stop asking questions and nod too much. The next morning they ask you to repeat the parts they said they understood. You weren't condescending on purpose, but the dynamic flipped from two people figuring something out to one being talked down to.
Where should you start when explaining something complicated?
Open with the part they're definitely familiar with, even if it's not the actual topic. 'You know how when you forward an email, the original is still there?' Then build the new thing on top. They feel oriented before they feel asked to stretch. The opposite — opening with the unfamiliar concept and asking them to follow — turns the conversation into a quiz. When the confusion is your own, Missing Link traces which earlier idea a concept depends on and finds the one that's missing.
What words make an explanation feel less condescending?
Watch the pronoun. 'You probably know that...' puts the burden on them. 'We sometimes get tripped up by...' puts the difficulty in the material itself, where it belongs. The grammatical shift is small. The status shift is huge. They're no longer the person who doesn't know — you're two people working through a thing together.
How do you explain something hard without making someone feel slow?
When something genuinely is hard, name that out loud. 'This part is genuinely confusing — lots of people need to hear it twice.' 'This is the bit where the analogy breaks down.' You're telling them that struggling is normal, not a sign that they're slow. People will engage with hard material when they trust that the hardness is in the material, not in them.
How do you check someone actually understood?
Asking 'does that make sense?' invites them to lie. Asking 'where does that get fuzzy for you?' invites them to point at the actual gap. Build pauses that require them to say something specific — what they understood, what they didn't, where you went too fast. The questions you ask determine whether you get real feedback or polite reassurance.
How can you tell your explanation has landed?
The strongest signal you've explained something well is when they start completing your thoughts. Make room for that. Slow down where the logic is about to land. Give them the half-second to predict the next beat. When they say 'oh — so it's like X,' don't correct them unless they're really wrong. Let them own the connection. That's when they actually learned it.
Find the right framing — for the right person
Analogy Engine takes any concept and the specific person you're explaining to — and finds the framing that respects what they already know.
Found this useful? Link to it.
https://deftbrain.com/guides/conversations/how-to-explain-something-complicated-without-making-someone-feel-stupid
Free to read, no account, no paywall — link away.