Condescension is speaking from an assumed superiority that quietly erases the other person's mind, and it happens most easily to people who actually know a lot.
Condescension usually starts from a position of assumed superiority. I understand this better than you. I know what you need. I can see what you can't. Sometimes that assumption is even justified, because you may have more expertise, more information, or more experience. But expertise and superiority aren't the same thing, and people can almost always feel the difference. Learning not to be condescending is a genuine communication skill, and it's harder than being polite, because it requires keeping the other person's mind, competence, and agency intact while you speak.
The obvious forms are easy to spot. Talking down to someone, using a patronizing tone, explaining elementary concepts to an expert, correcting someone in public, speaking to an adult as though they were a child.
The more interesting forms are quieter, and most of them come from good intentions. You explain before finding out what the person already knows. You give advice when they were just giving you information. You interpret their experience for them, or tell them what they're feeling, or reassure them about a worry they never voiced. You simplify a complex issue because you assumed they wouldn't follow it. You praise them for something any competent adult would be expected to do. You keep teaching after they've already understood. You answer the question you think they should have asked instead of the one they actually asked. Each of these can come from a warm place and still communicate the same thing. I am the one who understands, and you are the one who needs help.
People who know a lot are especially prone to this, and there's a specific reason why, beyond arrogance.
Once you've developed real expertise, something happens to your perception that you can't easily undo. Concepts that once took effort become automatic. Background knowledge arrives without being summoned. You see patterns fast, anticipate where an argument is going, and often know the answer before the other person has finished the question. That efficiency is valuable, and it also produces a well-documented cognitive bias. Camerer, Loewenstein, and Weber called it the curse of knowledge. Once you know something, you genuinely struggle to reconstruct what it was like not to know it, which makes you systematically overestimate what other people already understand (Camerer, Loewenstein, & Weber, 1989). The expert isn't only being presumptuous. They've partly lost the ability to model a mind that doesn't contain what theirs does.
This is where expertise shades into a failure of mentalizing, the capacity to stay genuinely curious about what's actually in another person's mind rather than filling it in from your own (Fonagy et al., 2002). You stop finding out what this particular person knows, believes, wants, or has already considered, and start responding to the pattern instead. Sometimes you're right about the pattern. But being right about the pattern isn't the same as being right about the person in front of you.
Accidental condescension almost always contains an imagined deficiency, a story you've invented about what the other person doesn't understand. Someone says they're considering leaving the company, and you respond with a lecture about not making impulsive career decisions, though they never said it was impulsive. Someone describes a disagreement with an employee, and you start explaining emotional regulation, though they never said they lost control. Someone mentions a financial decision, and you begin explaining risk, when they may have modeled it more carefully than you have.
The problem isn't simply unsolicited advice. It's that the advice reveals the deficiency you assumed was there. That assumed gap, more than any tone of voice, is where patronizing communication actually begins.
The discipline is to calibrate before you explain. Before giving information, find out what the person already knows. Before giving advice, find out whether advice is wanted. Before interpreting someone's experience, check whether your interpretation matches theirs. Before simplifying, find out what level of detail would actually help.
This takes a sentence, not a seminar. You may already know this, but there's one piece that might matter. Do you want my read, or are you mostly thinking out loud? I have a hypothesis about what's happening. Does it fit your experience? How much background would be useful? These aren't verbal niceties. They're ways of fixing an information problem you actually have, which is that you don't yet know what the other person knows.
When you do need to say something with weight behind it, four moves keep it from tipping into condescension. Start with what you actually observed rather than what you inferred. "The last three deadlines were missed" is observable. "You don't seem to understand the importance of deadlines" claims access to their mind.
Then locate your view as yours, not as reality itself. "My concern is that this creates risk for the team." "The way I'm reading it is." "From where I sit." It's a small move that stops your interpretation from being presented as the fact of the matter.
Then offer rather than impose. "I see one possible issue, want my read?" "There may be another way to think about this." "I can tell you what I've seen in similar situations, if that's useful." An offer leaves room for the other person to know something you don't.
And then return the agency. "What do you think?" "Does that fit?" "You know the situation better than I do, what am I missing?" The point isn't to soften your position into mush. It's to avoid taking over theirs.
Condescension often hides inside ordinary language. You need to understand. What you have to realize is. Let me explain something to you. Obviously. It's actually pretty simple. You'll understand when. I think what you're really feeling is. What you should do is. None of these is offensive on its own. The problem is what they presume, which is that you know and the other person doesn't, that your reading outranks theirs, or that the right answer is already settled.
A more equal version keeps the substance and changes the stance. "The part I think matters most is." "One thing I'm seeing differently is." "My read is." "Here's the tradeoff I'd watch." "I may be missing context, but." The difference is epistemic humility, which is confidence about what you know paired with an honest acknowledgment of what you don't.
Condescending communication often sounds very certain, and certainty gets mistaken for authority. But more sophisticated communication usually contains more differentiation, not less. You can know the facts without knowing the motive. You can see the pattern without knowing what produced it. You can hold real expertise without knowing what this particular person should do. You can disagree without assuming the other person failed to understand.
This is why strong communicators separate observation from interpretation. "You interrupted me three times" is not "You don't respect me." "She hasn't responded in four days" is not "She's trying to manipulate you." "He declined the promotion" is not "He's afraid of responsibility." The second statement in each pair might be true, but it requires an inference, and presenting an inference as a fact is one of the fastest ways to sound patronizing, because it casts you as the authority on someone else's inner life.
Advice tips into hierarchy easily, because the adviser occupies the position of knowing and the recipient the position of needing. Good advice usually starts with enough curiosity to check whether the problem is even the one you think it is. Sometimes the person doesn't want a solution, they want a sounding board. Sometimes they already know the solution and haven't decided whether they'll pay its cost. Sometimes they're not asking what you would do, they're working out what they think. Sometimes they have information you don't. The fastest route to patronizing someone is to solve a problem before understanding how they see it.
Psychological knowledge creates its own sharper version of the trap. Once you've learned words like projection, avoidance, defenses, attachment, or trauma, you can start interpreting people instead of relating to them. You're just projecting. That's your anxiety talking. You're being defensive. You clearly have a control issue. Perhaps. But psychological vocabulary doesn't grant privileged access to another person's mind, and using it to close an argument can be more condescending than plain criticism, because it claims superior knowledge of their motives. Used well, psychology generates hypotheses rather than verdicts. "I wonder whether something about losing control feels especially hard here." "I'm noticing this gets more charged when the conversation turns to competence." "Is there something I'm missing about why this matters so much?" Psychology should increase curiosity, not end it.
Someone else's condescension is also information. It may tell you they need to hold the expert position, or get uncomfortable when they aren't the most knowledgeable person present, or equate helping with being valuable, or struggle to imagine that others know things they don't, or manage their own anxiety through certainty. It may just be an unexamined habit. You don't need to diagnose which. You can notice the pattern without absorbing the hierarchy it implies. Someone speaking to you as though you're less competent doesn't make you less competent. Their communication tells you how they're positioning you, and you still get to decide whether that position is accurate.
None of this requires pretending everyone knows the same amount. Sometimes you are the expert. Sometimes you do know the thing they don't. Sometimes you have to correct a mistake, give direction, or make a decision they won't like. The skill is doing that without erasing the other person's mind.
You can say "This decision is mine, and here's how I'm thinking about it" without saying "Once you have more experience, you'll understand why this is right." You can say "There's an error in this analysis, let me show you where" without saying "I think you're confused about how this works." You can be fully authoritative without becoming superior. The distinction is whether you're using your knowledge to clarify the problem or to fix your position above the other person.
So before you correct, advise, interpret, or explain, two quick questions catch an enormous amount of accidental condescension. What am I assuming this person doesn't know? And then, do I actually know that? The goal isn't to become hesitant or endlessly deferential. It's to speak from accurate information instead of an imagined hierarchy. Know what you know, find out what they know, say what you see, and leave the other person in possession of their own mind. That's the difference between helping someone think and thinking for them.
Camerer, C., Loewenstein, G., & Weber, M. (1989). The curse of knowledge in economic settings: An experimental analysis. Journal of Political Economy, 97(5), 1232–1254.
Fonagy, P., Gergely, G., Jurist, E. L., & Target, M. (2002). Affect regulation, mentalization, and the development of the self. Other Press.
Stay ahead with insight-driven leadership strategies that rewire thinking, enhance decision-making, and decode human dynamics.
50% Complete
Subscribe to our Leadership Insights Newsletter and stay ahead of the curve with high-impact strategies designed for high-agency executives who play at the highest levels.