Detail Aversion Heuristic (Reds)
Erikson portrays Reds as impatient with detail and suggests linking essential checks to the results they want. The practical lesson is to show which details affect an outcome rather than assume a personality label predicts behavior.
THE IDEA
“Details … Boooooring…”
In Erikson’s framework, Reds dislike getting into details. It’s boring and takes time. Thus, Reds tend to be careless about small matters. You can accuse Reds of many things, but meticulousness isn’t typically one of them. For them the destination will always be more important than the journey, so Reds will do just about anything to achieve the desired results. Reds won’t naturally stop to consider the small things or analyze their method.
Conclusion: If you really want to help Reds do better work, try to demonstrate the benefits of keeping an eye on the details. Explain that the results will be better and profits larger if they just consider a couple of small but crucial elements of the project.
Be prepared for the huff and puff and a general unwillingness to act on your advice. A clear link to the desired result may make your advice more persuasive. As we know, Reds are good at pushing themselves to the limit, just as long as they make headway.
When to use it
Coaching a Red team member to improve quality by showing how attention to detail directly improves final results and profitability.
When assigning tasks in a project, balance detail-heavy work with result-oriented tasks to keep Reds engaged while ensuring thoroughness.
In negotiations, a Red might overlook contract fine print—use this heuristic to remind them to get a quick legal review before signing.
If you tend to skip details, identify the checks that matter for the decision and allow enough time to complete them.
FROM THEORY TO EVERYDAY LIFE
In practice
Red Manager Skips Report Review
A Red manager receives a detailed quarterly report but skims it quickly and makes a strategic decision based on the headline numbers, missing critical footnotes about market risks. The decision later leads to a costly oversight.
Project Speed Over Quality
In a software development project, a Red team member pushes to release a feature quickly without thorough testing, arguing that 'it works well enough.' Bugs appear post-launch, requiring extra fixes.
A MOMENT TO REFLECT
Put it to work.
Think of a time you avoided diving into details because it felt tedious. What was the outcome, and could a small detail have changed it?
How can you reframe detail-oriented tasks for yourself or a Red colleague to highlight the link to achieving bigger goals?
If you are a Red, what system could you put in place to ensure critical details aren't overlooked without sacrificing your result focus?
CONTINUE THE CONVERSATION
Source texts
- Surrounded By Idiots (Thomas Erikson)