Chapter 16: Before You Begin — Diagnosing the Real Problem

Opening: The Prepared Mind

Dr. Priya Okafor sat at her desk on a Tuesday evening after rounds, her office door closed, a blank legal pad in front of her. She had been putting this conversation off for three weeks.

Dr. Alejandro Vasquez had joined her department eight months ago. Brilliant diagnostician. Well-liked by nursing staff. And his patient documentation was, to put it plainly, a disaster — incomplete discharge summaries, late chart entries, progress notes that read like telegrams. Two near-misses in the billing cycle had been traced back to his paperwork. Priya's department head had flagged it. The time had come.

She picked up her pen and wrote at the top of the page: Documentation problem — Vasquez.

Then she stopped.

In the emergency department, Priya had been trained to never start treatment from the presenting symptom alone. A patient who comes in complaining of chest pain might have a pulmonary embolism, might be having a panic attack, might have pericarditis, might have musculoskeletal strain from shoveling snow. The symptom is real. The symptom matters. But the symptom is not the diagnosis. You do the workup first. You ask: What is actually happening here?

She looked at what she had written. Documentation problem — Vasquez.

Was that the diagnosis? Or was that the symptom?

She thought back over the eight months. Vasquez had come from a smaller regional hospital where, she now recalled someone mentioning, the documentation culture had been notoriously lax. When had she explicitly told him what was expected in this department? She tried to remember a specific conversation. She tried to remember handing him a documentation standards guide. She tried to remember a 30-day check-in about his onboarding.

Nothing.

She had assumed he knew. She had assumed that "everyone knows" the standards. She had assumed that a physician of his experience would simply meet expectations that she had never articulated.

Priya set her pen down. The discomfort that moved through her chest was not quite guilt and not quite embarrassment — it was something more precise. It was recognition.

The documentation problem was real. Vasquez's charts were genuinely deficient. The near-misses had genuinely happened. All of that was true. But if she walked into that conversation tomorrow morning as though she were confronting a doctor who had been negligent and evasive, she would be working from an inaccurate diagnosis. And inaccurate diagnoses, in her experience, produced treatments that made things worse.

She wrote a new header: What is the real problem here?

This chapter is about learning to ask that question — and developing the tools to answer it rigorously before you say a single word to another person.

16.1 The Presenting Problem vs. the Real Problem

In medicine, a "presenting complaint" is what the patient reports when they walk through the door. "My knee hurts." "I've been tired for two weeks." "There's a rash on my arm." These reports are essential information, but they are the beginning of the diagnostic process, not the end. A physician who treats the presenting complaint without doing the diagnostic workup is practicing dangerously. The presenting complaint is a signal. The diagnosis is what explains it.

Conflicts work the same way, and yet almost every difficult conversation begins — and too often ends — at the level of the presenting problem.

The presenting problem is what triggered the conversation. It is visible, it is recent, and it is specific. It is the thing that finally made the situation feel urgent enough to address. The dishes in the sink. The meeting that started without you. The report that was late again. The comment that landed wrong.

The real problem is the pattern beneath the trigger, the unmet need beneath the behavior, the structural issue beneath the incident. It is usually less visible, often older, and almost always more significant. Dishes in the sink might be a presenting problem for an underlying conflict about division of household labor, about fairness, about one partner feeling invisible. The late meeting might be a presenting problem for an underlying issue about whose time is treated as valuable. The missed deadline might present as an accountability problem when the real problem is that expectations were never made explicit.

Why do we so consistently conflate the two?

They are proximate. The presenting problem just happened. It is fresh, and fresh things demand attention. Our brains are wired to respond to the immediate stimulus.

They are concrete. The dishes are physical objects. The late report has a timestamp. These can be pointed to. The underlying need for respect or clarity or fairness is abstract, harder to name, easier to dismiss as vague or emotional.

They provide a target. The presenting problem has a clear villain — the person who left the dishes, the person who missed the deadline. The real problem is frequently murkier, often implicates us as well, and resists the clean narrative of wrongdoer and wronged party.

They offer the illusion of quick resolution. If the problem is really just the dishes, we can solve it right now. If the problem is actually about equity and partnership in a shared household, that takes a longer, more uncomfortable conversation. It is psychologically easier to pretend the problem is the dishes.

This pattern — presenting problem mistaken for real problem — is one of the most reliable predictors of conversations that go badly, or that must be repeated. You solve the dishes argument today; it erupts again in three weeks about the laundry. You address the late report; the same dynamic resurfaces in the budget meeting. You keep treating symptoms, and the underlying condition continues to progress.

Three Diagnostic Questions

The first move in conflict diagnosis is to slow down and ask three questions. These are deceptively simple questions that turn out to be surprisingly hard to answer honestly.

