Managing high D employees without breaking what makes them effective

It is Tuesday standup and your high D engineer is twelve minutes in on a topic that was supposed to be a status update. The room has gone quiet in two different ways. Half the team is leaning in. Half the team has stopped speaking.

You can feel the meeting tip. Whatever you say next will either close the gap or widen it. Telling the high D to take it offline will read as a slap. Letting it run will burn the rest of the agenda. You have done this both ways before. Neither felt like leadership.

What you actually need is a small move that protects the room without dimming the person carrying it. That is what this page is for.

Why this keeps happening

What is happening: High D teammates push for speed and outcomes. They cut to the call, name what is wrong, and keep going when the room would rather take a breath. When a manager has not adapted, the result is a team that either drags behind them or shuts down around them.

How it feels: You feel torn. You respect the directness. You also see the wake. You catch yourself softening their feedback for them in side channels, or apologising to teammates after meetings. You suspect they can tell. They can.

Why it should not be this way: Direct people are not the problem. Direct people without a manager who can match their pace are. This is a job for you, not a personality to fix.

How they receive feedback

High Ds want feedback the same way they give it: short, factual, and forward. If you bury a hard sentence inside three soft ones, they will mishear the soft ones as the message and ignore the hard one. Then nothing changes and you are frustrated.

Lead with the result, then the behaviour, then the ask. Ten words each is a lot. "You ran over by twelve minutes. The team stopped contributing. Wrap your update at two next time and bring the rest to me." That is the entire script. They will hear all three sentences and most of them will say thank you.

Five 1:1 questions that land

1. What did you decide this week that you would do the same way again?
2. Where did the team slow you down, and where was the slowdown actually useful?
3. Who on the team gave you something you did not expect this week?
4. What is one decision you are sitting on, and what is the hold-up?
5. If I made one change to how we run standup, what would help you most?

Coaching script

Use this when a high D is leading well but burning the room. The goal is to keep the engine and reshape the wake. Three moves, in order.

• Name the result you both want, in their language. "You want this team to ship faster. So do I."
• Name the cost of the current move, factually, with one example. No softeners. "In Tuesday standup, two people stopped contributing for the rest of the meeting."
• Hand them a small concrete adjustment they can make this week. "Wrap standup updates at two minutes. Bring the longer thread to me on Wednesday." Then stop talking.

Conflict repair script

Use this after the high D and another teammate have left a meeting frustrated. Run it the same day. Repair stales fast.

• Open with what each side thinks happened, in your own words. "You think they were dragging. They think you cut them off."
• Ask each person what they actually need from the next meeting. Write it down. Do not let either of them rewrite the other person's need.
• Agree on one small protocol change that costs the high D almost nothing and gives the other person room. A timed update, a written follow-up, a designated devil's advocate. Pick one.

A plan you can start this week

1. Stop softening their feedback for them. Speak in their cadence. Lead with the result, then the behaviour, then the ask. Ten words a sentence is plenty.
2. Give them a stage that has edges. They will run to the edge of any container you give them. A two-minute standup slot is a container. A vague "share when ready" is not.
3. Repair the same day. When the wake hurts someone, you have until end of day to run the conflict script above. After that, it sets.

What happens if you wait

If you do nothing, two things happen. The high D learns that this team is too slow for them, and starts looking. The rest of the team learns that being direct gets rewarded with extra room, and either copies it badly or goes quiet.

You lose the person who was carrying the pace, and inherit a team that is now quietly resentful of whoever you hire next.

What you'll see in Team Mode

Department Dynamics turns this page from a read into a tool you put in front of both groups this week. Two teams, plotted on the pace and focus axes, with the working agreement written for both sides.

See Team Mode

Frequently asked

How do you motivate a high D employee?

Give them a clear win condition, real authority to make the call, and feedback that respects their time. They are motivated by progress, not by recognition events. If they cannot point at progress on Friday, you will lose them.

What do high D personalities hate most at work?

Meetings that should have been a decision, managers who hedge, and being asked to wait for permission they already had. Anything that delays a yes or a no reads as friction.

How do you give feedback to a high D?

Short, factual, forward. Lead with the result you want, name the specific behaviour, give one concrete ask. Do not stack softeners. They will hear the softeners and miss the message.

Are high D employees good leaders?

Yes, when they have a manager who matches their pace and a team that trusts them to repair. The same edge that runs over a standup is the edge that ships a hard call on a Friday afternoon.

How do you calm down a high D employee?

You do not. You give them the next clear problem to solve. Calm is not their goal. Progress is. If you keep redirecting them toward progress, the heat lowers on its own.