November: The Rational Human

4 min read

Core idea

Rationality is harmony, not suppression

The common misconception is that being rational means tamping down emotion — a kind of ascetic self-denial that is virtuous but joyless. Greene rejects this. Rationality is the harmony between emotion and thinking, in which feeling supplies the motive force and thinking supplies the direction. Neuroscience supports the point: patients with damage to the emotional centres of the brain become incapable of deciding anything. Without emotion you cannot even begin to be rational.

The higher self versus the lower self

Greene splits human nature into two pulls. The lower self is reactive, defensive, distractable, tribal — the path of least resistance. The higher self is thoughtful, outward, persistent, individuated. The lower self is stronger by default; the higher self emerges only through effort and structure. The November work is a programme for spending more of your hours in the higher self — not by repressing the lower self but by routing its energy into projects, relationships, and goals that compound.

Why it matters

The rational human is buildable

Greene's hope is empirical: throughout history there have been people of high rationality — Pericles, Marcus Aurelius, Lincoln, Darwin, Chekhov, Mead, Buffett — and they share specific qualities you can cultivate. Realistic self-appraisal. Devotion to truth over flattery. Tolerance toward people. The ability to set a goal and reach it. None of these are gifts; all of them are practices. The rational human is not a saint but a particular kind of operator.

You have already been rational — in flashes

Most of us have lived through what Greene calls the maker's mindset — a project with a deadline that demanded all of our focus and made other people's drama feel like static. In those weeks, the lower self quieted. Other emotions felt like interference. We worked, we shipped, we felt better than usual. These episodes are evidence: the rational self is not a stranger. It is a familiar guest you have not learned to invite consistently.

Key takeaways

Mental model

Mental model

Practical application

  1. Lengthen your reaction time. For one month, do not send any emotionally-charged message for at least 24 hours after writing it. Write it; leave it; revisit the next day. Most will be deleted unsent.

  2. Audit the whirlpool. List the three people whose dramas have consumed the most of your week. For each, decide whether you are obligated to engage or whether you have been pulled in. Withdraw from the second category for a month and observe.

  3. Run the envy-to-action conversion. Pick one person whose success you envy. Spend an hour reading or watching their actual work. Write down three specific things they did that you have not done. Schedule one of them this week.

  4. Practice Mitfreude once a day. When someone reports a success — a promotion, a publication, a milestone — respond first with genuine pleasure, not with the comparative thought that floods in next. The skill is starving the comparative thought of oxygen by giving the pleasure-response more time on the field.

  5. Mark your maker's-mindset weeks. Look back over the last year and identify the periods you were most rational. What were you working on? What conditions did you have? Reproduce one of those conditions next month.

Example

The angry email that becomes a strategy memo

Suppose you receive a piece of feedback at work that lands as a personal attack. Your blood is up; you draft a reply in your head that catalogues every error in the feedback, every prior incident that proves your colleague is the real problem, every reason this is unjust. The lower-self path is to send some version of that — possibly compressed and softened, but still essentially a defence.

The higher-self path runs differently. You notice you are activated, and you put the response off until tomorrow. Overnight, you ask the harder question: what specifically in the feedback hurt? You find one sentence. You ask: is there a kernel that is accurate? You find a smaller kernel than the feedback claimed, but real. You ask: what would a more useful version of this conversation accomplish — for the project, not for my ego?

The next day you write a different message. You acknowledge the kernel concretely. You ask one question about the part you disagree with rather than refuting it. You propose a small concrete change you can both observe. The conflict de-escalates; the project moves forward; your colleague's view of you improves; and you have spent the energy of the anger on something that compounds rather than on something that drains. The horse pulled the cart somewhere useful, because the rider was awake.

Continue exploring

Tags