Specificity Matters: Why "Good Feedback" Isn't Good Enough

---

Vague feedback creates uncertainty. Specific feedback creates a path forward.

"Be more strategic."

"Communicate better."

"Take more ownership."

"Be more proactive."

"Think bigger."

Most leaders have either given or received feedback like this. It sounds reasonable. It may even sound helpful. 

But there is a problem:

What does it actually mean?

Imagine your manager tells you:

"You need to be more strategic."

You might leave the conversation with several questions.

What did I do that wasn't strategic?

What would a more strategic approach have looked like?

What should I do differently next time?

How will I know if I'm improving?

If the person giving the feedback can't answer those questions, the employee is left to fill in the blanks. And people don't always fill in the blanks the same way.

One person may interpret "be more strategic" as thinking further ahead. Another may think it means delegating more. Someone else may believe it means focusing less on details.

The feedback has been delivered. But shared understanding hasn't necessarily been created.

Useful feedback gives people something concrete to work with.

A more specific version of the same feedback might be:

"In the last two project meetings, you focused primarily on the immediate issue in front of the team. I'd like you to spend more time connecting the current decision to the project's longer-term objectives."

Now there is something to discuss.

The employee can ask questions.

They can explain their reasoning.

They can disagree.

They can begin thinking about what they might do differently.

Specificity doesn't guarantee agreement. It creates the conditions for a more productive conversation.

Some leaders worry that being more specific will make feedback feel more critical.

Usually, the opposite is true.

Compare:

"You're not a strong communicator."
 

with:

"In yesterday's meeting, you answered the client's question before confirming the information with the project team. Next time, pause and verify the information before responding when you're uncertain." 

The second statement is more direct. But it is also less personal.

It focuses on something that happened rather than making a broad judgment about who someone is.

That distinction matters. Feedback about a behavior can be discussed. Feedback about someone's identity is much harder to work with.

One of the simplest ways to make feedback more specific is to ask:

What did I actually observe?
 

Consider the difference between:

Interpretation:
"She doesn't take initiative."

and:

Observation:
"After the client changed the project requirements, you waited until our next scheduled meeting to raise the issue."

The first is a conclusion.

The second gives the person something concrete to respond to.

Maybe the employee didn't realize the change was significant. Maybe they thought someone else was responsible for raising it. Maybe they were waiting for additional information.

The conversation can now uncover that context. That's important because feedback should not eliminate inquiry.

It should create better inquiry.

Specificity isn't only about describing what happened. It also means explaining why the behavior matters.

For example:

"The proposal went to the client before the pricing assumptions were confirmed. Because Finance hadn't approved the numbers, we had to correct the proposal afterward."
 

Now the employee can see the connection between behavior and consequence. This doesn't require exaggerating the impact. In fact, credibility is often strengthened when leaders describe consequences accurately rather than dramatically.

The goal is simply to make the connection visible.

A feedback conversation can accurately identify a problem and still fail to create change.

Why? Because identifying what went wrong isn't the same as explaining what should happen next.

Consider:

"You need to be more proactive."
 

Now compare:

"When you see a risk that could affect the timeline, raise it as soon as you identify it—even if you don't have a solution yet."

The second statement creates a behavioral target.

It tells the employee what "proactive" looks like in this context. That is the real power of specificity. It turns an abstract expectation into something observable.

There is a trap on the other side, too. Specific feedback does not require a 45-minute presentation of every mistake someone has made. More detail isn't automatically better.

The goal is useful detail.

A good test is:

Would this example help the person understand exactly what I'm talking about and what they can do differently?
 

If yes, you probably have enough. If the person could reasonably respond, "I still don't know what you mean," you may need another example.

This may be the most important reason specificity matters.

Vague feedback requires the recipient to interpret a broad label.

Specific feedback gives the leader and employee something concrete to interpret together.

Instead of:

"You need to communicate better."

the conversation becomes:

"During the last two project updates, the team didn't learn about the timeline change until after the meeting. Going forward, I want you to flag significant changes before the meeting so the team has time to adjust."

Now the employee can explain. Perhaps they didn't have the information. Perhaps they thought the change was temporary. Perhaps they were waiting for confirmation.

The leader may discover information they didn't have. That's not a failure of feedback.

That's feedback doing its job.

Before your next feedback conversation, ask yourself:

Can I describe the behavior or situation without relying on a label?

Can I explain the relevant impact or consequence?

Can I describe the desired behavior or expectation?

Can we identify a practical next step or opportunity to revisit the issue?

If you can answer all four, your feedback is much more likely to be actionable.

The purpose of specificity isn't to make leaders better at criticizing. It's to make feedback more useful.

People cannot reliably act on information they cannot understand. They cannot improve what they cannot identify. And they cannot build new habits from a message that leaves them guessing about what "better" looks like.

Specificity turns feedback from a judgment into information. And information gives people something they can work with.

So the next time you catch yourself saying:

"Be more strategic."

"Communicate better."

"Take more ownership."

Pause.

Ask yourself:

What would I actually want this person to do differently?

Then say that.

Ready to prepare for a conversation where specificity matters?