When a small feeling is better left unnamed
I've spent this whole series saying name it. So it's only fair to share a study that says: not always.
It's a useful correction, and it fits the way I try to work: measure what you want, and let the results change the method.
The study
Einat Levy-Gigi and Simone Shamay-Tsoory ran two experiments on affect labeling, the habit of naming a feeling to soften it (Affect labeling: the role of timing and intensity, Levy-Gigi and Shamay-Tsoory, 2022).
In the first, 63 people looked at upsetting pictures and chose one of two words for the feeling, either while seeing the picture, right after it, or ten seconds later. Timing made no difference. Naming lowered distress in all three cases. That's helpful in itself: you don't have to name a feeling at the perfect moment. A little later works too. If you couldn't find the word in the moment, you can still find it on the way home.
The second experiment, with 79 people, changed how intense the pictures were. For strong pictures, naming reduced distress, as expected. For mild ones, it did the opposite. Naming the feeling made people more distressed.
The words were chosen from two options, in a lab, so this is a gentle and controlled kind of naming. Real life is messier. But the direction is clear enough to take seriously.
Why naming a small thing can grow it
The authors give a plain example: a driver who names every small annoyance on the road may end up feeling worse, not better. When a feeling is barely there, naming it may draw attention to it, and attention feeds it.
I recognise that. On a calm day, if I stop to label every flicker, "slightly irritated, a bit bored, faintly uneasy", I end up more irritated, bored and uneasy than when I started. Naming is a tool for weight, and a small feeling doesn't weigh much yet.
It's one study, and it needs repeating, so I hold it lightly. But it fits a good habit from work too.
Size it before you name it
In Scope it before you fight it I wrote about sizing a problem before taking it on. Teams do this all the time. A Scrum team doesn't call a meeting about every tiny bug. Small things get noted and handled in the normal flow of work. And the ROAM board from Four names for a worry has a word for risks a team chooses to live with: Accepted.
So I've added a size check before naming. My rough rule:
- if it's a 1 or 2 out of 10 and passing, let it pass. No label needed;
- if it keeps coming back, or rises to about 5, name it;
- if it's strong, name it straight away, even in the middle of things.
The numbers are my own rule of thumb, not from the study. The point is the shape: match the tool to the size.
What this means for measuring
Here, the number that matters is intensity. Before I name, I rate. It takes two seconds and stops me turning small moods into projects.
It also keeps the tool sharp. If I name everything all day, naming becomes noise. If I keep it for the feelings that matter, it still has its edge when a big one arrives.
It also connects to the two-week test in You'll think naming won't work. If you tried that test, look at the times the number went up after naming, and check how big the feeling was to begin with. If it was small, this study may explain why.
The series in a few lines
Looking back over these pieces, the method is simple. Name the big feelings, the obstacles, the risks and the plans. Say the fear while you face it. Add a because, and test the name. Use your own name when you need distance. Measure what matters. And let the small stuff pass without a label.
That's still name it, tame it. Taming includes knowing when to leave a thing alone. If you want the method on one page, it's on the Name it sheet, and the words I use are in the glossary.
I'm not a doctor, and this isn't therapy. It's a way of seeing that helps me. If you are struggling, please talk to someone you trust or a professional.
Name what weighs on you. Let the small things pass. Knowing the difference is part of the skill.