How to redirect a team member without breaking the relationship

Redirecting: the act every manager dreads

Ask any manager what moment they dread most in their week. The answer almost always comes back: having to redirect someone.

And for good reason. A poorly handled redirection can alienate the team member, destroy months of accumulated trust, or even trigger a resignation. Conversely, an avoided redirection lets the situation deteriorate — and sends a devastating message to the rest of the team: "here, you can cross the line without consequences."

The real challenge isn't choosing between firmness and the relationship. It's doing both at the same time.

What makes most redirections fail

Waiting too long

The most common reflex: postpone. "I'll see if it sorts itself out." It never does. And the longer you wait, the heavier the message becomes, loaded with accumulated examples and bottled-up frustration.

A redirection given within the week is a conversation. A redirection given three months later is a prosecution.

Confusing redirection with punishment

Redirecting isn't punishing. It's restating expectations, naming the gap, and offering a path back. The posture is fundamentally different:

• Punishment: "You made a mistake, here are the consequences."
• Redirection: "Here's what I observed, here's the impact, and here's what I expect from you."

Using the same tone with everyone

This is probably the most underestimated mistake. A direct, factual redirection will work with some profiles and completely alienate others.

A team member with a dominant profile (in the DISC framework) will need a short, factual exchange, no beating around the bush. A steadier or more conscientious profile will need more context, empathy, and time to process the message.

The same message, delivered the same way, can build trust with one person and destroy it with another.

The 4-step method

1. Name the facts — without judgment

Start with what is observable and indisputable.

• Avoid: "You're not reliable lately."
• Better: "The last three deliverables arrived 2 to 4 days late compared to the agreed dates."

Facts set the frame. Judgments open a debate.

2. Express the concrete impact

Help them understand why it matters — not to blame, but to give meaning.

"When deliverables arrive late, the downstream team can't move forward. It creates frustration and pushes back the entire timeline."

Impact makes the redirection legitimate. Without it, the team member may feel you're micromanaging for no reason.

3. Adapt your approach to the profile

This is where most management guides stop. But in practice, how you deliver the message matters as much as the message itself.

Some guidelines:

• Direct / driver profile: get straight to the point, don't sugarcoat, propose a solution quickly. This profile respects frankness.
• Expressive / enthusiastic profile: start by recognizing their efforts, show you believe in them, then address the issue. This profile needs to feel they're not "condemned."
• Steady / loyal profile: take your time, don't catch them off guard, give them space to respond. This profile needs security.
• Analytical / thorough profile: bring precise facts, data, dated examples. This profile needs to understand the logic.

This is exactly what VikL does: adapt formulations and conversation strategy to your interlocutor's behavioral profile — and yours — so the message truly lands.

4. State a clear expectation and open the dialogue

End with what you concretely expect, then hand them the floor:

"What I expect is that the next deliverables are submitted on time, or that you flag any anticipated delay 48 hours in advance. How do you see things from your side?"

That last question changes everything. It transforms a monologue into a conversation — and sometimes reveals blockers you hadn't seen.

3 mistakes to avoid after redirecting

1. No follow-up. A redirection without follow-up is wasted effort. Schedule a short check-in 1 to 2 weeks later.
2. Overcompensating with niceness. After redirecting, some managers feel guilty and become excessively lenient. It blurs the message.
3. Mentioning it publicly. What's said in a redirection stays in a redirection. Any reference in front of the team destroys trust.

In summary

Redirecting isn't an act of severity. It's an act of clarity — and respect. A team member who knows where they stand and what's expected is in a far better position than one navigating in the dark.

The key is adapting your approach to the person in front of you. Because a good redirection isn't the one that relieves you — it's the one the other person can actually hear.