Most managers who've done DiSC training can name the four styles. Far fewer can tell you what to actually do differently in a 1:1 with a high-C versus a high-D. The assessment gives you the map; this article gives you the navigation.
Before we get into style-by-style frameworks, a grounding principle: coaching to DiSC is not about changing someone's style. It's about understanding how they process information, what motivates their behavior, and where friction is most likely to arise — then adjusting your approach to meet them where they actually are instead of where you wish they were.
This is harder than it sounds if your style differs from theirs. A high-D manager coaching a high-S employee will default to directness and urgency that feel threatening rather than motivating. A high-C manager coaching a high-i employee will lean into data and process in ways that feel deflating rather than directional. Understanding the style gap between you and your direct report is as important as understanding their style alone.
If you haven't taken the DiSC leadership assessment yet, start there. You can't coach from a map you haven't read yourself.
The 360 scenario running through this article: You just received 360 feedback indicating that your team members feel unheard — like their input doesn't change decisions, and like they're not sure where things are headed. Here's how to coach based on each team member's DiSC style — same feedback, four completely different approaches.
Coaching Each DiSC Style
Each section below covers what motivates that style, what frustrates them, three coaching tactics that work, and the one mistake most managers make. Read the section for your direct report's primary style first, then read your own — the gap between them is where most coaching friction lives.
Coaching the High-D: Dominant Style
- Autonomy and authority over outcomes
- Big challenges with real stakes
- Recognition for results, not effort
- Fast-moving environments
- Visible impact and advancement
- Slow decision-making or excessive process
- Micromanagement or loss of control
- Vague direction or shifting goalposts
- Too many meetings, not enough action
- Emotional conversations without clear points
- Lead with outcomes, not process. High-D employees don't need step-by-step guidance — they need a clear target and the latitude to reach it their way. Frame coaching conversations around results: "The outcome we need is X. How do you want to get there?" Let them own the path.
- Be direct and specific with feedback. Soft, cushioned feedback lands poorly with high-D individuals — it reads as evasive and wastes time. State the issue clearly: "The decision you made last week on the vendor cut the ops team out of a decision that affects them directly. That's created a trust problem." No preamble, no excessive context. They respect straight talk.
- Challenge them with stretch goals. A high-D who isn't challenged is a high-D who's disengaged or causing friction looking for stimulation. Give them problems that are genuinely hard and consequential. Frame development as a pathway to bigger impact, not as fixing a weakness.
Over-explaining the rationale. High-D employees don't need a lengthy case built for every decision — they interpret excessive justification as a lack of conviction on your part. State the direction, name the constraint, and move on. Lengthy preambles signal uncertainty, and uncertain leaders lose high-D respect fast.
Your team says they feel unheard — and this person is high-D.
The most likely dynamic: they're making decisions fast and communicating outcomes after the fact. Their team is experiencing this as being steamrolled, not included. They see this as efficient; their team sees it as dismissive.
Don't frame this as "you need to slow down." Frame it as a results problem: "When your team doesn't feel included in decisions that affect them, you lose two things — better information upfront, and faster execution afterward, because people who had no input feel less ownership. The cost of five more minutes of input is weeks of adoption friction." Make the ROI case, not the feelings case.
Coaching the High-i: Influential Style
- Social connection and team energy
- Public recognition and visibility
- Creative latitude and variety
- Collaboration over independent work
- Being seen as the go-to person
- Isolation or too much solo work
- Repetitive, detail-heavy tasks
- Public criticism or being called out
- Rigid process with no room to improvise
- Conversations that feel purely transactional
- Start with the relationship, then the issue. High-i employees are relationally attuned — they notice whether a conversation feels connected or clinical. A 1:1 that opens cold and goes straight to feedback will generate defensiveness. Spend two minutes on genuine connection before transitioning to the development conversation. The warmth isn't a formality; it's the on-ramp.
- Make feedback specific and behavioral, not global. High-i employees are sensitive to anything that feels like a judgment on who they are rather than what they did. Avoid "you're not detail-oriented enough" — say "the report that went to the client Tuesday had three data errors that the client caught. Here's what I'd like to see next time." Behavior, not character.
- Leverage their strength as a vehicle for growth. High-i employees respond well to development framed as expanding their influence: "You're already great at rallying people around a vision. The next level is delivering outcomes that match the enthusiasm you generate." Connect the growth area to something they already care about.
Assuming enthusiasm means alignment. A high-i employee who leaves a coaching conversation energized is not necessarily an employee who has internalized the feedback. They process optimistically and can hear "this is going well" even in a conversation that included pointed development feedback. Close every coaching session by asking them to reflect back the one or two things they're going to do differently — not as a test, as a calibration.
Your team says they feel unheard — and this person is high-i.
The most likely dynamic: their 1:1s are warm and connected, but the team feels like conversations don't translate into action. Ideas are heard, energy is high, but follow-through is thin. People feel valued in the moment but unheard in outcomes.
Don't frame this as "you need to be more organized." Frame it around their relational value: "You're exceptional at making people feel seen in conversation. The gap right now is that your team can't always tell what happens to the ideas they share — so the follow-up isn't matching the investment of the conversation. A simple close — 'here's what I'm taking forward from this' — turns a great conversation into a trackable commitment." Connect the change to who they already are.
Coaching the High-S: Steady Style
- Stable, predictable work environment
- Deep relationships and genuine trust
- Clear expectations set in advance
- Being genuinely needed by the team
- Sincere, private recognition
- Sudden change without context or reason
- Conflict and interpersonal tension
- Pushy, aggressive communication styles
- Being put on the spot publicly
- Ambiguity about priorities or direction
- Give advance notice before difficult conversations. Ambushing a high-S employee with hard feedback in a surprise 1:1 triggers defensive shutdown — not because they're weak, but because they need processing time to show up constructively. If you need to have a development conversation, flag it: "I want to talk about something in our 1:1 Thursday — it's a development conversation, not a crisis." They'll arrive ready instead of guarded.
- Be patient with their pace of change. High-S employees don't resist change because they're incapable — they resist abrupt change because it disrupts the stability they use as a foundation for doing their best work. Walk them through the why, the timeline, and what stays the same. The context isn't a courtesy; it's what makes the change executable for them.
- Create explicit permission to disagree. High-S employees are conflict-averse enough that they'll agree in a conversation and quietly disengage rather than push back on a direction they have concerns about. Build explicit permission into your relationship: "I need you to tell me when something doesn't feel right. Your instincts about the team are usually better than mine — I can't act on what I don't hear." Make disagreement safe, repeatedly, until it becomes a pattern.
Interpreting agreement as buy-in. High-S employees are skilled at holding a pleasant, cooperative surface even when they have real reservations. A manager who mistakes that surface for alignment will be blindsided when the team member is disengaged, passively resistant, or quietly job-hunting. Check in below the surface: "What feels off about this that you haven't said yet?"
Your team says they feel unheard — and this person is high-S.
The most likely dynamic: this manager is absorbing a lot — they're deeply attuned to what their team is feeling — but they're not translating that into visible action or explicit acknowledgment upward. Team members feel heard in the room but invisible in the organization. There may also be a pattern of validating concerns without advocating for the resources or changes to address them.
Frame this gently but directly: "Hearing your team is something you do better than almost anyone. The next level is making sure they can see that their input travels somewhere. When you advocate for what they've told you — in staff meetings, in planning conversations — it closes the loop. They don't just feel heard; they see evidence that it mattered." Name it as a skill extension, not a correction.
Coaching the High-C: Conscientious Style
- High-quality work and accurate data
- Logical, well-reasoned decisions
- Clearly defined processes and standards
- Independent work time and space to think
- Being recognized as a subject-matter expert
- Decisions made without sufficient data
- Sloppy work or lowered standards
- Emotional arguments without logical grounding
- Unclear expectations or changing criteria
- Being rushed before they're ready
- Provide data and evidence to support feedback. Abstract feedback doesn't land with high-C employees — they want specifics. Not "your communication style creates friction," but "in the last three sprint reviews, the design team mentioned they didn't have enough lead time on the requirements. Here's the pattern." Evidence-backed feedback is credible; opinion-based feedback is dismissible. Come prepared.
- Give them pre-work before decision conversations. High-C employees process deeply before they speak — put them in an off-the-cuff decision meeting and you'll get either silence or excessive hedging. Send the question and relevant data before the conversation: "I want to decide on the vendor by Thursday — I'll send you the comparison doc Monday so you can think through it." You'll get their best thinking instead of their least-prepared thinking.
- Name the decision point explicitly. High-C employees can keep refining indefinitely if the standard for "done" isn't made explicit. Help them calibrate when "good enough" is genuinely good enough: "This analysis needs to be solid enough to present to the board, not exhaustive. What would it take for you to be confident enough to present it Thursday?" Set a decision gate, not an open-ended standard.
Dismissing their concerns as overthinking. When a high-C employee raises a risk or asks for more time to validate an assumption, the instinct in many organizations is to move past them. Sometimes they are genuinely overthinking. But more often, they've caught something real — and dismissing them without engaging the substance trains them to stop raising flags. Engage the concern: "Walk me through the specific risk you're seeing. If it's real, we adjust. If it's not, you'll have worked through it and can move confidently."
Your team says they feel unheard — and this person is high-C.
The most likely dynamic: this manager communicates in a mode of technical precision that leaves team members feeling like their perspective has been evaluated and filed rather than genuinely received. They may ask good questions, but the follow-up usually involves analysis of the issue rather than empathy about the experience of it. There may also be a pattern of extensive process without visible acknowledgment that team input shaped it.
This is a genuinely counterintuitive development area for high-C leaders: "You hear a lot. The gap is that your team can't always tell you heard them, because your response is analytical rather than relational. When someone raises a concern, try reflecting before responding: 'That sounds frustrating — tell me more.' Not as a technique, as a genuine discipline. You don't have to choose between being rigorous and being heard as a human. You can be both."
The Hardest Part: Coaching Across Style Gaps
The style sections above assume the coach knows their own style and is managing the gap consciously. Most coaching failures don't happen because the manager doesn't know the employee's style — they happen because the manager is defaulting to their own preferred mode without realizing it.
A high-D manager coaching a high-S employee will instinctively move fast, be blunt, and push for commitment in the first conversation. The high-S employee will agree, disengage, and start job-searching. The D manager thinks the conversation went fine; the S employee thinks the relationship just got unsafe.
A high-i manager coaching a high-C employee will bring warmth, energy, and a lot of words. The high-C employee will want data, precision, and logical structure. They'll leave the conversation feeling like nothing concrete happened — because nothing concrete happened.
The rule for managing style gaps is simple but uncomfortable: adapt first. The manager's job is to create conditions where the employee can do their best work — which means meeting the employee where they are, not where you are. That's not a personality change. It's a professional competency.
If you want to see how Elevoq's AI leadership coaching handles this — your AI coach already knows your DiSC profile and adjusts accordingly. When you bring it a coaching challenge about a direct report, it will ask about their style and adapt its guidance to the actual gap, not a generic framework.
Common Mistakes Across All Styles
Beyond the style-specific mistakes covered above, three patterns show up consistently regardless of style:
- Coaching the style you wish they had. If you're a high-D manager with a high-S employee who is too slow for your pace, your job is not to turn them into a D. Their steadiness is probably genuinely valuable on your team. Coach the strengths into higher-leverage situations; work on the edges that create friction.
- Treating DiSC as a fixed destiny. DiSC describes behavioral tendencies, not ceilings. High-S leaders can learn to deliver direct feedback; high-C leaders can learn to make faster decisions in low-stakes situations. The profile tells you where to start, not where they'll end up. Development is the point.
- Using DiSC as an excuse. "She's just a high-C, she'll never move fast enough" is a manager abdicating their coaching responsibility. DiSC explains behavior — it doesn't excuse the manager from developing it. If someone's style is creating real problems, that's a coaching conversation, not a tolerance exercise.
The pattern that separates effective DiSC coaches from ineffective ones: Effective coaches use the framework to ask better questions — "given that you're a high-S, what made that conversation feel so unsafe?" Ineffective ones use it to predict and box: "you're a high-D, so of course you steamrolled the team." One opens development; the other closes it.
Where to Go From Here
If you don't yet have your own DiSC profile, that's the first step. You cannot coach effectively from a framework you haven't applied to yourself — your blind spots are exactly where your coaching will fall short. Take the free DiSC leadership assessment on Elevoq. It's 15 minutes and gives you a full behavioral profile including your coaching tendencies, your likely style gaps with different team members, and your specific development areas as a leader.
If you have your profile and are ready to work on specific coaching challenges — a team member who isn't improving, a recurring conflict with a direct report, a development plan you're not sure how to structure — that's exactly what the AI coaching sessions on Elevoq are built for. Your coach knows your style and will help you navigate the gap between your approach and what the team member in front of you actually needs.
See the full breakdown of all four DiSC leadership styles if you want to go deeper on any style beyond the coaching frameworks covered here. Understanding the style is foundation; knowing how to coach it is the practice.
Elevoq's coaching programs range from self-serve individual plans to full-team programs. Compare DiSC coaching options at every tier — the individual plan starts free, and team programs include cohort debriefs with your DiSC results mapped across the team.