How to Handle Vague Feedback

How to handle vague feedback requires one thing most professionals avoid: asking for specificity in the moment. The instinct is to nod, accept the feedback politely, and figure it out later. That instinct keeps people stuck. The response that actually works acknowledges the feedback, signals genuine openness, and asks for one concrete example. That single follow-up question transforms vague feedback into something you can actually use.

Vague feedback is one of the most common and most quietly damaging workplace experiences. It sounds like "you need to be more strategic," "your communication could be stronger," or "you're not quite hitting the mark." Each of those phrases points at something real. None of them tells you what to actually change.

What follows is the guessing cycle. You try something. You are not sure if it is the right thing. You wait for the next round of feedback to tell you whether you guessed correctly. Months pass. The pattern repeats. The frustration builds on both sides.

Breaking the cycle requires a simple but counterintuitive move: asking for the specific example the person giving the feedback almost certainly has in their head but did not share.

Why People Accept Vague Feedback Without Pushing Back

Most professionals accept vague feedback for one of three reasons. They do not want to seem defensive. They assume they understand what is meant even when they do not. Or they worry that asking for more will come across as arguing.

None of those concerns are unreasonable. But they produce a worse outcome than a well-framed follow-up question would.

What NOT to say: "Okay, I'll try harder."

This phrase sounds cooperative. What it actually does is accept the feedback without gaining any clarity about what needs to change. You walk away with increased anxiety about whether you are doing the right things and no additional information to guide the next attempt. The person who gave the feedback probably feels like the issue has been addressed. It has not been addressed. It has been deferred.

What NOT to say: "I'm not sure what you mean."

This phrase is honest, but it tends to read as passive or as a mild challenge. It puts the burden back on the feedback giver without offering a bridge. The response you get is usually a slightly rephrased version of the original vague feedback, which does not help. What you want is not a restatement. You want an example.

The Follow-Up Question That Actually Works

The most effective response to vague feedback has two parts. The first signals that you took the feedback seriously and are not reacting defensively. The second asks for the specific example that will make the feedback usable.

"I appreciate the feedback. To make sure I improve in the right way, can you give me a specific example of what you'd like done differently next time?"

That question is doing a lot of work quietly. The opening phrase signals receptiveness. "In the right way" signals intent to actually change, not just to argue. "A specific example" is the operational ask. "Next time" orients the conversation toward the future rather than relitigating the past.

You will get one of two responses. Either you get a concrete example that tells you exactly what the feedback is really about, or the person realizes they cannot produce a specific example and the feedback becomes a more collaborative conversation about what they are actually looking for. Both outcomes are better than what you started with.

A Step-by-Step Approach to Vague Feedback Situations

Slow down your instinct to agree immediately. The urge to say "absolutely, I hear you" and move on is strong. Resist it long enough to identify whether you actually have enough information to act on what you just heard.
Acknowledge the feedback before asking for more. "I appreciate you raising this" is not empty politeness. It signals that you are not about to become defensive, which makes the person more likely to engage genuinely when you ask for specificity.
Ask for one specific example, not a full audit. "Can you point to a specific instance?" is a reasonable ask. "Can you give me a detailed breakdown of everywhere you've seen this issue?" is not. Keep the ask narrow and focused.
Listen to the example without defending against it. When the example comes, the temptation is to explain the context behind what happened. Resist that. The context may be relevant, but the moment to share it is after you have fully understood what the feedback is pointing at.
Confirm your understanding before the conversation closes. "So if I'm hearing you correctly, what you're looking for is [specific behavior change] in [specific type of situation]. Is that right?" That confirmation prevents both of you from walking away with different understandings of what was agreed.
Follow up at an appropriate interval. If the feedback was significant, a check-in two to three weeks later signals that you took it seriously. "I've been working on [specific thing]. Have you noticed any difference?" That question is powerful because it shows accountability and creates a feedback loop rather than a one-time event.

When Vague Feedback Is a Pattern, Not an Incident

Some managers consistently give feedback in ways that are too general to act on. If you are regularly hearing things like "keep it up" or "you need to improve your executive presence" without any specifics, the vagueness may be a reflection of how that person gives feedback rather than a reflection of a real performance gap.

In those cases, the conversation shifts slightly. You are not just asking for a specific example in the moment. You are trying to establish a feedback cadence that works for both of you.

"I really value your feedback and want to make sure I'm acting on it well. It helps me most when I have a concrete example to anchor to. Going forward, would it work if we took a few minutes after [deliverable or meeting] to talk about one specific thing I could have done differently?"

That request is not a complaint about how your manager gives feedback. It is a proposal for a practice that works better for you. Most managers respond positively to that kind of specific, constructive proposal.

Using AI to Prepare for Feedback Conversations

If you know a feedback conversation is coming, or if you want to process a recent one and figure out how to follow up, this prompt is useful:

"I received vague feedback at work and want to respond professionally. The feedback was [describe it]. Help me write a short follow-up message that shows openness, asks for a specific example, and does not sound defensive. Keep it under four sentences."

The Workplace Survival Guide includes AI Prompt Extensions for navigating feedback conversations, including situations where the feedback is vague, where you disagree with it, or where you need to ask for more without triggering a defensive response.

Tired of leaving feedback conversations without real clarity?

The Workplace Survival Guide includes scripts, anti-scripts, and AI prompts for vague feedback, difficult managers, workload conversations, and more. $29, instant access. Get your copy here.

Frequently Asked Questions

What if the tension involves someone who is senior to me?

The principles are the same, but the framing shifts slightly. Lead with openness and curiosity rather than a statement of the problem. "I've been getting the sense that something is off in how we're working together, and I wanted to check in. Is there something I've been missing?" That approach preserves the relationship dynamic while still naming the issue and opening the door.

What if the other person denies there is any tension?

Acknowledge their response and describe what you have observed specifically. "I hear that, and I appreciate you saying so. I've noticed that our recent project handoffs have felt more stilted than usual, and I wanted to make sure I haven't done something that affected our working relationship." Specific observations are harder to dismiss than general feelings. If they continue to deny it and the observable issues persist, a conversation with your manager may be the appropriate next step.

Should managers always intervene in team tension, or is some friction healthy?

Productive disagreement is healthy. Interpersonal friction that is affecting collaboration, morale, or output is not. The distinction is usually visible in whether the friction is idea-focused or person-focused. Healthy debate is about approaches and decisions. Problematic tension is about the people themselves, or has started to affect who will work with whom.

What if the tension is coming from a structural issue, like unclear roles, rather than a personal one?

Then fix the structural issue. Interpersonal conversations are useful, but they cannot sustainably resolve a role clarity problem or a workload distribution problem. The conversation about the tension should surface the structural root cause, and then the manager needs to address that root cause directly. Asking two people to "communicate better" while leaving the ambiguous ownership in place is a recipe for the same tension returning.

How do I address tension when I am not sure who is at fault?

Start by not trying to assign fault. The most productive tension conversations are not about who is to blame. They are about what needs to change going forward. "I'm not here to figure out what went wrong in the past. I want us to establish what working well together looks like from here" is a frame that sidesteps the blame question entirely and focuses on the outcome both parties need.

Page updated

Report abuse