The 4 profiles that make (or break) an IT team
You work with people you don't understand. And you think they're the problem.
The meeting starts at 9 a.m. Someone has been talking for five minutes without having said anything. Another hasn’t said a word, but you can tell he disapproves of everything. He’s sitting there with his arms crossed, staring intently at his coffee. A third has already made up his mind and is just waiting for everyone else to finish so he can move on.
And you try to follow along, wondering how competent adults can spend so much time solving nothing.
It’s not a question of IQ. It’s not a question of goodwill. It’s not even a question of organizational politics, even if it sometimes looks like it.
It’s a matter of filtering.
Each person in this room processes information, risk, relationships, and decisions in their own unique way. And when these filters don’t recognize each other, everything slows down, everything clashes, everything costs more than it should.
This series exists because no one has explained it clearly to you. Not in training, you know, those days where they stick colored labels on people and everyone laughs politely before going back to exactly how things were before. Not in management books that you don’t have time to read anyway. Not in team retrospectives where they talk about “communication” without ever naming what’s really important.
IT teams have a particular problem with this. We recruit for technical skills. We evaluate based on deliverables. We tolerate interpersonal friction because we tell ourselves it’s the price to pay for having brilliant people. And we end up normalizing dysfunctions that cost entire projects.
A senior developer who stalls a decision for three weeks because they need to validate every hypothesis. A manager who imposes a direction without consultation and then wonders why their team is sluggishly executing it. A discreet and reliable team member who hands in their resignation on a Friday afternoon without anyone seeing it coming. Another who generates enthusiasm at every meeting but whose ideas never come to fruition.
These aren’t character flaws. They’re different profiles. And understanding the difference completely changes how you work with these people.
When you can read what’s really happening in a room, you waste less energy fighting against behaviors you don’t understand. You start playing a game whose rules you know. And in IT, that’s a real competitive advantage.
The Diagnosis
There are several models for categorizing behaviors in the workplace. The most common one in the training you’ve probably attended is called DISC. Other derivative versions circulate under the name Insights Discovery or simply “the 4 colors”.
The terminology varies. The underlying logic, however, remains stable.
What the model says and what it doesn’t say
The model is based on two axes: are you task-oriented or people-oriented, and are you direct or reserved in your communication style? The intersection of these two axes yields four dominant profiles, each associated with a color depending on the version you use.
What the model doesn’t say: no one is a pure color.
Most people have a dominant and a secondary style. Some adjust their style depending on the context (more direct in crisis mode, more conciliatory in calm mode). The model is a tool for understanding, not a permanent label.
Each of the 4 profiles can be summarized in one sentence.
The Red wants results now, without going through the “two-hour discussion” phase.
The Blue wants to understand before acting, document before delivering, validate before committing.
The Green wants everyone on board and for no one to get hurt in the process.
The Yellow wants things to be dynamic, stimulating, and for the people around him to be as energized as he is.
Each of these profiles has real value within a team. Each also has a real cost when it is misunderstood or mismanaged.
Why does it particularly stick in IT?
In most of the IT organizations I’ve worked with in Quebec since 2010, I’ve observed a real dynamic. The technological environments overrepresent the Blue profiles: rigor, analysis, and a need for precision.
They value the Reds when they need to deliver quickly under pressure. They systematically underestimate the Greens until the turnover rate costs them a fortune. And they don’t know what to do with the Yellows, who disrupt meetings but sometimes keep the culture alive.
The problem isn’t that these profiles coexist. The problem is that we never name them. So everyone interprets each other’s behavior through their own filter, and we call it “a personality clash” when it’s actually a misinterpretation.
What this series will do
Over the next few Tuesdays, we’ll analyze each profile one by one. How to recognize it. What truly motivates it. What holds it back. And how to adapt your communication with it without betraying yourself.
The last article in the series will be the most actionable: what to do in practice when several profiles clash in your team, and how to navigate this from any position — developer, manager, consultant, contributing individual.
The Mirror
Before we continue: which of these four profiles reminded you of someone in particular on your team?
And which one reminded you a little of yourself?
Because the uncomfortable part of this model is that understanding others is good. Seeing yourself in it is what really changes things.
What you can do on Monday morning
If you want to start using this model this week, here are three concrete things you can do even before reading the following articles. Three tips, no additional theory.
1. Observe before concluding. In your next team meeting, choose one person and observe them based on a single criterion: do they talk mainly about tasks and results, or mainly about relationships and impact on people? This will already give you a starting point for understanding. You don’t need to categorize someone to begin to read them better. You just need a simple question to ask yourself.
2. Identify your own dominant profile. Ask yourself this question: in a project under pressure, what is your first reflex? Make a decision and move forward (Red). Ask for more data before committing (Blue). Check that everyone is aligned (Green). Look for a new and stimulating solution (Yellow).
This first reaction is your dominant profile speaking. Knowing yours allows you to understand why certain behaviors around you drain your energy — and why you probably drain others’ energy too.
My first reflex under pressure is to... — complete this sentence honestly before reading the rest of the series.
3. Replay a recent friction with a different filter. Think of a recent interaction that frustrated or exhausted you. Not an open conflict, just something that caused friction. Now ask yourself: Did this person perhaps have a very different profile than you? Were they processing the situation through a filter you hadn’t noticed?
You don’t need to answer now. Just leave the question open. The next articles will help you answer it more precisely.
If you want to stop wasting energy decoding behaviors you could simply read, the following articles will give you access to detailed profile-based analysis grids and the exact wording for difficult conversations. Let’s stop philosophizing. Let’s get to work.
Next week, we’ll start with Red. The one who decides before you’ve finished your sentence. The one you find abrupt — or the one you are, and you wonder why others can’t keep up with.
Keep this question in mind until Tuesday: do you read the people around you, or do you judge them?
Is your IT project going nowhere? The worst thing you can do is commission a 3-month theoretical analysis from a large firm. I’m opening 3 spots this quarter for my Backstage Immersion. In 5 days, I’ll audit your systems and team dynamics “behind the scenes,” and deliver a roadmap with 2 priority action plans to get you back on track. Discover my services and book a 15-minute call.