Most people give feedback the way they'd want to receive it. If you're direct and results-driven, you deliver feedback crisply and move on. If you're analytical and precise, you explain your reasoning thoroughly before stating the concern. If you're relationship-oriented, you start with what's going well.
The problem is the person on the other side isn't you. Different filters, different priorities, a different idea of what good feedback sounds like. What reads as respectful and clear to one person reads as cold to another. What feels thorough and fair to one person feels like an interrogation to someone else.
DiSC doesn't tell you what feedback to give. But it tells you a lot about how to deliver it so it actually lands.
How each style hears feedback
D Dominance
What they want: The bottom line, fast. D-types respect directness. They'd rather hear "this didn't work and here's why" than be walked slowly to the same conclusion.
What misses: Long preambles, excessive softening, or feedback buried in praise. If you spend five minutes building rapport before getting to the point, they'll have already stopped listening.
What works: Lead with the issue, then the impact, then the ask. Keep it short. Don't apologize for having the conversation. They'll respect you less for it.
i Influence
What they want: To feel like you're still on their side. i-types are tuned to tone. They feel the feedback before they process the content. If the relationship doesn't feel intact, the message doesn't get through.
What misses: Pure task feedback with no relational context. Delivering criticism in a flat, businesslike tone can register as personal rejection even when it isn't meant that way.
What works: Acknowledge what's working first, and mean it, don't run it as a formula. Then raise the concern as something you're solving together ("here's what I think could shift") rather than a verdict ("here's what you got wrong").
S Steadiness
What they want: Safety and clarity. S-types don't love surprises, and hard feedback can feel destabilizing, especially if it comes out of nowhere or sounds like the relationship is at risk.
What misses: Ambiguity. If the feedback is vague ("you could communicate more assertively"), they'll fill the gaps with anxiety. Rushed feedback backfires too, the kind delivered between meetings or over email when the topic deserved a real conversation.
What works: Create the right conditions. Give them notice if you can ("I want to talk through something with you today"). Be specific about the behavior, not the person. Reassure them that you're raising this because you trust them and want things to work.
C Conscientiousness
What they want: Evidence and reasoning. C-types don't just want to know what the issue is. They want to understand why it matters and how you got there. Feedback without logic doesn't compute.
What misses: Impressionistic or feelings-based feedback ("it just didn't feel right"). Vague positive feedback ("you did great") is equally useless to them. They want to know specifically what worked and specifically what didn't.
What works: Come prepared. Have examples. Explain your reasoning. If you say "this approach isn't working," be ready to show the data or the observation behind it. They may push back. Welcome it. That's usually engagement, not resistance.
The thing feedback-givers miss
Feedback that works is calibrated to the receiver, not the giver. Sounds obvious. But most managers give feedback in their own style, and then blame the missed landing on the other person being defensive or unaware.
When feedback doesn't land, the first question isn't "why won't they hear this?" It's "did I deliver it in a way they could actually receive?"
That shift puts the responsibility where it belongs, on the person giving the feedback, and it trades frustration for a plan.
Start by naming the style of the person you're giving feedback to. Then ask whether you're delivering it the way they need to receive it. Not the way you'd want it. The way they do.
Most people can do this once they stop thinking about it as a performance ("I need to be nice about this") and start thinking about it as communication ("I need this to actually land").
Want a full playbook?
The DiSC Deep Dive Guide includes communication scripts, a cross-style friction matrix, and 36 exercises for building real fluency, not just awareness.
Download free PDF guide Book a free intro call