Question 1: What triggered this conversation?

Describe the specific incident, behavior, or event that made you decide this conversation needed to happen — or that made the conflict surface. Be precise. Be behavioral. Avoid evaluative language.

Not: "Tyler is irresponsible and keeps letting the team down." But: "Tyler submitted the Henderson report two days after the agreed deadline, and this is the third time in eight weeks that a deliverable has been late."

Not: "My mother keeps treating me like a child." But: "Last week, my mother called me three times in one day when I hadn't responded to her text, and then asked my older sister to check on me."

This discipline — describing the incident in behavioral, observable terms — is the foundation of accurate diagnosis. We will return to it repeatedly in this chapter and the next.

Question 2: What is the pattern beneath the trigger?

Is this a one-time event, or does it recur? If it recurs, what is the theme? What do multiple incidents have in common?

The theme might be about responsiveness, about respect for time, about power and authority, about independence, about trust, about fairness, about belonging, about competence. Often one of these themes will surface quickly once you ask for it.

Sam Nguyen, an operations manager in his mid-thirties, initially framed his conflict with his direct report Tyler as a straightforward accountability issue. But when he mapped the pattern — not just the most recent missed deadline, but all the instances over four months — he noticed something: the late deliverables were clustered. They were almost always in the first week of a new project cycle, when expectations were freshest and most ambiguous. That was not the pattern of someone who was careless. That was the pattern of someone who was unclear.

Question 3: What is the underlying need or interest?

Beneath the pattern is a need. This is where the real problem lives.

Jade Flores, a nineteen-year-old in her first year at community college, had been in escalating conflict with her mother over her independence. The presenting argument was about trust — her mother did not trust her judgment, Jade felt. But when Jade pushed herself to identify the underlying need, she found something more complicated. It was not just that she wanted her mother to trust her. It was that she needed their relationship to be reorganized on different terms — from parent-child to something more mutual, more adult. That reorganization had never been negotiated. It had never even been named. Every individual conflict about curfew, or about her new friends, or about the calls that went unanswered, was a symptom of that deeper unaddressed shift.

🪞 Reflection: Think of a conflict you are currently navigating or recently experienced. Write one sentence describing the presenting problem — the specific incident or behavior. Then write one sentence about the pattern beneath it. Then try to name the underlying need. What do you notice as you move through these three levels?

The Danger of Getting This Wrong

When you misdiagnose a conflict and approach it as though the presenting problem were the real problem, several things predictably happen.

The other person feels that you are nitpicking, that you are focused on details rather than what actually matters, or that no matter what they do, you will find something else to criticize. They may capitulate on the presenting problem — agree to be on time, agree to update the documents — while the underlying dynamic continues unchanged. And then you have the same conversation in a different form three months later.

Alternatively, when you bring only the presenting problem, the other person may raise what they experience as the real issue, and you have arrived unprepared. The conversation destabilizes because you are arguing at different levels of abstraction without knowing it.

The most skillful people in difficult conversations — and the research on this is consistent — are those who do the diagnostic work beforehand. They arrive knowing what level they are working at. They arrive able to articulate not just what happened but what matters and why.

💡 Intuition Check: Notice whether your instinct right now is to think "I already know what the real problem is." That instinct is worth examining. Most of us believe we already understand our own conflicts. The diagnostic process is useful precisely for those cases where our initial understanding turns out to be incomplete. The doctor who is most confident in her diagnosis before doing the workup is the one you want to worry about most.

16.2 The Conflict Diagnosis Framework

The six steps below constitute a structured approach to diagnosing a conflict before you engage in it. The framework is designed to be worked through in writing — not because writing is magic, but because writing forces the specificity and precision that thinking alone tends to blur.

Work through this framework as though you were a clinician doing a patient workup. Your goal is not to feel better about your position. Your goal is an accurate picture of what is actually happening.

Step 1: Describe the Incident (Observable, Behavioral, Neutral)

Write a description of the specific event or events that have made this conversation necessary. The rules for this description:

• Observable. If you couldn't have filmed it, it doesn't belong here. Behaviors you can see, hear, and document.
• Behavioral. Actions and statements, not character assessments or intentions.
• Neutral. As though you were describing what a camera captured, not what a prosecutor would argue.

This step is harder than it looks. Our natural descriptions of conflict incidents are packed with evaluation, interpretation, and attribution of motive. "He disrespected the team" is not an observable description. "He interrupted the two junior analysts three times during the meeting without acknowledging their points" is.

Example (Sam Nguyen / Tyler):

First draft (evaluative): "Tyler keeps missing deadlines and doesn't seem to care about the impact on the team."

