I spent most of last year trying to learn one small skill: to look at things before naming them. It turns out to be surprisingly hard and unexpectedly generative.
The problem with naming first
The instinct, when something interesting happens — a strange bug, an awkward meeting, a sentence that doesn’t sit right — is to immediately name it. To classify, to compare, to slot it into an existing category. “Ah, this is a race condition.” “Ah, this is a power struggle.” “Ah, this is just a bad metaphor.”
The naming feels like understanding. It is often the opposite. Once you have named a thing, you have decided what it is like, which means you have decided what it is not worth looking at more closely. The name is a small cognitive door that closes behind you.
What looking-first looks like
Looking, before naming, is awkward. You catch yourself wanting to call the thing something. You sit with the discomfort. You write down literally what you saw, in physical detail, before reaching for the abstraction.
A few small examples from the year:
- A bug I had filed under “concurrency issue” turned out, on slow observation, to be a config-loading order issue with a concurrency-shaped symptom. The name had been wrong for six months.
- A meeting I had filed under “she’s blocking the project” turned out to be a person asking the question no one else was asking, in a register I was misreading as resistance. The name had cost me a year of cooperation.
- A sentence in my own writing that I kept calling “elegant” turned out, on re-reading, to be evasive. The name had been the thing protecting it.
Each time, the thing I was looking at had been the same for months. What changed was that I stopped naming it.
The craft
You can practice this. It is not abstract. The minimum loop:
- Pick a thing you have a fast name for.
- Describe it in three sentences without using the name.
- Notice what shows up that the name had been hiding.
Over months, the habit re-tunes what you notice. You start catching the moment of premature naming as it happens. You buy yourself a second of delay, and inside that second, all sorts of things you had been editing out become visible.
Why it matters
The thing worth saying, in the end, is small:
Most of what we call thinking is recognition. Real observation is what happens before recognition.
If the goal is to write things that are still useful in ten years — or to build software that is still maintainable, or relationships that are still honest — the prerequisite is to see what is actually there, not what you have already named.
The craft is the small, daily refusal to close the door too soon.