.svg)
Marcus has run the same weekly meeting for two years. He gets through the agenda in twenty minutes, makes the calls that need making, and ends early. He thinks it's efficient. Two of his four team members have stopped bringing up problems in that meeting. They wait, then raise things one-on-one, days later, when the decision has already moved on.
Nobody in that room is difficult. They're just working from different defaults.
DISC describes behavior, not identity
DISC is a behavioral model. It describes how people prefer to act, communicate, and make decisions at work, across four dimensions: Dominance, Influence, Steadiness, and Conscientiousness.
The critical nuance, and the one most explanations get wrong: DISC doesn't sort people into four boxes. Every person has all four dimensions in different proportions. You're a blend, not a quadrant. Your collaboration style reflects which dimensions are strongest for you, and that mix shapes how you default, especially under pressure. You'll likely recognize parts of yourself in all four.
That distinction isn't pedantic. The moment DISC becomes a label, it stops being useful and starts being an excuse. "That's just how I am" is where development goes to die.
The four dimensions
Dominance is driven by results, speed, and directness. High-D contributors decide fast and say what they think. In meetings they're decisive and to the point, and impatient with long discussion. Under pressure they get more forceful. The blind spot: moving so quickly that other people's input never makes it into the room.
Influence is driven by connection, enthusiasm, and recognition. High-I contributors energize a group, tell the story, pull people in. Under pressure they get louder, or avoid the hard truth to keep the mood intact. The blind spot: reading positivity as agreement.
Steadiness is driven by stability, harmony, and loyalty. High-S contributors listen more than they speak and hold teams together. Under pressure they go quiet and absorb the tension. The blind spot: dissent that doesn't surface until it's become resentment.
Conscientiousness is driven by accuracy, quality, and preparation. High-C contributors are analytical and thorough, and want to be right before they speak. Under pressure they withdraw and over-analyze. The blind spot: silence that reads as agreement when it's actually unresolved concern.
Every dimension makes sense from the inside. No dimension is better. Each carries a natural strength and a real growth edge. And none of them describes anyone completely: these are tendencies, not scripts. A high-D manager listens carefully on the days it matters most. A high-S colleague pushes back hard when the stakes are real enough.
Back to Marcus
Marcus has high Dominance. Twenty-minute meetings feel efficient to him because he processes fast and decides fast. One of his quiet team members has high Conscientiousness: she needs time to prepare and doesn't want to raise a concern she can't yet support. Another has high Steadiness: he won't interrupt momentum to introduce friction.
Marcus isn't doing anything wrong by his own logic. Neither are they. But the meeting is designed for one dimension and attended by four.
Once Marcus can see that, the fix is small: send the agenda two days ahead, and ask specific questions rather than "any concerns?" A high-C team member can prepare. A high-S team member gets a direct invitation instead of an open floor.
Where awareness stops
Here's what most DISC explanations leave out: understanding the model doesn't change what you do.
Managers can name their style, name their team's styles, and still run the same meeting on Monday. The insight is real; the transfer isn't automatic. Knowing that high-C colleagues need advance notice is easy. Remembering it in the twenty seconds before you say "any concerns?" is a different skill entirely, and that one is built through repetition, not comprehension.
This is why DISC works best as a starting point rather than an endpoint. The assessment gives you the shared language. What you do with it, deliberately, over time, is where behavior actually shifts.
Practice it
Before your next team meeting:
- Name your own dominant dimension, and one way it shapes how you run the meeting. Not how you'd like to run it. How you actually do.
- Pick one person whose defaults differ from yours. What does the meeting look like from where they sit?
- Change one structural thing, not one intention. Send the agenda earlier. Ask a named person a specific question. Leave a silence for eight seconds instead of filling it.
- After the meeting, check what changed. If nothing did, the adjustment was too small. Try a bigger one.
DISC gives your team a shared language. FlyingPenguins turns it into practice, so what people learn about themselves shows up in how they actually work.
