What does it mean that emotions are data not directives?

Emotions provide information about your internal state — they do not command action.

Example: You are in a project retrospective when a colleague says, "I think we would have shipped on time if the architecture had been scoped properly" — a comment aimed, however politely, at your design decisions. A flush of heat rises through your chest. Your jaw tightens. The emotion — a compound of anger, embarrassment, and defensiveness — arrives with a built-in instruction set: correct the record, point out the constraints you were under, remind the room who actually stayed late to fix the deployment pipeline. But you have trained yourself to treat emotions as data. So instead of executing the instruction set, you pause and ask: what information does this feeling contain? The anger says a boundary has been crossed — someone is assigning blame without full context. The embarrassment says part of you wonders if the criticism has merit. The defensiveness says your competence is being publicly questioned and your status feels threatened. Three distinct data points, each useful, none of which require you to speak in the next five seconds. You note the data. You decide, based on your values and the situation, to address the scope constraints calmly after the meeting in a one-on-one conversation. The emotion informed the response. It did not dictate it.

Try this: Three times today, when you notice an emotion arise — any emotion, positive or negative — pause and complete this sentence in writing or in your head: "I am feeling [name the emotion], and the data it contains is [what it tells me about my situation, needs, or values]." Do not act on the emotion immediately. Simply extract the data. At the end of the day, review your three entries. Notice whether the data the emotions contained would have led to the same action as your first impulse, or whether the pause revealed a different and better response.