Phase 1 · Module 2
Use these scenarios for team coaching sessions, 1:1 debriefs, or certification preparation
Scenario 1
Situation
Marcus is a high-performing D-style (Dominance) employee. In every meeting he cuts people off, pushes his ideas with force, and visibly sighs when others take time to explain their thinking. Two C-style team members have stopped contributing ideas because of him.
Your Task
Address the communication impact of a dominant DISC style without demotivating a high performer.
Step-by-Step Guidance
Meet with Marcus privately — never correct DISC-related behavior publicly.
Lead with results: "Marcus, your ideas are strong and I want them to land better with the team."
Name the behavior specifically: "In Tuesday's meeting, you spoke over Keisha twice and the team pulled back after that."
Connect it to his goal: "When people disengage, you lose access to information that could sharpen your ideas."
Give him a concrete strategy: "Before you push back on an idea, try one sentence of acknowledgment first — that's an interesting angle — here is what I would add to it."
Do NOT ask him to change who he is — ask him to flex his style for greater impact.
Check in after the next meeting: "How did that feel? Did you notice a difference in the room?"
Facilitator Debrief
D-styles respond to logic and results, not emotional appeals. Frame the behavior change as a performance tool, not a personality correction. They will adopt it if they see the ROI.
Key Principle
DISC flex: You cannot change someone's style — but you can coach them to flex it strategically for better outcomes.
Scenario 2
Situation
Sofia is a steady, reliable S-style employee who has been with the company seven years. Her performance has slipped — she is missing small deadlines and her work quality has dropped slightly. She avoids conflict and becomes visibly distressed when you hint at concerns.
Your Task
Deliver performance feedback to an S-style employee in a way that motivates rather than shuts them down.
Step-by-Step Guidance
Choose a private, unhurried setting — S-styles need safety and time, not speed.
Open with genuine relationship-building: "Sofia, I want to talk because I care about how you're doing — not just the work."
Start with a true positive observation before introducing the concern.
Frame the feedback as a shared problem: "I've noticed some missed deadlines lately and I want to understand what's happening from your side."
Use SBI gently: "Last week the client report was due Thursday and arrived Friday [situation/behavior]. The client flagged it [impact]."
Ask for her perspective before offering solutions: "What has been getting in the way for you?"
Give her time to process — S-styles do not respond well to pressure or urgency.
End with a clear, kind agreement: "Let's check in every Monday morning — five minutes — just to make sure you have what you need."
Facilitator Debrief
S-styles value stability, relationships, and sincerity. They need to feel supported — not evaluated. Rushing the conversation or leading with the problem will trigger defensiveness or withdrawal.
Key Principle
Adapt to the receiver: The same feedback lands very differently depending on the person's DISC style. Matching your delivery to their style is not manipulation — it is effective communication.
Scenario 3
Situation
A new software system is being rolled out next month. Your C-style team member — Daniel — has sent three detailed emails listing risks and flaws in the implementation plan. He has not said he refuses to use it, but his resistance is slowing the team's buy-in.
Your Task
Bring a C-style skeptic on board with an organizational change.
Step-by-Step Guidance
Do not dismiss or minimize his concerns — C-styles earn trust through being heard on details.
Set up a meeting specifically to review his list: "Daniel, you raised some important points. I want to go through them properly."
Validate every concern you can: "You're right that the data migration timeline is tight — I'm going to raise that with IT."
For concerns you cannot change: "That one is fixed — here is the rationale behind it."
Give him a role in the rollout that uses his analytical strength: "Would you be willing to create the QA checklist for the first two weeks?"
Provide as much data as possible: adoption rates from the pilot team, vendor documentation, FAQ sheet.
C-styles do not respond to enthusiasm — they respond to evidence. Use facts, not energy.
Facilitator Debrief
C-styles are not being difficult — they are being thorough. Their resistance is often the most valuable feedback you will get before a rollout. Channeling it constructively turns a critic into your best quality-control partner.
Key Principle
Use style as a resource: A C-style's caution is not a problem to overcome — it is a quality-control asset to leverage.