What does it mean that observation and evaluation are different acts?

Observation and evaluation are neurologically distinct operations. Your brain can register what is happening before deciding whether it is good or bad — but only if you train the pause between the two. Collapsing them into a single act distorts perception and triggers defensive reactions in others.

Example: During a code review, an engineering lead writes: 'This function is poorly structured.' The author gets defensive, the conversation stalls, and the actual design issue goes unresolved for another sprint. A week later, reviewing a different PR, the same lead writes: 'This function has four levels of nesting and two exit paths that skip the validation step on lines 47 and 62.' The author immediately sees the structural problem and refactors it in twenty minutes. The same defect, two different outcomes — one mixed observation with evaluation, the other separated them.

Try this: Pick a fifteen-minute window today — a meeting, a commute, a conversation. Carry a notepad or open a blank document. For the full fifteen minutes, write down only what a camera would record: behaviors, words spoken, timestamps, physical facts. No adjectives that encode judgment (avoid 'good,' 'bad,' 'lazy,' 'brilliant,' 'slow,' 'aggressive'). After the window closes, review your notes and circle any evaluation that slipped in. Most people find three to five evaluations hiding in what they thought was pure description. The gap between what you intended and what you wrote is the size of your observation-evaluation conflation habit.