Vague Feedback Is a Verdict

I kept someone on my team six months longer than I should have.

The person was good. Not bad at their job, not disruptive, not a problem employee in any way a handbook would flag. They just weren't growing in the direction the role needed them to grow. I knew it by month four.

Here's what I did instead of having the conversation:

I gave vague feedback. "Keep pushing on X." "I think there's more ownership to take on Y." Things that sound developmental but are actually verdicts wearing a coaching costume.

I told myself I was being patient. That development takes time. That maybe I was wrong about the ceiling I was seeing.

I wasn't wrong. I was avoiding.

This newsletter is about what that avoidance actually costs, who pays for it, and what the alternative looks like. I want both sides of this dynamic to read it. Because I think the people sitting in vague feedback right now deserve the decoder ring, and the managers giving it deserve to be asked harder questions.

The Three Costs

For me as a manager: six months of managing around a gap instead of filling it. Every project that touched their zone of weakness got routed differently. I was building invisible architecture to protect them from exposure, and I told myself it was leadership. It wasn't. It was organizational debt that compounded weekly. By month five I was spending more cognitive load on the workarounds than on the actual work.

For the team: they could feel the gap. Senior people always can. Nobody said anything directly because I hadn't said anything directly. But the workarounds were visible, and each one eroded trust in my judgment a little more. The cost wasn't visible on any dashboard. It showed up in the quiet ways the most talented people on the team started routing decisions around me instead of through me.

For the person: this is the part that still bothers me. Those six months of vague feedback? They internalized all of it as "I'm developing." Every "keep pushing" got logged as a sign of confidence. When the real conversation finally happened, they were blindsided. Six months of soft language followed by "this isn't working" felt like betrayal. And honestly? It was. I stole six months of clarity from someone I was supposed to be leading. That's not patience. That's cowardice with a leadership title.

Why It Happens

I've talked to dozens of hiring managers since then. The pattern is the same everywhere, regardless of function or level. Engineering leaders do it. Sales leaders do it. Ops leaders do it. The delay is almost never about the employee. It's about the manager's discomfort with the conversation.

We wrap it in softer language. "I want to give them a fair shot." "Maybe they just need the right project." "I'll revisit at the next review cycle." All true-sounding. All avoidance in a professional costume.

The underlying truth: nobody trained us for this. We got promoted into management because we were good at the work, then handed responsibility for telling people things that might end their job. Most of us figure it out by getting it wrong first. The cost of the learning curve gets paid by the people we manage.

The 90-Day Alternative

The version I wish I'd used: "Here's specifically where I need to see growth. Here's what that looks like concretely. Here's the timeline. And here's what happens if we don't get there."

Four sentences. Direct. Uncomfortable for one conversation.

Infinitely more respectful than six months of coded language.

The specificity matters. Not "I need to see more leadership." That's vague. "I need to see you running the cross-functional review without me in the room within the next 60 days, and the way I'll know you're ready is X." That's a real growth target.

And the consequence has to be real. Not "we'll talk again." "If we're not there by August, we'll need to have a different conversation about whether this role is the right fit." That's a verdict you can actually plan around.

The Decoder Ring (For The Other Side)

If you're sitting in a role right now and getting vague developmental feedback that never gets more specific, pay attention to what's happening around the feedback, not just the words.

Signals that tend to matter:

• Feedback that stays general across multiple review cycles, while your peers are getting concrete project assignments

• Projects routing around you that used to route through you

• Less invitation to the rooms where decisions happen

• "Keep doing what you're doing" while nothing about your trajectory is actually changing

Not always a verdict. Sometimes feedback really is developmental. But developmental feedback gets more specific over time. It comes with new assignments that test the growth area. It changes something.

Terminal feedback stays vague. And static. And comfortable for the person delivering it.

The hard question to sit with: if the feedback you've gotten in the last three review cycles was identical, and nothing about your responsibilities has changed in that time, what story is the silence telling?

What I Want Both Sides To Take Away

As a manager: the kind thing is the direct thing. If you've been giving someone vague feedback for more than two cycles, you owe them a different conversation. Even if it's the conversation that ends the role. Especially then.

As an employee: the absence of hard feedback isn't safety. Sometimes it's the opposite. And you deserve to know the difference before someone else makes the decision for you.

The whole problem with vague feedback is that it puts the cost of the manager's discomfort on the employee. Six months of "keep pushing" buys the manager six months of avoidance. The employee pays for it with six months of misplaced confidence and a more brutal landing when the truth finally arrives.

I wish someone had told me at 28 what I'm telling you now.