Difficult conversations are not the problem; avoiding them is.
In business and in life, most breakdowns in trust, performance, and culture can be traced back to conversations that should have happened earlier and often did not. People delay these conversations because they fear or dislike conflict, potential emotional reactions, legal exposure, or damage to relationships.
The irony is simple. Avoidance creates exactly what people are trying to prevent.
When handled correctly, a difficult conversation becomes a leadership moment. It creates clarity, restores trust, and sets new behavioural standards at work and/or at home. This is where structure matters.
Creating Psychological Safety First
Before you reach for any model or script, there must be safety.
People don’t hear feedback when they feel or sense that they are being attacked. When the other person feels under fire, they tend to defend, justify, or disengage completely. The conversation turns into a fight, a shutdown, or a legal risk.
A safe space does not mean being soft. It means being clear, respectful, and predictable. When people know what is coming and why, they stay present.
A well-structured framework allows you to:
- Stay factual
- Regulate emotion
- Reduce defensiveness
- Focus on behaviour, not personality
One of the most practical frameworks developed for this purpose is the DESC Model.
The DESC Model (Bower & Bower, 1991)
Sharon and Gordon Bower developed the DESC Model in Asserting Yourself as a structured, assertive communication script. It’s designed to address problematic behaviour without escalating conflict.
DESC stands for Describe, Express, Specify, Consequences. The model is simple, repeatable, and effective when used with intent. Let’s walk through each step.
D – Describe
Begin with observable facts only. No opinions. No labels. No assumptions. This answers one question: What actually happened?
Example: “In this morning’s meeting, I noticed I was interrupted three times while presenting the budget overview.”
By sticking with what you saw or heard, you anchor the conversation in something concrete instead of attacking the person.
E – Express
Next, you explain the impact using “I” language. This is not an emotional dump. You’re giving the other person a clear statement of effect. This answers the question: What impact did this have on me or the outcome?
Example: “I felt frustrated, and it disrupted my flow, which affected how clearly the information landed.”
That simple shift from blame to impact helps the other person hear you without feeling cornered.
S – Specify
Then you spell out what you want to see happen going forward. Vague requests lead to vague results, so this step answers, What needs to change?
Example: “Moving forward, I’d like to finish my points before input is added.”
Now the other person knows exactly what better behaviour looks like.
C – Consequences
Finally, you describe the positive outcome of change, and when appropriate, the real consequence of no change. This is not a threat. It adds weight and clarity to the conversation, and answers: Why does this matter?
Example: “That will help us stay focused and present a united message. If interruptions continue, I’ll need to reset how we run these meetings.”
Used this way, DESC gives you a script that keeps the conversation behavioural, respectful, and outcome-focused. The next challenge is how you say it (your tone, pace, and level of detail), and that’s where many leaders still get into trouble, even with the right words in front of them.
Where DESC Alone Falls Short
DESC tells you what to say. It does not tell you how to say it.
This is where many well-intended conversations still fail. My own journey into DISC started with that kind of miscommunication, which I share in From Miscommunication to Mastery: My Unexpected Journey into DISC. I now see the same pattern when leaders follow a good script word-for-word and still lose the room because the delivery doesn’t fit the person sitting across from them.
People do not respond to words alone. They respond to tone, pace, level of detail, and emotional energy. Those elements are driven by behavioural style. This is why at DHC Training Solutions, we do not teach DESC in isolation. To make the script work in real life, you need DISC.
Why DISC Strengthens the DESC Model
The DISC Model of Human Behaviour explains how people prefer to communicate and process information.
In broad strokes:
- Direct personas want clarity and efficiency
- Inspiring personas want connection and engagement
- Supportive personas want safety and harmony
- Cautious personas want logic and accuracy
When you combine DESC with DISC, you gain two advantages:
- You keep a clear structure for the conversation.
- You adapt your delivery to the person in front of you.
The message stays the same. The delivery flexes with their behavioural style, so the conversation has a better chance of success.
If you want a broader view of how DISC shapes emotional responses under pressure, I discuss it in more detail in Cracking the Code: How DISC Makes Emotional Intelligence Actually Work.
From here, you can start tailoring your DESC delivery to each style.
Applying DISC to DESC Delivery
Here’s how I coach leaders to adjust their DESC delivery for each DISC persona.
Direct (D) Style
With a high D, your goal is to respect time and focus.
You’ll want to:
- Keep it brief
- Focus on results and impact
- Use minimal emotional language
They respect clarity and speed. Give them the headline, the effect on outcomes, and the clear expectation going forward.
Inspiring (I) Style
With a high I, your task is to keep things clear without losing connection.
You should:
- Stay on point
- Use concrete, relatable examples
- Avoid long build-ups or side stories
They value energy and rapport. Hold their attention with a clear line of conversation, and give them room to respond without letting the talk wander from the issue.
Supportive (S) Style
With a high S, you’re working with someone who values harmony and trust.
Aim to:
- Slow the pace
- Reassure your intent
- Emphasize the relationship
They are often loyal and steady. Make it clear you’re raising the issue because you care about the relationship and the work, and give them time to process and ask questions.
Cautious (C) Style
With a high C, accuracy and structure matter.
You’ll want to:
- Be precise in your wording
- Stick to facts, data, and specific examples
- Avoid exaggeration or vague language
They appreciate logical, consistent feedback. Show your evidence, explain the standard, and outline what “good” looks like in practical terms.
DESC gives you the roadmap, and DISC tells you how fast to drive and how sharp to turn.
DESC Script Examples You Can Use Right Away
Here are ten common workplace situations with sample DESC scripts you can adapt to your voice and context.
1. Repeated Interruptions in Meetings
Scenario: A colleague interrupts you repeatedly during meetings.
DESC Script:
- Describe: “During the last two meetings, I was interrupted several times while presenting.”
- Express: “I feel frustrated because it disrupts the message and impacts how the team receives the information.”
- Specify: “I’d like to finish my points before the discussion starts.”
- Consequences: “That will help and assist meetings run more smoothly and improve clarity for everyone.”
2. Profanity and Threatening Language
Scenario: Someone swears and threatens you in front of others.
DESC Script:
- Describe: “This afternoon, you used profanity while speaking to me in front of a client.”
- Express: “I felt uncomfortable, and it undermined professionalism in that moment.”
- Specify: “I’m asking that we keep language professional at all times.”
- Consequences: “This maintains credibility with clients and protects our working relationship.”
3. Discriminatory Comments
Scenario: A coworker makes a derogatory comment about a minority group.
DESC Script:
- Describe: “Earlier today, you made a comment suggesting a specific group cannot be trusted.”
- Express: “I find that inappropriate, and it conflicts with our workplace values.”
- Specify: “That language needs to stop immediately.”
- Consequences: “Respectful behaviour creates trust, and continued behaviour would require formal escalation.”
4. Chronic Missed Deadlines
Scenario: A team member repeatedly misses deadlines.
DESC Script
- Describe: “The last three reports were submitted after the agreed deadlines.”
- Express: “This puts pressure on the rest of the team and delays delivery.”
- Specify: “I need deadlines met, or advance notice if there is an issue.”
- Consequences: “This allows us to plan effectively and avoid rework.”
5. Constant Side Conversations in Meetings
Scenario: Two people regularly whisper and distract others.
DESC Script
- Describe: “In the last two meetings, there were side conversations while others were speaking.”
- Express: “It disrupts focus and slows decisions.”
- Specify: “Please pause side conversations and raise points with the group when relevant.”
- Consequences: “We’ll make decisions faster and reduce misunderstandings.”
6. Public Undermining
Scenario: A peer challenges you in front of the team rather than privately.
DESC Script
- Describe: “In the team huddle, you challenged my decision in front of everyone.”
- Express: “It weakened alignment and created confusion.”
- Specify: “Bring concerns to me first privately, and we’ll align before discussing publicly.”
- Consequences: “That protects trust and keeps the team confident in direction.”
7. Micromanaging
Scenario: Your manager rewrites your work and checks in excessively.
DESC Script
- Describe: “You’ve been asking for updates multiple times a day and revising my drafts directly.”
- Express: “I feel restricted, and it slows my output.”
- Specify: “Can we agree on one daily update and clear ownership of drafts?”
- Consequences: “This will improve speed and accountability, and you’ll still have visibility.”
8. Credit Stealing
Scenario: A colleague takes credit for your work in meetings.
DESC Script
- Describe: “In yesterday’s meeting, the outcome of my analysis was presented as yours.”
- Express: “I felt discouraged, and it impacts trust.”
- Specify: “In future, please reference my contribution, and I’ll do the same for you.”
- Consequences: “That keeps collaboration strong and recognition fair.”
9. Gossip and Rumours
Scenario: A team member spreads rumours about others.
DESC Script
- Describe: “I’ve heard you repeating personal information about colleagues.”
- Express: “It damages trust and team culture.”
- Specify: “Stop sharing personal stories about others and bring concerns directly to the person or manager.”
- Consequences: “We’ll build a more respectful and secure workplace.”
Why This Matters for Conflict Resolution Training
Teaching conflict resolution without behavioural awareness is incomplete.
DESC builds structure to the conversation. DISC builds adaptability to the delivery.
Together, they:
- Reduce HR escalation
- Increase accountability
- Protect relationships
- Strengthen leadership confidence
This is why our conflict resolution training at DHC Training Solutions integrates both models. Leaders walk away knowing what to say and how to say it, to the right person, at the right time.
Difficult conversations are part of leadership. Poorly handled conversations don’t have to be. When structure meets behavioural intelligence, conversations stop being feared and start producing results.
DISC Makes Everything Make Sense. Keep Calm, and DISC On!
