The Red Decides Fast, Delivers Fast, and Bulldozes Everything in Their Path.
Not out of arrogance. By nature. What it costs and how to work with it.
You work with a Red. Or you are one. Either way, this is going to sting.
They walk into the meeting with the conclusion already in their head. They listen for the first two minutes, out of politeness, or because they’re still hoping someone will say something useful. Then they call it. Not because they’re arrogant. Because for them, the decision was obvious from the start — and everything after that is wasted time.
You’ve crossed paths with one. Maybe you manage one. Maybe you put up with one. Maybe you recognize yourself in this portrait and you’re wondering why everyone else can’t keep up with your pace.
This article is for both sides.
Red profiles are a minority in IT teams, but a minority that takes up a lot of space. Not out of malice. By nature. Their engine is results. Their unit of measure is progress. Their allergy is the status quo dressed up as process.
In an environment dominated by Blue profiles — analytical, rigorous, cautious — the Red stands out. They talk fast. They decide fast. They move on while everyone else is still validating.
Which produces two diametrically opposed readings of the same person. From the Red’s side: “I’m efficient, I deliver, I don’t drown in details.” From the team’s side: “They don’t listen, they make decisions without consulting anyone, they steamroll people.”
Both are right. That’s where it gets interesting.
The Diagnosis
The Red profile isn’t a difficult personality. It’s a filter oriented toward action and results, in a world where most people need more context, more time, more consensus before they move.
The problem isn’t the Red. The problem is the gap between their processing speed and everyone else’s — and the complete absence of any translation between the two.
What actually motivates them
The Red needs to feel like they’re moving forward. Not tomorrow. Now. Every meeting without a decision is a failed meeting. Every process that slows down action is an obstacle, not a safeguard. Every time someone asks them to revalidate something they’ve already analyzed, they read it as a lack of trust, not as caution.
This need for momentum isn’t pathological impatience. It’s how they measure their own usefulness. A Red who isn’t delivering, isn’t deciding, isn’t making things move — that’s a Red who’s suffering. Quietly, but genuinely.
What derails them
The Red checks out when they feel like they’re going in circles. When meetings pile up without conclusions. When decisions get pushed back for reasons that seem bureaucratic to them. When they have to defend choices they consider obvious.
At that point, two versions of the Red emerge. The first short-circuits the process: they decide alone, move forward without consulting, and discover three weeks later that their team didn’t follow. The second pulls back entirely: they execute mechanically, without investment, waiting to find a context where they can have real impact again.
Both versions cost the organization. And both are avoidable.
The mechanism nobody names
What the people around a Red interpret as arrogance is often something else entirely: an inability to slow down their own processing to let others catch up.
The Red has already done the work in their head. They’ve weighed the options, ruled out the bad ones, identified the best path. That work took a few minutes, sometimes a few seconds. The problem is they didn’t do it out loud. So when they announce their conclusion, everyone else doesn’t have the film. They just have the ending.
And an ending without the film looks a lot like a decision being imposed.
The Mirror
If you work with a Red: the next time they call it before you’ve finished speaking, ask yourself honestly — were they wrong? Or is the problem that they didn’t take the time to show you their reasoning?
If you are a Red: when did you last do the work out loud? Not to convince anyone. Just so others could see how you got to where you are. It doesn’t slow down the decision. It saves you from having to defend it for three weeks.
What You Can Try Starting Monday Morning
Three concrete situations. What you can do starting Monday, depending on where you sit.
If you manage a Red
Give them room to decide, with clear guardrails. A Red who’s told “you have full authority on X, within these constraints” delivers. A Red who has to go through ten approval layers slows down, works around them, or leaves.
When you need to pump the brakes, do it with facts, not process. “We can’t go there because the client set this specific constraint” lands. “We have to go through the committee first” doesn’t or at least, not without friction.
If you work alongside a Red
Stop waiting for them to ask your opinion. They won’t — not because they don’t care, but because it doesn’t come naturally to them. Take the space. “Before we decide, I have two points to raise” works. The Red respects someone who gets to the point just as fast as they do.
What doesn’t work: long intros, careful phrasing, “I just wanted to maybe mention that possibly...” They checked out at the third hesitation. Say what you have to say. Short. Direct. They’ll listen.
If you are a Red
Before your next important decision, do the work out loud. Not in a two-hour meeting — just two or three sentences. “Here’s where I am, here’s why, here’s what I’m proposing.” Thirty seconds. It changes everything about how others receive your conclusion.
And pick one person on your team — preferably someone Green or Blue — and ask them a real question before you decide. Not necessarily to change your decision. So that person feels like they’re in the conversation rather than facing a done deal.
The Red isn’t your team’s problem. The absence of translation between their pace and everyone else’s — that is.
The question you can ask yourself this week: in your team, who does that translation work? And if nobody does, what is it costing you?