Core Primitive
Relationship conflict reveals important data about needs values and boundaries.
You have been reading conflict wrong
Every conflict you have ever had in a relationship carried information. Not just emotion, not just friction, not just the unpleasant sensation of two people who want different things. Information — specific, actionable data about what each person needs, what each person values, and where the structure of the relationship has a gap that neither person has addressed.
You almost certainly did not extract that information. You did one of three things instead: you fought to win, you fought to end the fight, or you avoided the fight entirely. All three responses treat conflict as a problem to be solved or suppressed. None of them treat it as what it actually is — a signal from the relational system that something requires attention.
Creating emotional safety taught you how to create emotional safety in relationships. That safety is not the absence of conflict. It is the precondition for conflict to become productive. When both people feel safe enough to disagree without fearing abandonment or attack, the disagreement can do its real work: surfacing information that the system needs in order to evolve.
This lesson teaches you to read that information.
The positions-versus-interests distinction
In 1981, Roger Fisher and William Ury published Getting to Yes, a book that transformed negotiation theory and, by extension, our understanding of how conflict works. Their central insight was a distinction that applies to every argument you have ever had: the difference between positions and interests.
A position is what you say you want. "I want you to spend less time at work." "I need more space." "You should have told me before making that decision." Positions are concrete, specific, and usually incompatible. If one person's position is "We should move to Portland" and the other's is "We should stay in Chicago," the positions cannot both be satisfied. This is why position-based conflict feels zero-sum — one person wins, one person loses, or both compromise in a way that leaves neither satisfied.
An interest is why you want what you want. The person who wants to move to Portland may be driven by a need for proximity to family, or a desire for lower cost of living, or a longing for a different pace of life. The person who wants to stay in Chicago may be driven by career investment, or deep friendships, or a need for stability during an already turbulent period. Interests are the needs, fears, values, and concerns that generate the positions. And unlike positions, interests are often compatible even when positions are not. Both people may share an interest in financial security, in maintaining close relationships, in building a life that feels sustainable. Once you move from positions to interests, the solution space expands dramatically — because there may be many ways to satisfy both people's underlying interests that neither person's original position captured.
Fisher and Ury were writing about formal negotiation between organizations and governments. But the principle applies with even greater force to intimate relationships, because the interests at stake in relational conflict are not about resources or territory. They are about attachment, identity, safety, and belonging — the deepest needs a human nervous system can have.
Marshall Rosenberg, the psychologist who developed Nonviolent Communication, built an entire framework on this same insight applied to interpersonal conflict. Rosenberg's model proposes that behind every statement in a conflict — every accusation, demand, withdrawal, or emotional eruption — is an unmet need. Not a want, not a preference, not a position. A need. And that conflict becomes constructive the moment both parties shift from arguing about strategies (positions) to identifying and acknowledging the needs those strategies are attempting to serve.
Rosenberg identified a taxonomy of universal human needs: autonomy, connection, honesty, meaning, physical well-being, play, peace, and interdependence, each with specific sub-needs. When your partner says "You never listen to me," the position is "Listen more." The need might be for respect, for mattering, for being valued — or it might be for connection, for the felt sense that the other person is genuinely present. You cannot know which need is driving the statement until you ask, and you cannot ask effectively while you are defending your position.
This is why most relationship conflict is circular. Both people are arguing about positions — about the specific behaviors they want the other person to change — while the actual needs driving those positions remain invisible, unnamed, and unaddressed. The conflict repeats because the surface issue gets resolved (or exhausted) but the underlying need does not. Two weeks later, the same need surfaces through a different position, and the cycle restarts.
Task conflict versus relationship conflict
Not all conflict carries the same kind of information. Karen Jehn, an organizational psychologist whose research has been replicated across dozens of studies, identified a distinction that is essential to reading conflict accurately: the difference between task conflict and relationship conflict.
Task conflict is disagreement about the substance of a decision — what to do, how to do it, what the priorities should be. Should we renovate the kitchen or pay down the mortgage? Should the project launch in Q2 or Q3? Should the kids attend public school or private school? Task conflict involves competing ideas, different assessments of the evidence, and genuine disagreement about the best course of action.
Relationship conflict is disagreement that targets the other person — their character, their competence, their motives, their worth. "You always do this" is relationship conflict. "I think the other approach would work better" is task conflict. "You don't care about this family" is relationship conflict. "I'm worried we're not allocating enough time to this" is task conflict.
Jehn's research found something that initially surprised the field: moderate levels of task conflict actually improve outcomes. Teams, couples, and groups that engage in substantive disagreement about ideas make better decisions than those that suppress disagreement in the name of harmony. The friction generates better analysis. The competing perspectives surface blind spots. The argument, when it stays focused on the substance, functions as a quality-control process.
Relationship conflict, by contrast, is almost always destructive. It does not generate better analysis. It generates defensiveness, contempt, and withdrawal. It damages trust. And it does not carry useful information about the task — it carries information about the relational system itself: that someone feels attacked, that the interaction has become unsafe, that the disagreement has escalated from the substance to the person.
The practical implication is that when you are in a conflict, your first task is to determine what kind of conflict it is. If you are arguing about what to do, stay in it. The argument is productive. If you are arguing about who the other person is, stop. The conflict has shifted from information-generating to information-destroying, and continuing will not produce anything useful.
Carsten De Dreu extended this work by demonstrating that task conflict only improves outcomes when it occurs in a context of psychological safety and cooperative norms. When people trust each other's intentions, substantive disagreement drives innovation. When trust is absent, even task conflict degrades into relationship conflict because every disagreement about ideas gets interpreted as an attack on the person. This is why Emotional safety in relationships and Creating emotional safety — emotional safety in relationships — are prerequisites for this lesson. You cannot read conflict as information if the relational system is too unsafe for honest disagreement to occur.
The sixty-nine percent that never get resolved
John Gottman's research produced a finding that many people find disturbing when they first encounter it: approximately 69 percent of relationship conflicts are perpetual. They never get resolved. They are not solvable problems with a correct answer that both partners will eventually converge on. They are ongoing tensions rooted in fundamental differences in personality, values, or needs.
One partner is an introvert who needs solitude to recharge; the other is an extrovert who needs social engagement. One values spontaneity; the other values planning. One wants to save aggressively for the future; the other wants to enjoy life now. These are not problems to be fixed. They are differences to be managed — permanently.
The 69 percent finding reframes the purpose of conflict in long-term relationships. If most conflicts are perpetual, then the goal is not resolution. The goal is dialogue. Gottman distinguishes between "gridlocked" perpetual problems and "dialogued" perpetual problems. In gridlock, the couple has the same argument repeatedly with increasing frustration and decreasing connection. Neither person feels heard. Both feel stuck. The topic becomes radioactive — too painful to raise, too important to ignore. In dialogue, the couple acknowledges that the difference is permanent, explores the dreams and values underneath each person's position, and finds ways to live with the tension while honoring both perspectives. The conflict does not disappear. It becomes a conversation rather than a battle.
This is conflict as information at its deepest level. The perpetual problem is telling you something fundamental about who each person is — not something that needs to be changed, but something that needs to be understood and accommodated. The conflict is not a malfunction in the relationship. It is the relationship processing a genuine difference between two people who are genuinely different.
Morton Deutsch, one of the foundational researchers in conflict studies, formalized this principle through his distinction between constructive and destructive conflict. Constructive conflict is characterized by cooperative orientation — both parties believe that their goals are positively linked, that a good outcome for one is compatible with a good outcome for the other. Destructive conflict is characterized by competitive orientation — both parties believe their goals are negatively linked, that one person's gain is the other person's loss. The same disagreement can be constructive or destructive depending entirely on the orientation. And the orientation is a property of the relational system, not the topic.
David Johnson and Roger Johnson extended Deutsch's work through their research on constructive controversy — what happens when people with opposing views engage in structured, cooperative debate. Their findings are consistent across educational, organizational, and interpersonal settings: when people argue about ideas within a framework of mutual respect and shared goals, both parties end up with more nuanced understanding, greater perspective-taking ability, and better decisions than either would have reached alone. The conflict does not just resolve the immediate question. It upgrades the cognitive capacity of both participants. Conflict, handled constructively, makes you smarter.
What the conflict is actually carrying
When you learn to read conflict as information, you discover that every disagreement carries data in at least four channels simultaneously.
Needs data. Beneath every position is a need. "You spend too much time on your phone" carries data about a need for attention, presence, or connection. "Stop telling me what to do" carries data about a need for autonomy or respect. The conflict is the delivery mechanism for information about needs that have not been articulated directly — often because the person experiencing the need has not identified it consciously. They know they are upset. They do not know what they need. The conflict is the system's attempt to surface that information.
Values data. Recurring conflicts often reveal values that are held deeply but have never been explicitly named or negotiated. If you keep fighting about how to spend weekends, the conflict may be carrying data about different values regarding family time, personal freedom, productivity, or adventure. These values are not right or wrong. They are facts about what matters to each person. The conflict is trying to put those facts on the table so the relationship can account for them.
Boundary data. Some conflicts carry information about boundaries that have been crossed, eroded, or never established. "I don't want your mother commenting on our parenting" is boundary data. "I need you to ask before committing us to plans" is boundary data. "I am not willing to have this conversation when you are yelling" is boundary data. The conflict is the system's alarm that a boundary needs to be defined or defended.
Structural data. Many conflicts are not about needs, values, or boundaries at all. They are about missing agreements — structural gaps in how the relationship operates. Who is responsible for what? How are decisions made? What are the rules about money, time, space, communication, and accountability? When these structures are absent or ambiguous, conflict fills the gap. The argument about who should have taken out the trash is not about trash. It is about the absence of a clear system for distributing household responsibilities. The conflict is information about a structural problem that can only be solved by building the structure.
Susan David, whose work on emotional agility has influenced both clinical practice and organizational psychology, frames this principle succinctly: emotions are data, not directives. The anger you feel during a conflict is not an instruction to attack. The hurt is not an instruction to withdraw. They are signals — data points that, when read accurately, tell you something important about what is happening in the relational system. The skill is learning to receive the data without being commanded by it.
How to extract the information
Reading conflict as information is a practice, not an insight. The insight — "conflict carries data" — takes ten seconds to understand intellectually. The practice of actually extracting that data in the middle of a disagreement, when your nervous system is activated and your prefrontal cortex is partially offline, takes months to develop.
The process has three phases, and they must happen in order.
Phase one: Acknowledge the emotion. Before you can extract information from a conflict, you have to metabolize the emotional charge. This means naming what you feel, out loud if possible. "I am feeling defensive right now." "I notice I am getting angry." "This is hitting a nerve for me." The acknowledgment does two things: it signals to the other person that you are present and honest, and it creates enough distance between you and the emotion for your analytical capacity to come back online. Skip this phase and the other person will not trust your analysis — because it will feel like intellectualization rather than genuine engagement.
Phase two: Shift from positions to interests. Once the emotional charge has been acknowledged, begin asking interest-based questions — of yourself and the other person. "What am I really asking for here?" "What do you need most right now?" "What would it look like if we both got what we actually need?" These questions transform the conflict from a contest between incompatible positions into a joint investigation of compatible interests. This is where Rosenberg's NVC framework is most useful: observation, feeling, need, request. What happened? What do I feel? What do I need? What am I asking for?
Phase three: Name the pattern. If the conflict is recurring, the most valuable information is not in the content of any single instance — it is in the pattern across instances. "We keep having versions of this argument. What is the pattern telling us?" This meta-level question often reveals the structural or values-level data that individual conflicts obscure. The pattern is the signal. The individual arguments are noise.
The limits of the framework
This framework has real limits, and ignoring them would be irresponsible.
Not all conflict is between people of good faith operating within a fundamentally safe system. When one party is manipulative, abusive, or acting in consistent bad faith, the conflict does not carry useful information about shared needs. It carries information about power, control, and danger. In those situations, the appropriate response is not to extract data from the conflict. It is to protect yourself and, if necessary, exit the system.
Even in healthy relationships, some conflicts are genuinely zero-sum. If one person needs to live near their aging parents and the other needs to live near their workplace, and those locations are in different cities, no amount of interest-based negotiation will make both positions simultaneously achievable. The conflict carries real information — that the relationship faces a genuine constraint — but the information does not automatically produce a solution. Some conflicts reveal incompatibilities that must be lived with, negotiated around, or occasionally accepted as the limit of what the relationship can accommodate.
And the timing matters. Extracting information from a conflict while the conflict is at peak intensity is often impossible and sometimes counterproductive. The nervous system in full threat-response mode is not capable of nuanced data analysis. Gottman's research shows that when heart rates exceed roughly 100 beats per minute — a state he calls "diffuse physiological arousal" — the capacity for perspective-taking, empathy, and creative problem-solving drops precipitously. The information in the conflict does not expire. It can be extracted after both people have returned to baseline. The skill is knowing when to engage the analysis and when to simply survive the wave.
From information to evolution
The purpose of reading conflict as information is not to become a detached analyst of your own relationships. It is to give the relational system what it needs to evolve.
Every relationship is a living system, and living systems require feedback to adapt. Conflict is feedback. When you suppress it, the system loses the data it needs to adjust. When you let it escalate destructively, the data gets corrupted by contempt and defensiveness. When you learn to read it — to hear the needs underneath the positions, to see the values underneath the frustration, to identify the structural gaps underneath the recurring arguments — you give the system clean information. And systems with clean information adapt.
The next lesson, The complaint versus the criticism, takes this principle to a more specific level. It examines the distinction between complaints and criticisms — two forms that conflict takes, with radically different informational content. A complaint addresses a specific behavior: "You did not call when you said you would." A criticism attacks the person: "You never follow through on anything." The complaint carries information. The criticism carries ammunition. Learning to distinguish them — in yourself and in others — is the next step in becoming literate in the language of relational conflict.
Conflict is not the enemy of connection. Unread conflict is.
Sources:
- Fisher, R., & Ury, W. (1981). Getting to Yes: Negotiating Agreement Without Giving In. Penguin Books.
- Rosenberg, M. B. (2003). Nonviolent Communication: A Language of Life (2nd ed.). PuddleDancer Press.
- Gottman, J. M., & Silver, N. (1999). The Seven Principles for Making Marriage Work. Crown Publishers.
- Gottman, J. M. (2011). The Science of Trust: Emotional Attunement for Couples. W. W. Norton.
- Jehn, K. A. (1995). "A Multimethod Examination of the Benefits and Detriments of Intragroup Conflict." Administrative Science Quarterly, 40(2), 256-282.
- Deutsch, M. (1973). The Resolution of Conflict: Constructive and Destructive Processes. Yale University Press.
- Johnson, D. W., & Johnson, R. T. (2007). Creative Controversy: Intellectual Challenge in the Classroom (4th ed.). Interaction Book Company.
- De Dreu, C. K. W., & Weingart, L. R. (2003). "Task Versus Relationship Conflict, Team Performance, and Team Member Satisfaction: A Meta-Analysis." Journal of Applied Psychology, 88(4), 741-749.
- David, S. (2016). Emotional Agility: Get Unstuck, Embrace Change, and Thrive in Work and Life. Avery.
- Ury, W. (1991). Getting Past No: Negotiating in Difficult Situations. Bantam Books.
Frequently Asked Questions