The Conversation You Have Been Avoiding for Six Months

Putting it off is rarely a nerve problem. The conversation has to answer two separate questions, and you have been carrying them as one.

You have already had it several times, silently, in the car and in the ten minutes before a meeting that then went somewhere else. Every version ends about the same way, which is part of why it has not happened out loud. In the meantime you have been building around the problem. Work that should go to this person goes to someone else, and you do not say why. You review things you would not review for anyone at that level. Your own week has quietly reshaped itself around what this person will and will not finish.

Most of the writing on this treats the delay as conflict avoidance and tells you to be direct and to do it sooner. That is not wrong, and it does not help, because the reason you have not been direct is that you do not yet know what you would be direct about.

Two questions, carried as one

The conversation has to answer two questions, and they do not have the same answer.

The first is about the person. Can they do this work, at this level, with the support they have now and a reasonable amount of time?

The second is about the position. Is the job built so that a capable person could succeed in it? Count what it reports to. Compare the authority it was given against what it is held responsible for. Look at the pieces that were added over the last two years, each time something elsewhere was cut, and notice whether anyone ever redrew the position afterward or just kept adding.

Until you have answered the second question, you cannot ask the first one honestly. That is usually where the six months went. Somewhere in you sits the possibility that the role is the problem, or half of it, and so every draft of the conversation you write in your head carries both charges at the same time. The person hearing it will take the harsher one.

What the delay has already cost

You became the compensation. Every workaround you built to keep the unit moving is a small piece of the problem that is now invisible from the outside. Your director sees a functioning team. You see the hours you spend holding a seam together. The longer that runs, the harder the conversation gets, because you will be raising a concern about someone whose recorded performance looks acceptable, and part of the reason it looks acceptable is you.

Their colleagues have known longer than you have been deciding. People who work next to each other can tell what is landing and what is being absorbed by someone else. When a leader says nothing for two quarters about work everyone can see, the team does not read that as patience. It reads as a standard that applies unevenly, and the people carrying the extra weight start doing the arithmetic on whether their own effort is being noticed.

The person lost the time. This is the cost that gets left out of the argument you have been having with yourself. Six months ago they could have used the information. They could have asked for a different assignment, or pushed back on the scope of the job, or gone somewhere the fit was better, or fixed the thing. Withholding it did not protect them. It protected the week you were going to have to give up.

Taking the two questions apart

Write the role before you write anything about the person. One page, no names. What does this job actually require now, what does it control, what does it depend on other people to deliver, and how much of it has to happen at once. Then ask whether the strongest person you have ever hired could do it as it currently stands. If the answer is no, you have a structural problem, and starting with a performance conversation puts a person on trial for a design decision that somebody made above them.

Say which conversation this is in the first minute. If the role is broken, open with that, tell them you are changing it, and be specific about what comes off. If the issue is performance, then it is performance, and it needs three things: the observable behavior, when it happened, and how many times. Not a summary of your impression. People can respond to a dated example. Nobody can respond to a general sense that things have not been going well, which is why those conversations end with agreement in the room and no change in the work.

Name the interval and the evidence before you leave. Six weeks, these two or three things, and this is what different looks like when I see it. That sentence is what separates a real conversation from the version you will be having again in the spring. It also gives the person something they can win, which matters more than most leaders expect, and it commits you to looking at the same evidence they are looking at.

The part that is about you

Ask yourself how long you have actually known. Not when you first put words to it, but when you first found yourself routing work around this person. That gap is not a scheduling problem. It is worth understanding, because you will be in this position again with someone else, and the delay is the part of it you control.

Then ask a harder one. Is there a version of this where you hired someone for a job that then changed underneath them, and you never told them the job had changed? That happens constantly in institutions under pressure, and it is not a failure of character on anyone's part. It does mean the conversation you owe is a different one, and it starts with you naming the change rather than asking them to explain a gap you created.

There is also the possibility that you have been protecting a relationship. That is a real reason and it deserves to be said plainly rather than converted into some more defensible one. It is also worth testing, because a leader who avoids the conversation to keep the relationship usually loses the relationship anyway, about a year later, in a worse form.

Three questions

When did you first route work around this person, and what did you tell yourself that day? Get to the actual date. The distance between that date and today is the size of the problem you are working with.

If a strong hire started in this role Monday with no history and no goodwill, what would break in the first month? Everything on that list belongs to the job, not the person, and you have to fix it or say out loud that you are not going to.

What are you waiting for that would make this easier? Write it down and look at whether it is actually coming. If it is not, then the conversation is not waiting on circumstances. It is waiting on you, and it has been for six months.