Subject: What I mean when I say “need” Last time, I wrote about conditional worthiness — how the standards we apply to others eventually become the standards we live under ourselves. If you haven’t read it yet, that piece lives in the archive here: [[26-2-23]]. That conversation about worth led me somewhere deeper. Before we decide who is worthy, before we decide how to treat people, we are constantly deciding something more subtle: what counts as a need. The word _need_ carries weight. When we use it, we’re invoking something fundamental — something that feels non-negotiable. I’ve been experimenting with a more careful way of using it, because I’ve noticed that when I’m sloppy with this word, my conversations get rigid. Here’s the frame I’m proposing: A need is a universal requirement for a happy and fulfilling human life — something true across personality, culture, and circumstance. Connection qualifies. Autonomy qualifies. Meaning qualifies. Safety, rest, dignity, understanding — these qualify. A specific job doesn’t. A specific person doesn’t. Immediate agreement doesn’t. Those can matter deeply. But they are strategies. Needs are the underlying human requirements. Strategies are the methods we use to meet them. Connection is a need. Texting back immediately is a strategy. Respect is a need. Agreeing with me is a strategy. Security is a need. Controlling the plan is a strategy. When we blur those categories, conflict hardens. If I say, “I need you to text me back immediately,” I’ve labeled a strategy as non-negotiable. Now you’re defending your autonomy instead of helping me meet my need for reassurance. But if I say, “When I don’t hear from you, I start to feel disconnected. I need reassurance that we’re okay,” we’re collaborating on the real thing. The strategy becomes flexible. The need stays steady. There’s also a common linguistic trap here: we use “need” as disguised authority. “You need to calm down.” “We need to fix this.” “I need you to change.” These sentences don’t name universal human requirements — they prescribe behavior. And prescriptions tend to trigger resistance. The other person doesn’t hear care; they hear indictment. If what I’m calling a need cannot be framed as a universal human requirement, it’s probably a preference or a strategy. And preferences are negotiable. This way of thinking overlaps with work from Marshall Rosenberg and others who emphasize distinguishing needs from strategies. Rosenberg even keeps a “library of needs” — categories like connection, autonomy, meaning, peace, play — as a way of helping people identify what’s actually alive underneath their reactions. I’ve collected a version of that library at the bottom of my own article on needs here: [[Needs]]. It’s a helpful reference when you’re trying to find the universal layer beneath a specific demand. Rosenberg would say that many negative emotions arise when needs aren’t being met. I don’t think that explains everything about human emotion — but as a diagnostic tool, it’s powerful. So here are three practices I’m trying. First: translate strategy into need. When I hear myself say, “I need you to…,” I pause and ask: what universal requirement am I actually protecting? Connection? Security? Respect? Clarity? Second: separate need from person. “I’m needing respect right now” describes something human and universal. “You need to respect me” assigns obligation. One invites collaboration. The other invites defense. Third: assume shared humanity. If it’s truly a need, the other person has it too — even if they express it differently. You both need autonomy, but not necessarily in the same form. You both need connection, but not through the same strategy. Most conflict isn’t bad people colliding; it’s two valid needs colliding at the level of method. Here’s the micro-habit I’m experimenting with: In your next moment of tension, identify the need first. Name it out loud if you can. Then, instead of defending a single strategy, work with the other person to design multiple ways that need could be met. Treat the need as fixed. Treat the strategies as creative. And here’s why I think this matters beyond just smoother conversations. Language shapes perception. Perception shapes action. If I regularly speak as if my strategies are universal needs, I slowly train myself to see the world as a place of noncompliance and threat. If I regularly translate my reactions down to shared human requirements, I train myself to see other people as negotiating the same core realities I am. That shift in language is small. But small linguistic shifts compound into worldview. And worldview eventually expresses itself in action. So here’s the invitation I’m working with: The next time you feel tension — with someone else or with yourself — ask: What need of mine is active? What need of theirs is active? Name the universal requirement first. Then design the strategy. Be careful with the word _need_. The way you use it doesn’t just shape the conversation in front of you. It shapes the world you believe you’re living in — and the kind of person you become inside it.