What It Means If You Get Frustrated When People Explain Things Too Slowly
You know the feeling. Someone is walking you through something step by step — carefully, thoroughly, making sure you understand each part before moving to the next. And somewhere around step two, something in you starts to strain.
You already know where this is going. You understood the concept three steps before they introduced it. And now you're sitting in a kind of polite tension, nodding, waiting, trying not to let it show on your face that you finished processing this a while ago.
This frustration is real. And it's more informative than most people realise.
What frustration with slow explanation actually signals
When information arrives slower than your brain can process it, your brain doesn't idle. It keeps running. It fills the gap with its own activity — completing the explanation internally, generating follow-up questions, making connections to other things, or simply starting to wander.
The frustration you feel isn't impatience in the ordinary sense. It's cognitive friction. The mismatch between how fast your brain wants to move and how fast it's being allowed to move creates a specific kind of discomfort — like being stuck in traffic when you can see the open road ahead.
This is a reliable signal that your processing speed is significantly higher than the rate at which information is being delivered.
Why this isn't the same as arrogance
This matters to say clearly, because a lot of fast-processing people carry guilt about this.
Getting frustrated when things move too slowly is not the same as thinking you're better than the person explaining. It's not dismissiveness. It's not disrespect. It's a neurological response to a speed mismatch — and it would happen even if the person explaining was someone you deeply admire, teaching something you genuinely care about.
The frustration isn't about them. It's about the pace.
The situations where this shows up most
**In meetings.** When the agenda moves through things you absorbed in the first thirty seconds. When context is being established that you already have. When a decision is being approached slowly and carefully that seems straightforward to you.
**In training and onboarding.** When a process is being explained in more detail than you need. When examples are being used to illustrate something that was already clear from the principle.
**In one-on-one conversations.** When someone is building to a point you can already see. When they're being careful and thorough in a way that, from inside your head, feels like circling.
**In instructions of any kind.** Written, verbal, visual — if they're paced for a lower processing speed than yours, the friction appears.
What nobody tells you about this
The people who explain things slowly are not, in most cases, misjudging your ability. They're calibrating to an average they've learned to expect. Most people need more explanation than you do. Most people benefit from the extra steps. The careful, thorough explainer isn't doing something wrong — they've just optimised for a different cognitive profile than yours.
The frustration you feel is real and valid. And it's not something you can simply decide not to feel. But understanding why it happens makes it considerably easier to manage — because you stop interpreting it as the other person wasting your time and start recognising it as a speed differential that's no one's fault.
The skill worth developing
The most useful thing to build isn't patience — at least not in the passive, grit-your-teeth sense. It's active listening at speed.
This means using the cognitive surplus you have — the processing capacity that isn't being used by what's being explained — deliberately. Not to mentally leave the conversation, but to go deeper into it. To think about edge cases. To consider what might complicate the picture being painted. To generate questions worth asking.
This transforms slow explanation from something to endure into something to use. And it has an unexpected side effect — you often emerge from carefully paced explanations with a richer understanding than you'd have gotten from a faster version of the same thing. Not because the pace added information. Because you did.
If this resonates, it's not coincidence. The frustration you feel in slow-paced environments is one of the most consistent characteristics of a specific thinking style — and understanding yours gives you a precise map for why you work the way you do.
