Chapter 2: Thinking or Overthinking?

Priya and Tomás had been friends since university, and on the same Monday, each of them received a job offer.

The offers were similar in shape. Each came with a raise and a more senior title, and each meant moving to a city a few hours away. Each was exciting and frightening in roughly equal measure. They texted each other the news, and both stayed up late that night.

Here is what Priya did over the next six days.

On Tuesday she wrote down what she wanted from the next stage of her career: room to grow, a manager she could learn from, and enough money to stop worrying about rent. She noticed that the offer met two of the three and was unclear on the third. On Wednesday she called a former classmate who worked at the company and asked two specific questions about the manager and the team’s turnover. On Thursday she emailed the recruiter to ask about flexibility for visiting her family. The reply came on Friday. Over the weekend she went for a long walk, noticed that her stomach unclenched whenever she pictured herself saying yes, and on Sunday evening she accepted. She was still nervous. But she could name exactly what she was nervous about, and the list was short.

Here is what Tomás did.

On Monday night he wrote a list of pros and cons. On Tuesday night he read the list again and added nothing. On Wednesday he began to wonder how he would feel in a year if he took the job and hated it, and then how he would feel if he turned it down and his old job soured. On Thursday he asked four friends for their opinions, received four slightly different answers, and spent the evening weighing each friend’s credibility. On Friday he reread the offer email, searching for hidden signals in its wording. By the second week he was reciting the same pros and cons at two in the morning, in the same order, in nearly the same words.

Tomás did not care less than Priya. If anything, he cared more. He did not think for fewer hours; he thought for many more. He was not less intelligent or less careful. What differed was what the thinking did. Priya’s thinking kept producing something: a list, a call, an email, a clearer sense of her own preferences. Tomás’s thinking had stopped producing anything after Tuesday. It was moving, but it was not going anywhere.

Thinking is not the enemy

Before going further, one clarification, because it matters for everything that follows. This book is not against thinking. Thinking is how we plan, learn, make amends, solve problems, and understand ourselves. A person who never reflected would be neither wise nor kind. The aim of this book is not less thinking. It is thinking that works, and the ability to notice when it has stopped.

The trouble is that useful thinking and exhausting thinking often start from the same place, with the same question, and with the same sincere intention. From the inside they can be hard to tell apart. So it helps to have a map.

Four kinds of thinking

Psychologists distinguish many forms of repetitive thought, but four are enough for everyday life.

Reflection is thinking in the service of understanding. In a 1999 paper, the psychologists Paul Trapnell and Jennifer Campbell separated reflection, a self-focus driven by curiosity or genuine interest, from rumination, a self-focus driven by perceived threats, losses, or injustices. People drawn to reflection tended to be more open to new experience, while people prone to rumination tended to experience more negative emotion. The lesson for us is that the motive behind a thought matters as much as its topic. Curiosity opens a question. Fear guards it.

Problem-solving has a finish line. It asks what can be done, chooses something, and moves. When Priya called her classmate, she was problem-solving: she had identified a gap in what she knew and went to fill it.

Worry looks ahead and asks what might go wrong. It is not useless; it is how we notice real risks. But worry has a slippery quality. Unlike a problem, a hypothetical can generate endless variations: What if the job is great but the city isn’t? What if the city is great but the team changes? What if the team stays but the company is sold? Each answer produces another question, and none of them can be resolved by thinking alone.

Rumination looks backward or inward and asks why: why did this happen, why am I like this, why can’t I get past it. Its questions tend to be broad, evaluative, and unanswerable, and they tend to end in verdicts about the self.

Notice that these are not four personality types. All of us move among them, sometimes within a single hour. Tomás began in problem-solving mode on Monday and slid, around Wednesday, into worry. The skill is not to avoid any of the four. It is to catch the slide.

The same question, twice

Here is a subtle point that clears up a lot of confusion: *the same question can be useful once and exhausting the fiftieth time.*

Imagine you leave a meeting convinced it went badly. Asking yourself, that evening, what happened in there? is reasonable. You may realize you rushed your opening, or that one person misunderstood your point, or that the problem was not you at all. That is reflection, and it produces information.

Now imagine asking the identical question for the sixth night in a row, without having learned anything in between. The question has not changed. What has changed is that it no longer has anything left to give. You are not investigating anymore; you are circling.

The psychologist Edward Watkins has studied a related distinction that is worth borrowing. He and his colleagues have found that repetitive thought tends to be more harmful when it is abstract and less harmful when it is concrete. Abstract thinking asks broad, global questions: Why do I always mess things up? What is wrong with me? Why does this keep happening? Concrete thinking asks about specifics: What exactly happened in the first five minutes? What was the moment it shifted? What is one thing I could try differently next time? The first kind tends to deepen distress and stall action. The second kind tends to move us toward something we can use.

