#244: Is-a-Has-a-Error, Reification & Ultimate Attribution Error
3 Ideas in 2 Minutes on Thinking Errors
I. Is-a-Has-a-Error
In complex systems, a common thinking mistake is the Is-a-Has-a Error. “Is-a” defines what something fundamentally is (a dog is an animal), while “has-a” describes something it merely contains or uses (a dog has a collar). That distinction sounds trivial. But when designers blur it, systems can end up assigning authority to the wrong component.
Take aviation. An aircraft has an autopilot, but it is not an autopilot. The autopilot is just one optional control system. When software is designed as if the aircraft is basically an autopilot system, control logic flips. Automation may still be treated as authoritative even when it’s disengaged, while manual pilot inputs are partially ignored.
Occasionally, you may even want to remind yourself that you are not your job. You merely have one, meaning it’s one part of your life and not your entire identity.
II. Reification
Reification is what happens when we start treating an abstract idea like it’s a concrete thing you could point to or put on a table. Our brains naturally like to think in terms of “things”, so we often turn processes or relationships into objects without noticing. It’s a shortcut that makes complex reality easier to talk about.
An everyday example is when someone says, “Stress is attacking me lately.” Stress isn’t actually a physical force doing something. It’s a word for a pattern of bodily and psychological responses. But talking about it like an external thing with its own agency makes it feel more tangible and easier to communicate.
Once you notice the habit of Reification, you start seeing it everywhere…
III. Ultimate Attribution Error
The Ultimate Attribution Error is your mind’s built-in PR team working overtime. [See what I did there?] We attribute negative actions of out-group members to their character while attributing their positive actions to situational factors (and vice versa for our-group members).
Let’s say someone on your side does something good. Your brain immediately writes a glowing character reference: “See? Bob is smart, kind and competent. Bob’s a legend.” But when the same person messes up, the story changes instantly: “That’s just because of all the stress that’s been attacking Bob lately.”
However, if someone we dislike does something admirable, we suddenly become master minimisers: “Well, Ben was just lucky,” or “Anyone could’ve done that”. But when Ben screws up? That was no accident. Now it’s treated as a window into his deep, flawed soul. One mistake becomes proof of “what Ben’s really like”.
What makes this error especially sneaky is how natural it seems. It doesn’t feel like Confirmation Bias, it feels like common sense. In reality, you’re running two completely different explanation systems at the same time. A generous, context-sensitive one for “us”. And a harsh, personality-based one for “them”. So don’t let your internal PR team go rogue. It’s supposed to serve you, not take over. 🐘
Have a great week,
Chris
themindcollection.com