Revised (observable, behavioral, neutral): "Tyler submitted the Henderson project report on Thursday, two days after the agreed Monday deadline. This is the third deliverable in the past eight weeks that has arrived late. The Millbrook summary (late by one day, week 3) and the Q4 capacity audit (late by three days, week 5) were the previous two instances."

Notice how the revised description strips out Tyler's presumed emotional state ("doesn't seem to care") and substitutes documented facts. It is also more powerful — specific patterns are harder to argue with than vague assessments.

Step 2: Identify the Trigger

What specifically activated this conversation right now? Why today and not two weeks ago, or two weeks from now?

Triggers are important diagnostic information. They reveal what the threshold is for this person in this relationship. They sometimes reveal the real stakes of the conflict — not the pattern itself, but something about the pattern that crossed a line.

Common triggers: - An escalation in frequency or severity - An external event (a complaint from a third party, a near-miss, a deadline) - An accumulation effect (the straw that broke the camel's back) - A change in context (a new role, a new relationship stage, a new standard)

Example (Priya / Vasquez):

The trigger was not the documentation problem itself — that had been evident for months. The trigger was the department head's flag. The pattern crossed from "Priya's private concern" to "organizational visibility." That shift changed the stakes and made the conversation feel urgent in a new way.

Knowing this helps Priya assess her own motivation: is she having this conversation because it is genuinely the right moment, or because she is now worried about her own reputation? Both might be true. The diagnosis makes that legible.

Step 3: Map the Pattern

Has this happened before? In what form? What is the recurring theme?

This step requires you to look backward with some discipline. Rather than cataloguing every grievance, you are looking for the structural similarity across incidents. What is the common denominator?

Pattern mapping questions: - How many times has a version of this happened? - What do all the instances have in common? - Is the frequency increasing, decreasing, or stable? - Are there contextual factors that make it better or worse? - Is there a type of situation in which this does not happen?

Example (Jade / her mother):

Incidents: The three calls in one day. The conversation at Thanksgiving about Jade's new friends. The argument about Jade arriving home at midnight on New Year's Eve. The ongoing tension about Jade's unread texts.

Common theme: Every incident involves Jade's mother reaching for control in a moment when she feels her access to Jade has diminished. The pattern is not about any specific rule — it is about a mother struggling with her daughter's growing autonomy and not having a framework or vocabulary for that struggle.

Contextual factor: Conflicts are worse when Jade has been away — visiting friends, traveling with her roommate. They are less intense during periods when they have been in regular contact.

Pattern name: "The renegotiation we haven't had."

Naming the pattern is a useful practice. It helps you refer to it precisely, think about it as a structural issue rather than a personal attack, and communicate about it more clearly when the time comes.

Step 4: Identify Your Need

What do you actually need here? Not what you want the other person to do, but what underlying need that behavior would satisfy.

This is where Chapter 15's work on positions versus interests becomes directly applicable. Your position is what you are asking for. Your interest is why you are asking for it — the need, concern, or value that underlies the request.

If you are having trouble naming your need, the following prompts can help:

• If this situation were fully resolved, what would be different?
• What would I be able to feel or do that I can't feel or do right now?
• What does this situation threaten or undermine?
• What am I afraid of if nothing changes?

Example (Marcus Chen):

Marcus Chen, a 22-year-old pre-law student interning at a law firm, had been working late three or four nights per week — far beyond the hours the internship required. When he examined why he hadn't addressed this, he first said he needed "better boundaries around hours." But when he pushed to identify the underlying need, he found something more precise: he needed to be seen as professionally competent without sacrificing himself to prove it. The late hours were a symptom of never having established — with himself or his supervisors — what his professional presence should look like. He did not need a conversation about overtime. He needed to redefine his professional identity.

⚠️ Common Pitfall: Be alert to needs that are actually disguised positions. "I need Tyler to submit reports on time" is a position masquerading as a need. A genuine need sounds like: "I need to be able to trust that deliverables will arrive when they're expected so that I can plan and report accurately." The position might satisfy that need — or other approaches might satisfy it equally well. Staying at the level of the need keeps options open.

Step 5: Identify What You Imagine Their Need Is

This step requires intellectual honesty and some imagination. You are generating a hypothesis — not a verdict — about what the other person's underlying need might be in this situation.

This step matters because:

1. It prevents you from entering the conversation treating the other person as simply an obstacle to your desired outcome.
2. It prepares you to listen accurately when they do speak — you will have a hypothesis to test rather than arriving completely blank.
3. It sometimes surfaces important information: if you cannot generate a plausible hypothesis about their need, you may have been thinking about this conflict in an overly self-referential way.

The discipline here is to generate a charitable hypothesis — the most reasonable, human interpretation of what would explain their behavior. Not a naive or idealized version, but a version that treats the other person as a person rather than a problem.

Example (Sam about Tyler):

Sam's first hypothesis: "Tyler needs to feel like the rules don't apply to him."

Revised hypothesis: "Tyler may need to feel confident in what's expected before he can commit to a deadline. He may be working from a level of ambiguity that makes any deadline feel uncertain. He may need acknowledgment that the workload is genuinely high and support in prioritizing."

The revised hypothesis is more useful — not because it lets Tyler off the hook, but because it opens the door to a conversation about expectations and support rather than a conversation about consequences and compliance.

🪞 Reflection: When you generate a hypothesis about the other person's need, notice your resistance. Are there versions of their need that you are unwilling to consider? That resistance is worth examining. It often signals an area where the diagnosis would benefit from more work.

Step 6: Define What a "Good Outcome" Would Look Like

The final step in the diagnostic process is to articulate — before the conversation — what you are actually trying to achieve. This sounds obvious, but most people do not do it. They go into difficult conversations with a vague sense that they want things to be "better" or they want the other person to "understand." These are not outcomes. They are wishes.

A good outcome definition has three components:

Behavioral: What would the other person actually do differently? What would you do differently?

Relational: What would the relationship look and feel like after a successful resolution?

Structural: Are there systems, agreements, or shared understandings that need to change?

Example (Priya / Vasquez):

Behavioral: Vasquez submits discharge summaries within 24 hours of patient departure; progress notes are entered same-day. Priya provides a written documentation standards guide and schedules a 30-day follow-up.

Relational: Vasquez understands what is expected and why it matters. Priya understands what support Vasquez needs. They have a clearer foundation for their working relationship.

Structural: The department establishes an onboarding checklist for new attendings that explicitly covers documentation standards.

Notice that this outcome definition requires something from both parties. That is a feature, not a bug. If your outcome definition requires only behavioral change from the other person, that is a diagnostic signal: you may not yet have fully examined your own contribution to the situation.

The Conflict Diagnosis Worksheet

The following template synthesizes all six steps into a single working document. Complete it in writing, in full sentences, before any difficult conversation.

CONFLICT DIAGNOSIS WORKSHEET

Date: _______________
Conversation I am preparing for: _______________

STEP 1 — DESCRIBE THE INCIDENT (observable, behavioral, neutral)
What specifically happened? Write it as a camera would capture it.
_______________________________________________________________

STEP 2 — IDENTIFY THE TRIGGER
What made this conversation feel urgent or necessary right now?
_______________________________________________________________

STEP 3 — MAP THE PATTERN
Has this happened before? What is the recurring theme?
Pattern name: _______________
Number of instances: _______________
Contextual factors (when it is worse/better): _______________

STEP 4 — IDENTIFY YOUR NEED
What is the underlying need or interest behind your position?
(Complete this sentence: "What I actually need is...")
_______________________________________________________________

STEP 5 — IDENTIFY THEIR NEED (hypothesis)
What might be the other person's underlying need?
(Begin with: "A charitable hypothesis about their need is...")
_______________________________________________________________

STEP 6 — DEFINE THE GOOD OUTCOME
Behavioral: What would each person do differently?
Relational: What would the relationship look and feel like?
Structural: What agreements or systems need to change?
_______________________________________________________________

📊 Real-World Application: This worksheet is a direct adaptation of structured approaches used in organizational mediation, pre-litigation dispute resolution, and clinical supervision contexts. Research on negotiation preparation (Malhotra & Bazerman, 2007; Mnookin, 2010) consistently finds that structured pre-negotiation analysis improves both the quality of outcomes and the efficiency of the conversation. Preparation is not a substitute for skill in the room — but it is a prerequisite.

16.3 Interests, Rights, and Power: Three Lenses

In 1988, William Ury, Jeanne Brett, and Stephen Goldberg published Getting Disputes Resolved: Designing Systems to Cut the Costs of Conflict. Their framework emerged not from theory but from field research — including an extended study of a coal mining company where labor disputes had been extraordinarily costly and frequent. What they found, across multiple industries and dispute types, was that conflicts operate at one of three fundamental levels, and that the level at which a conflict is approached determines both the cost of resolution and the durability of the outcome.

The three levels are interests, rights, and power.

Understanding which level your conflict is actually operating at is one of the most useful pieces of diagnostic information you can have before a difficult conversation begins.

Interests: What You Actually Want and Why

An interest is an underlying need, concern, goal, or value — the why beneath the what. Interests are not positions. When two people argue about whether a window should be open or closed, their positions are fixed and appear incompatible. But when you discover that one person wants fresh air and the other person is cold, you find interests that can both be satisfied simultaneously (perhaps by opening a window in another room).

Interests can be tangible (money, time, resources) or intangible (respect, recognition, security, autonomy, clarity). In most conflicts, both types are present, and it is frequently the intangible interests — the ones that are hardest to name — that are driving the most heat.

The key diagnostic question for interests: What does each party actually need here, and why?

Interest-based approaches to conflict resolution are generally the most productive because they open up the possibility of solutions that meet both parties' needs simultaneously. They treat the conflict as a shared problem to be solved rather than a contest to be won.

Rights: Standards Both Parties Agree Should Apply

A rights-based approach invokes an external standard — a contract, a law, a policy, a shared norm, a precedent, a professional code. Rights arguments say: "Regardless of what you or I want, the agreed standard says X."

Rights-based approaches are appropriate when: - There is a genuine agreement or contract at stake - A shared norm has been violated - Interest-based resolution has been attempted and failed - The power imbalance is so severe that only an external standard creates safety

The cost of rights-based resolution is higher than interest-based. It typically requires a third party (a manager, an HR department, a court) to adjudicate. It is adversarial by structure — there is a winner and a loser, and both parties know it going in. It can damage or end the relationship. And it often leaves the underlying interests unaddressed, which is why legal victories frequently produce ongoing conflict.

The key diagnostic question for rights: Is there a standard — contractual, legal, professional, or normative — that both parties already acknowledge?

Power: Who Can Force Whom to Do What

A power-based approach relies on coercion — the ability to impose costs on the other party, or to take unilateral action that forces a change. Strikes, lockouts, ultimatums, public pressure campaigns, threats to leave a relationship — these are all power moves.

Power-based resolution is the costliest of the three. It typically produces resentment, resistance, and retaliation. It damages relationships severely and sometimes permanently. And crucially, it resolves nothing at the level of interests — the underlying needs remain unaddressed, ensuring that the conflict resurfaces in a new form.

That said, power approaches are sometimes the only option available. When someone is in genuine danger, when a rights-based approach has been exhausted, when the other party has no interest in any form of engagement — the capacity to act unilaterally may be necessary.

The key diagnostic question for power: Is coercion necessary here, or am I reaching for it because it feels faster or more satisfying?

The Three-Level Comparison

Ury, Brett, and Goldberg's central finding was that most conflicts are capable of interest-based resolution but are instead fought at the rights or power level — because the parties involved either do not know how to work at the interests level, or because they are too emotionally activated to slow down enough to try. The result is a systematically more expensive, less durable resolution than the situation required.

⚠️ Common Pitfall: The most seductive move in a difficult situation is to escalate to rights or power when interests-level conversation feels hard or uncertain. "I'm going to HR" or "If you don't change this, I'm leaving" can feel like action. But reaching for these levers before exhausting interests-level approaches frequently forecloses the most productive path and leaves both parties worse off.

Applying the Lens: What Level is Your Conflict At?

Diagnostic questions for level-identification:

1. Has an explicit agreement been violated? If yes, rights may be relevant. If no, you are probably at interests.
2. Is there a law, policy, or professional standard that applies? If yes, rights may be relevant.
3. Do both parties acknowledge the standard that would adjudicate this? If not, a rights approach may simply produce a dispute about which standard applies.
4. Has interest-based conversation been genuinely attempted and failed? If yes, rights-based approaches may be appropriate.
5. Is there a power imbalance so severe that the lower-power party cannot safely engage at the interests level? If yes, rights or structural protection may be necessary first.
6. Are you reaching for rights or power because it feels faster, not because it is actually necessary? Be honest about this one.

🔗 Connection: The distinction between levels maps onto the Five-Layer Model from Chapter 2. Conflicts rooted in Layer 1 (facts and behavior) and Layer 2 (interpretation and meaning) are typically interest-level conflicts. Conflicts involving Layer 4 (identity) or Layer 5 (values) often escalate to rights or power when people feel their fundamental sense of self is under attack. Accurate layer identification and accurate level identification are complementary diagnostic tools.

Where Sam's Conflict Actually Lives

Sam Nguyen, preparing for his conversation with Tyler about missed deadlines, initially framed the situation as a rights-level conflict. There were clear expectations; Tyler had not met them. A performance documentation process existed; perhaps it was time to begin it.

But when Sam mapped the pattern — specifically, the cluster of late deliverables at the beginning of project cycles — and when he generated a charitable hypothesis about Tyler's need (clarity, support, realistic workload assessment), he found himself looking at an interests-level conflict. The rights-level frame was available, but premature. Using it would mean escalating to formal documentation and potential disciplinary action for a problem that might be fully resolvable through a clearer conversation about expectations.

The diagnostic question Sam needed to answer before the conversation was not "How do I enforce the deadline policy?" It was: "What does Tyler actually need to be able to meet deadlines consistently, and what have I not yet provided?"

That reframing — from rights to interests, from enforcement to problem-solving — is what the diagnosis produced. And it changed everything about what kind of conversation Sam was about to have.

16.4 Mapping Stakeholders and Relationships

No conflict exists in a vacuum. Every difficult conversation is embedded in a system — a web of relationships, histories, power dynamics, and observing parties. Diagnosing a conflict without mapping that system is like diagnosing a patient without knowing their medical history, their family history, or what medications they are currently taking.

Stakeholder mapping is the practice of identifying, before the conversation, everyone who is affected by this conflict and by its resolution.

Who Is Directly Involved?

The most basic element of stakeholder mapping is identifying the primary parties — who is directly involved in the conflict.

This sounds obvious, but it is sometimes more complicated than it appears. In a conflict between a manager and an employee, is HR a party? Is the manager's supervisor? In a conflict between partners in a romantic relationship, are children stakeholders? Are parents who have been confided in?

Primary parties are those whose behavior is directly at issue and who have a direct stake in the resolution.

Who Is Indirectly Affected?

Secondary stakeholders are people who are not directly involved in the conflict but whose interests will be meaningfully affected by how it is resolved.

Example (Sam / Tyler):

Primary parties: Sam and Tyler. Secondary stakeholders: The rest of Sam's team — who are currently absorbing the downstream effects of Tyler's late deliverables. Tyler's peers — who may be aware of the pattern and watching how it is handled, drawing conclusions about fairness and accountability norms on the team.

The team's presence as secondary stakeholders affects Sam's calculus in several ways. If the conversation with Tyler goes well and the pattern changes, team morale benefits. If it does not — if Sam fails to address it, or addresses it badly — the team's confidence in Sam's leadership erodes. He is not just managing one person's behavior; he is setting a norm for the whole group.

The Relationship Context

For each primary stakeholder, the relationship context includes:

History: What is the track record of this relationship? Has there been conflict before? Has there been repair? Is there a foundation of trust to draw on, or has that foundation been damaged?

Power balance: Who has formal authority? Who has informal influence? Are there power asymmetries that affect what each party can safely say or do?

Relational stake: What does each party have to lose if this goes badly? What is the cost of relationship rupture for each of them?

Example (Jade / her mother):

History: The relationship is long, close, and laden with love — and also with a history of Jade's mother holding tight to control during Jade's adolescence. There have been arguments; there has also been genuine warmth and repair. The relationship has a high relational stake on both sides: both Jade and her mother would be devastated by genuine estrangement.

Power balance: Formally, Jade's mother has diminishing formal authority as Jade reaches adulthood. Practically, Jade is still financially dependent — she lives at home and her mother contributes to her college costs. That dependency gives her mother informal leverage that both are aware of.

Understanding this context helps Jade prepare more precisely. The power asymmetry means she needs to be thoughtful about framing — approaching the conversation as a proposal for renegotiation rather than a declaration of independence. The high relational stake means she can invoke what the relationship means to both of them as part of the motivation to work through discomfort.

The "Audience" Consideration

In many conflicts, there is an implicit audience — people who are watching, or who will be told about, the conversation and its outcome. This audience shapes the dynamic in ways that are easy to miss.

When Priya's department head flagged the documentation problem, the audience for the upcoming conversation expanded. Priya was no longer just having a conversation between herself and Vasquez — she was implicitly reporting to a supervisor who would eventually want to know how it was handled. That audience changes the stakes. Priya cannot simply let the issue slide; her response is itself a form of accountability.

Audiences can also complicate resolution. When one partner in a conflict has recruited allies — confided in friends, consulted family members, posted publicly — there is social pressure to maintain the position they have been validated in, even when a different approach might be wiser. The audience is invested in a particular narrative, and departing from that narrative has social costs.

Diagnostic question: Who is watching this conflict, and how does their presence affect what is possible?

🪞 Reflection: In a conflict you are currently navigating, draw a simple stakeholder map. Write your name in the center. Draw lines to each person directly involved. Then add secondary stakeholders — people affected by the outcome — in an outer ring. Note the relationship context for each primary party: history, power balance, relational stake. What does the map reveal that you had not considered?

The Stakeholder Map Template

STAKEHOLDER MAP

[Center] — Your name or position

Primary Parties:
- Name: _______  Role: _______  History: _______  Power Balance: _______  Relational Stake: _______
- Name: _______  Role: _______  History: _______  Power Balance: _______  Relational Stake: _______

Secondary Stakeholders:
- Name/Group: _______  How affected by resolution: _______
- Name/Group: _______  How affected by resolution: _______

Audience:
- Who is watching this conflict? _______
- How does their presence affect what is possible? _______

Structural context:
- What is the organizational or relational system this conflict is embedded in?
- Are there systemic factors (norms, policies, resource constraints) affecting the conflict?

16.5 When You're Part of the Problem

This is the section that most people would prefer to skip. It is also the section that the diagnostic process is fundamentally incomplete without.

Difficult Conversations by Douglas Stone, Bruce Patton, and Sheila Heen — a foundational text in this field — identifies what they call the "contribution system" as one of the three central conversations that make up every difficult situation. Their argument is simple and uncomfortable: in almost every conflict, both parties have contributed to creating the conditions that produced it. Contribution is not the same as fault, they emphasize carefully. Fault is backward-looking, blame-assigning, and evaluative. Contribution is forward-looking, systems-oriented, and diagnostic. "How did we together create this situation?" is a different question from "Whose fault is it?"

The reason contribution analysis is so difficult is that our brains are poorly designed for it under conditions of stress. When we feel wronged, we attend carefully to the other person's behavior and construct an accurate ledger of how their actions produced the problem. We attend much less carefully to our own behavior — especially the behaviors that are absences (things we failed to do) rather than acts (things we did). We did not give unclear instructions — we simply did not give explicit instructions. We did not create a culture of avoidance — we simply never modeled the behavior of addressing problems directly.

Omissions are harder to see than commissions. And yet omissions are among the most common forms of contribution to conflict.

Common Forms of Contribution

Creating the conditions for problematic behavior. Sam did not cause Tyler to miss deadlines. But Sam ran onboarding meetings so quickly — always with an eye on his packed calendar — that expectations were communicated in outline rather than in detail. He created conditions in which ambiguity was the norm.

Rewarding the very behavior you are now confronting. Before this conversation, did you do something that signaled the behavior was acceptable? Did you absorb the consequences quietly? Did you accommodate in ways that made the behavior sustainable? If you praised Vasquez's clinical work effusively and said nothing about his documentation for eight months, you communicated — however unintentionally — that documentation was not a priority. When you now say it is, there is a legitimate question about why the standard changed.

Not setting expectations clearly. The most common form of contribution to accountability conflicts. The expectation existed in your head but was never adequately communicated. You assumed; they assumed; the assumptions diverged.

Having modeled the behavior yourself. Do you miss deadlines? Do you send the kinds of incomplete memos you are now confronting in others? Do you handle difficult conversations by avoiding them — and then wonder why your team develops a culture of avoidance?

Escalating the dynamic. Some conflicts grow through the behavior of both parties in a feedback loop. You became more controlling as they became more evasive; they became more evasive as you became more controlling. Neither of you created the dynamic alone.

⚠️ Common Pitfall: The contribution framework is sometimes misused as a form of self-blame that paralyzes action. Identifying your contribution does not mean accepting all responsibility, letting the other party off the hook, or failing to raise legitimate concerns. It means arriving at the conversation with a complete picture — one that includes your role — rather than a partial picture that lets you feel blameless. You can have contributed to a situation and still need to address it clearly and directly.

The Ten Hard Questions

Before you walk into any difficult conversation, work through the following questions in writing. They are not comfortable questions. That is the point.

1. What did I contribute to creating this situation? Look for omissions as well as acts.

2. Have I communicated my expectations clearly, specifically, and verifiably — or have I assumed they were understood?

3. Have I rewarded or tolerated this behavior in the past, even implicitly?

4. Is there anything I am avoiding in myself by focusing on the other person's behavior?

5. Am I addressing this at the right time, or am I acting from a triggered state that would benefit from more distance?

6. What is my emotional investment in being right about this? How willing am I to discover that my initial framing was incomplete?

7. Have I made it safe for this person to tell me something I would not want to hear? Would they be likely to have raised concerns with me before they became a problem?

8. What am I afraid of in this conversation? What outcome would I dread, and how is that fear shaping my preparation?

9. Am I approaching this conversation to genuinely solve a problem, or to establish a record, to punish, to relieve my own frustration, or to win?

10. If the roles were reversed — if this person were preparing to confront me about something — would I recognize myself in the diagnosis?

🪞 Reflection: Take one of the ten questions above that produces the most resistance when you read it. Write about that resistance. What is it protecting you from knowing?

The "Clean Hands" Question

A final diagnostic question that distills the contribution analysis into a single inquiry: Am I approaching this conversation with clean hands?

This does not mean: Am I perfect? No one is perfect. It does not mean: Is everything this person does acceptable? It is not. What it means is: Am I approaching this honestly? Am I willing to see the full picture — including my role in it? Or am I entering this conversation as though I were purely the wronged party, looking only for acknowledgment and change?

Priya Okafor, sitting at her desk on that Tuesday evening, eventually wrote the answer to this question on her legal pad: No, not entirely. I never gave him the standards document. I never had the 30-day check-in. I assumed. That is mine.

That acknowledgment — private, honest, and precise — changed the conversation she was going to have. Not because Vasquez's documentation was acceptable. It was not. Not because the conversation no longer needed to happen. It did. But because Priya was now going to arrive at that conversation with a complete diagnosis rather than a partial one. She was going to be able to say: here is the problem, here is what it requires, and here is what I recognize as my part in how we got here.

That combination — accountability for the issue and accountability for her contribution — is what the research calls a "clean" approach to confrontation. And it is what diagnosis makes possible.

16.6 Chapter Summary

The hardest preparation for a difficult conversation is not deciding what to say. It is deciding what is actually true — about the situation, about the other person, and about yourself.

This chapter introduced a systematic approach to that preparation: the work of diagnosis before the conversation begins.

We began with the foundational distinction between the presenting problem — the trigger, the incident, the visible symptom — and the real problem — the pattern, the underlying need, the structural issue that the presenting problem is an expression of. The presenting problem is where most conversations begin and too many end. The real problem is what determines whether resolution is durable.

We worked through the six-step Conflict Diagnosis Framework, which transforms an anxious, intuition-driven preparation process into a structured, written analysis: describe the incident, identify the trigger, map the pattern, identify your need, generate a hypothesis about their need, and define what a good outcome would look like. The framework is not a script — it is a workup. You are the clinician. The conflict is the patient.

We then applied the interests/rights/power framework from Ury, Brett, and Goldberg — one of the most robust and empirically grounded tools in the dispute resolution literature. Most conflicts that feel like rights or power conflicts are actually operating at the level of interests and can be resolved there — more cheaply, more durably, and with far less damage to the relationship. The diagnostic task is to identify what level your conflict is actually at, rather than treating it at the level that feels most intuitively satisfying or emotionally urgent.

We mapped stakeholders and relationships — the system in which every conflict is embedded. Who is directly involved, who is indirectly affected, what is the relationship history and power balance, and who is watching? The conflict you are about to enter is not between two isolated individuals. It is between two people embedded in a web of relationships, histories, and observing parties. Understanding that web is part of accurate diagnosis.

Finally, we confronted the most difficult diagnostic task: identifying your own contribution to the conflict you are preparing to address. Drawing on Stone, Patton, and Heen's contribution framework, we examined the most common forms of contribution — creating conditions for problematic behavior, not setting clear expectations, rewarding the behavior you are now confronting, and modeling what you now object to. We worked through ten hard questions to ask before any confrontation. And we closed with the "clean hands" question — not a requirement of perfection, but an invitation to honesty.

Looking Forward

Chapter 17 uses the results of this diagnostic work to answer a different set of questions: When? Where? How? Once you know what is actually at stake in a conversation, you can make intelligent decisions about the time, place, and medium that will give the conversation its best chance. Diagnosis tells you what the problem is. Chapter 17 helps you decide how and when to engage it.

Chapter 18 (Opening the Conversation) takes diagnosis one step further: the opening of a difficult conversation is built directly from what diagnosis has revealed as the core issue. The six-step worksheet you complete before the conversation becomes the architecture of how you begin it.

Key Terms

Presenting problem: The visible, surface-level trigger for a conflict — the incident or behavior that makes the conversation feel necessary.

Underlying problem: The pattern, unmet need, or structural issue that the presenting problem is a symptom of.

Conflict diagnosis: A structured process of analyzing a conflict before engaging in it, to identify what is actually at stake and at what level.

Interests: Underlying needs, goals, concerns, and values — the "why" beneath positions and behaviors.

Rights: External standards — contracts, laws, policies, shared norms — that both parties acknowledge should apply to the situation.

Power: The capacity to impose costs or take unilateral action to force a change in the other party's behavior.

Contribution framework: The framework (Stone, Patton, and Heen) for understanding how both parties jointly create the conditions for conflict, without assigning fault.

Stakeholder mapping: The practice of identifying all parties directly and indirectly affected by a conflict and analyzing the relationship context of each.

References

Fisher, R., Ury, W., & Patton, B. (2011). Getting to yes: Negotiating agreement without giving in (3rd ed.). Penguin Books.

Malhotra, D., & Bazerman, M. H. (2007). Negotiation genius: How to overcome obstacles and achieve brilliant results at the bargaining table and beyond. Bantam Books.

Mnookin, R. H. (2010). Bargaining with the devil: When to negotiate, when to fight. Simon & Schuster.

Stone, D., Patton, B., & Heen, S. (2010). Difficult conversations: How to discuss what matters most (2nd ed.). Penguin Books.

Ury, W. L., Brett, J. M., & Goldberg, S. B. (1988). Getting disputes resolved: Designing systems to cut the costs of conflict. Jossey-Bass.