This is not a trick, and concrete questions don’t magically remove pain. But it gives us a practical rule of thumb: when a question is vague, sweeping, and about your worth as a person, it is probably not going to be answered by thinking harder. When it is specific, small, and about what happened or what to do, it often can be.

A note on useful worry

It would be unfair to say that worry never helps. The psychologist Julie Norem has described a strategy she calls defensive pessimism, in which some people deliberately imagine what could go wrong before an important event and then use that imagining to prepare in detail. The musician who pictures the string breaking and therefore packs a spare is using worry well.

What distinguishes this from a loop is that the imagining leads somewhere. It ends in a packed spare string, a rehearsed answer, a backup plan. Useful worry has an exit. When imagining a bad outcome produces no preparation and only more imagining, it has stopped being preparation and become something closer to a rehearsal of dread.

The Progress Test

How, then, do we tell the difference in the moment, when we are tired, and the loop feels like diligence?

Here is the simplest tool I know. Ask yourself one question: *Has this thought helped me understand, decide, or do anything new?*

There are three ways to pass, and each is deliberately modest. Understand: I see something about this that I did not see before. Decide: I now know which way I am leaning. Do: I have identified a step I can actually take.

The word that matters most is new. Thinking about the same problem is fine, even necessary. Thinking about the same problem without anything new arriving is the signature of a loop. By this test, Priya’s Wednesday phone call passed immediately. Tomás’s Friday re-reading of the offer email did not, and he could have known that by asking. When nothing new arrives, treat that as a cue to change strategy, not as an order to stop thinking: gather information, make a plan, or set the question down for now.

A few ways to use this test well:

• Be kind about it. The test is a question, not a verdict. If the honest answer is no, that is useful information, not a failure.
• *Don’t turn it into a weapon. I’m overthinking again, what is wrong with me?* is just another loop wearing a different coat. Ask the question lightly, like checking a clock.
• Allow a “not yet.” Sometimes a thought needs time. If you are waiting for a reply, or for your own feelings to settle, the test may honestly return not yet. The point is to notice the difference between waiting and circling.

What to do when the answer is no

The Progress Test does not tell you to stop thinking. You already know how well that works. It tells you that this particular kind of thinking has stopped paying, and it opens a short list of better options:

• Get new information. If a gap in knowledge is feeding the loop, close it. Ask, look it up, or run a small test. Priya’s calls and emails were not an interruption of her thinking; they were her thinking, extended into the world.
• Make it concrete. Turn a why or a what if into a what is one thing I could do? Even a small step, such as drafting a message you may or may not send, shifts the mind from circling to building.
• Park it on purpose. Write the thought down, with a note such as come back to this on Saturday at ten. This isn’t suppression. It is telling the mind it has been heard and giving it somewhere to put the worry, which makes it easier to set down.
• Change the channel. Move your body, call someone, cook something that needs both hands. Absorbing activity doesn’t solve the problem, but it can interrupt the groove long enough for you to come back with a clearer head.
• Let yourself feel it. Sometimes a loop is standing in for a feeling that hasn’t been allowed to arrive: sadness, fear, or anger. If the thinking seems to circle around something heavier than the topic, try naming the feeling quietly instead of analyzing it. We will return to this idea many times.

None of these is a cure, and none will work every time. Think of them as doors. The Progress Test is how you notice that you are standing in a room with no windows; the list is a reminder that the room has doors.

Try this: The Progress Test in practice

For the next week, practice the test at three natural moments each day. A good cue is any time you notice you have been on the same topic for about ten minutes.

1. *Pause and ask: Has this thought helped me understand, decide, or do anything new?*

1. If yes, keep going, and write down the new thing in one line. This trains you to recognize real progress.

1. If no, choose one door: get information, make it concrete, park it, change the channel, or feel the feeling.

1. Afterward, notice. What happened when you stepped out of the loop? Did the problem feel smaller, the same, or just quieter? There is no right answer. You are collecting evidence about how your own mind works.

You may find that on some days you ask the question ten times and the answer is no every time. That is fine. The habit of asking is the practice, and it is quietly building the skill that matters: the ability to step slightly outside your own thoughts and see what they are doing.

When it helps most. The Progress Test works best on thoughts that cannot be settled tonight: the replayed conversation, the decision with no new facts. It is less useful in the middle of a strong emotion, when the question can feel cold. In those moments, wait until the wave eases and then ask. A realistic goal is not that the answer always changes, but that you ask more often and sooner, until asking becomes a habit you barely notice.

A THOUGHT TO CARRY

Thinking asks, what do I know now that I didn’t know before? Overthinking asks the same question again, hoping for a different answer.