Managing high C employees without grinding the team to a halt

It is Thursday afternoon and your high C analyst has missed the deadline you agreed to on Monday. Their last message in the thread is nine more questions about the spec. Eight of the nine are reasonable. The ninth is the one that tells you they have not started.

If you push, you will get a thoughtful, polite reply explaining why moving without the answers would create risk you would both regret. They will be partly right. They are also stalling, and you both know it.

What you need is a way to honour the rigour without losing the week. That is a craft, not a personality clash.

Why this keeps happening

What is happening: High C teammates carry standards, precision, and a clean trail of why we made the call. They also stall under ambiguity, defer decisions to more information, and treat speed as the enemy of quality even when the quality bar has long been met.

How it feels: You feel stuck. You know the work is going to be excellent when it lands. You also know the rest of the team is waiting. You start carrying decisions for them in side channels because at least then something moves. Then you wonder why they feel underused.

Why it should not be this way: Rigour is not stalling. Stalling is rigour without a deadline. A high C who has a clear bar, a clear deadline, and an explicit "good enough" definition will ship more than anyone on the team.

How they receive feedback

High Cs need feedback that is specific, accurate, and grounded in evidence they can verify. Vague feedback reads as imprecise, and imprecise feedback they will discount entirely. Bring the example. Bring the data. Bring the specific paragraph.

Then separate the standard from the timeline. "This is excellent work. It is also two days late, and the team is waiting. I want both. Here is how we get both next time." That is the whole conversation.

Five 1:1 questions that land

1. What is one thing on your list this week that does not need to be perfect, and what bar would be enough?
2. Where is a decision sitting with you because you are waiting for one more piece of information?
3. What did you almost catch in someone else's work this week, and how should we share it forward?
4. What process change would let you trust the team's read more often?
5. Where am I asking for precision that the work does not actually need?

Coaching script

Use this when a high C is stalling on a decision in the name of rigour. The goal is not less rigour. It is rigour with a finish line.

• Acknowledge the standard. "You are right that there are open questions. The work you do once you start is the work nobody else on this team can do."
• Set the explicit good-enough bar for this specific call. "For this decision, decision-ready means the top three risks are named in writing with a recommended mitigation. The next three risks go in the follow-up doc."
• Agree a small visible commitment. "By tomorrow noon, send me the three risks and your call." Then hold the line. Do not extend.

Conflict repair script

Use this when a high C and a fast-moving teammate are in a loop where one is stalling and the other is pushing.

• Validate both reads, separately. The high C is protecting quality. The other person is protecting tempo. Both are leadership instincts, not failures.
• Make the bar explicit and shared. "For this kind of call, decision-ready is X. For this kind of call, the high C bar applies." Write it down.
• Agree a one-page risk note as the artefact that lets the team move. The high C gets the rigour they need. The other person gets the speed they need. The team gets a paper trail.

A plan you can start this week

1. Set the bar before the work starts. High Cs hold whatever bar you give them. If you do not name one, they will pick the highest one available. That is on the brief, not on them.
2. Separate decision from documentation. The decision can ship at eighty percent. The documentation can be excellent later. Telling them this changes their week.
3. Bring evidence to feedback. Specific, accurate, grounded. Vague feedback they will discount entirely, and you will not know it happened.

What happens if you wait

If you do not give them a clear bar and a clear deadline, you do not get more quality. You get the same quality, slower. And meanwhile the team learns that careful people stall. That is not a lesson you want a team to learn.

You will also lose the high C. Not loudly. They will simply notice that the work they do well is not the work that gets credit, and they will quietly find a team where it does.

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 C employee?

A clear standard, a clear deadline, and a manager who respects the work behind the answer. They are motivated by being trusted with something hard and being given the time to do it right.

What slows down a high C employee?

Ambiguity. Without a bar, they will pick the highest bar available. Without a deadline, the work expands. Both are usually on the brief, not on the person.

How do you give feedback to a high C?

Specific, accurate, grounded in evidence they can verify. Bring the paragraph, bring the example. Then separate the quality bar from the timeline bar. Praise the quality. Hold the timeline.

How do you keep a high C moving?

Define decision-ready in advance. Decision-ready is not publication-ready. Put the remaining questions in a follow-up doc, not in the spec. Hold the deadline.

Are high C employees difficult to manage?

Only if you have not given them a bar. Once they know the standard, the deadline, and the good-enough threshold, they are usually the most reliable people on the team.