Skip to content

Chapter 2 of 7

Listening, Questioning, and Feedback

The first analytic move in a difficult conversation is to distinguish positions from interests. A position is what someone says they want; an interest is the deeper need or concern driving that demand. Because positions are visible and interests are often hidden, open questions are essential: they surface context, assumptions, and needs that short defensive statements conceal. Once enough is on the table, identifying a shared objective — a goal both parties care about, such as protecting trust, meeting a deadline, or serving a customer well — turns the conversation into a "we" activity rather than a contest. Reframing supports this shift by restating the problem in more neutral or constructive language so it becomes easier to solve together.

Structured feedback models help translate listening into clear messages. SBI (Situation, Behavior, Impact) describes what happened without exaggeration or personal attack. DESC (Describe, Express, Specify, State consequences) adds the assertive request and its consequences, making it action-oriented. BIQ (Behavior, Impact, Question) pairs an observation with an open question that invites dialogue. Each of these avoids the manipulative framing of the "praise sandwich," which critics argue teaches people to ignore the praise and signals that critique is something to be endured. The same spirit runs through "radical candor" — care personally plus challenge directly — and through the "ruinous empathy" warning, which names the cost of withholding necessary feedback to spare feelings in the moment.

Effective messages also rest on recognizable phrasing. "I noticed, I felt, I need" grounds feedback in observable behavior, names the personal impact, and ends with a clear ask, reducing both defensiveness and ambiguity. An I-statement such as "I felt concerned when the client update went out late because it affected trust. Can we agree on a clearer handoff next time?" expresses a concrete experience and a specific request without accusing. Repair attempts — apologies, careful humor, respectfully restating a point — interrupt escalation before it builds. These tools travel into writing too, but with care: because tone is harder to read in writing, short messages can feel sharper than intended, and sensitive issues should usually move to a live conversation. Two distinctions are worth holding throughout. First, a concern is anchored in a future outcome ("I'm worried we'll miss the deadline") while a complaint is anchored in blame about the past; concerns tend to move things forward, complaints often do not. Second, validation ("I see how that makes sense from where you stand") is not the same as agreement ("I share that view"), and unconditionally regarding another's worth — separate from their behavior or yours — defuses shame-driven escalation.

All chapters
  1. 1Foundations of Conflict Resolution
  2. 2Listening, Questioning, and Feedback
  3. 3The Five Conflict Styles
  4. 4Negotiation
  5. 5Cognitive Biases and Emotional Dynamics
  6. 6Team and Group Dynamics
  7. 7Repair, Resolution, and Lasting Change

Drill it

Reading is not remembering. These come from the Conflict Resolution deck:

Q

What is conflict resolution?

Conflict resolution is the process of addressing disagreement in a way that reduces friction, surfaces the real issue, and helps people move toward a workable o...

Q

What is the difference between conflict management and conflict resolution?

Conflict management reduces harm and keeps work moving, while conflict resolution aims to address the underlying issue so the conflict does not keep resurfacing...

Q

What is the first step in resolving a conflict?

Start by clarifying the issue: what happened, who is affected, and what outcome each person wants.

Q

Why should you separate people from the problem?

Separating people from the problem lowers defensiveness and helps everyone focus on the issue instead of attacking identity or intent.