One interview goes badly and the thought that arrives isn’t “that interview went badly.” It’s “I never get these.”
Notice what happened in the gap. One event became a rule. And the rule isn’t about the interview any more — it’s about you, and it extends forward into every interview you’ll ever have.
What it is
Burns’ definition is a single sentence: “You see a single negative event as a never-ending pattern” [1].
The important word is single. Overgeneralization isn’t noticing a real pattern — patterns exist, and spotting them is useful. It’s building a pattern out of one data point, or two, and then treating it as settled. The evidence is a sample of one. The conclusion is a law.
What makes it worth catching is that the conclusion is usually a claim about the future, dressed as an observation about the past. “This never works out” sounds like a summary of your history. It functions as a prediction — and predictions change what you do next.
What it sounds like
- “This never works out for me. I always fail.”
- “I’m always the one who has to reach out.”
- “Nobody ever texts me first.”
- “Every time I try this, the same thing happens.”
The tell is unmistakable once you’re listening for it: always, never, everyone, nobody, every time, nothing ever. Absolute quantifiers attached to something that has happened once, twice, or a handful of times.
Here’s a useful test. Take the sentence and try to falsify it with one counterexample. “Nobody ever texts me first” — has anyone, ever, once? Almost always yes, and almost always you can name them. The claim doesn’t survive a single counterexample, which tells you it was never really a claim about frequency. It was a claim about how you feel, wearing the grammar of a fact.
Why it’s convincing
Because generalizing is what minds are for. Turning repeated experience into a rule is the core trick of learning — touch a hot pan once, update permanently. The machinery works exactly as designed. It just fires on too little data when you’re upset, because a bad mood makes matching memories easier to reach, so the two or three supporting examples come to hand instantly and the dozens of counterexamples don’t come at all.
That’s why arguing with it in your head rarely works. You’re not short of counterexamples; you’re short of access to them in that moment. Which is the strongest argument for writing it down: on a page you can go looking for the exceptions deliberately, instead of waiting for them to surface on their own.
It also spreads. Burns notes that labeling — “I’m a failure” rather than “I made an error” — is “an extreme form of overgeneralization,” where instead of describing the mistake you attach the label to yourself [1]. One event becomes a pattern, and then the pattern becomes an identity.
How to catch it
Hunt the absolutes. Always, never, everyone, nobody. Circle them. They are the highest-yield words in this entire list of patterns.
Count the actual instances. Not how it feels — how many times, specifically. “I never get these” usually means “this is the second one this year.” Two is not never, and it’s not a pattern either.
Find one counterexample. Just one. You’re not trying to prove the opposite, only to break the word never, because once it’s broken the sentence has to be rewritten and the rewrite is automatically more accurate.
Rewrite it with a number and a time. “That’s two interviews this year that didn’t go my way” says the same thing without the prophecy attached.
What to do once you’ve caught it
The fairer version of an overgeneralization is almost always the specific version. Replace the rule with the event: not “I always mess this up” but “I mishandled the start of that call.” Specific is smaller, truer, and — unlike a law of nature — something you can actually do something about.
Then keep the entry, because this pattern is uniquely well suited to being caught by your own records. Three weeks of entries is a real sample. If you wrote “this never works” four times and three of those things worked, your own notes settle the argument in a way that no amount of thinking in bed ever will.
The other nine patterns are in the guide to cognitive distortions. Its closest neighbors are all-or-nothing thinking, which supplies the verdict that gets generalized, and mental filtering, which supplies the selective evidence.
How aMind helps with overgeneralization
The problem with this pattern is not that you lack counterexamples. It is that you cannot reach them while you are upset, because a low mood serves up the matching memories and hides the rest. Arguing with never inside your own head is a rigged fight.
That is the exact thing a written record fixes, and it is why aMind keeps everything in History on your device. When you write “this never works out”, the entries from the last three weeks are sitting right there, and they either support you or they do not. Most of the time they do not, and seeing that in your own words settles the question in a way that thinking about it never will. Inside a single reflection the same logic applies at a smaller scale: the evidence step asks what supports the thought and what argues against it, so the exceptions get written down instead of waiting to be remembered.
