How to Give Helpful Feedback Instead of Vague Feedback

How to Give Helpful Feedback Instead of Vague Feedback

"Good job."

The person smiles. You smile. Everyone is polite. Then nothing changes, because nobody knows what was good.

"Needs work."

The person nods. You nod. Everyone is less polite inside. Then nothing changes, because nobody knows what work is needed.

Vague feedback feels easy in the moment because it is short and safe. It also leaves the listener with a foggy little cloud instead of a map. Helpful feedback does not have to be long, but it should show the person what to keep, what to change, and what to do next.

Why it feels awkward

Specific feedback can feel more exposed than vague feedback. If you say, "Good job," you cannot be wrong in any interesting way. If you say, "Your second example makes the argument easier to understand," you have taken a position. The listener can ask questions. You may need to explain yourself.

That is exactly why specific feedback is useful.

In English, vague praise and vague criticism often sound friendly but incomplete. They are fine for quick encouragement, but not enough when someone is trying to improve. A student, coworker, or friend needs more than your general feeling. They need evidence.

The most reliable pattern is:

Observation + effect + next step.

Observation: what you see or hear.

Effect: what it does to the reader, listener, customer, teammate, or situation.

Next step: what to keep, repeat, adjust, cut, add, or check.

Common traps

Trap 1: Praise with no evidence. "Great work" feels good for five seconds, then disappears.

Trap 2: Criticism with no direction. "This needs work" may be true, but it does not tell anyone where to start.

Trap 3: Personal taste pretending to be feedback. "I don't like it" is less useful than "The informal tone may not fit this client."

Trap 4: Too many comments at once. Ten suggestions can make the listener freeze. Choose the most important one or two.

Trap 5: Fixing it yourself. Rewriting everything may be faster, but the other person learns less.

Better phrases

For praise:

  • "The opening example works well because it gives the reader a real situation right away."
  • "Your answer is strong because each reason has evidence."
  • "The chart is easy to read. The labels are short, and the colors are clear."
  • "This email has a good tone: polite, direct, and not too stiff."

For criticism:

  • "The main idea is clear, but the second paragraph repeats the first. You can cut it or add a new point."
  • "The report has useful data, but the conclusion does not explain what the team should do next."
  • "The design is clean, but the button is hard to find. Making it darker would help."
  • "The answer starts well, but it needs one example to support the claim."

For mixed feedback:

  • "Keep the structure. Revise the examples."
  • "The tone works. The length is the issue."
  • "The content is useful. The order needs adjusting."
  • "The first half is strong. The ending needs a clearer next step."

These phrases are still short. The difference is that they point.

Wrong / Better / Why

Wrong Better Why
"Good job." "Good job explaining the problem before giving the solution. That order makes the email easy to follow." Names what worked and why it worked.
"Needs work." "The answer needs one example after the main claim so the reader can see your point." Gives a place to start and a next step.
"I don't like the design." "The design may be hard to scan because the headings and body text look similar." Turns taste into an observable issue.
"Make it better." "Make the first sentence more specific by naming the problem and the customer." Defines what "better" means.
"This is confusing." "The timeline is confusing because the dates are not in order. Try listing them from earliest to latest." Explains the source of confusion and how to fix it.

Mini dialogues

A: Is my presentation okay?

B: The structure is strong. You explain the problem, then the solution, then the result. The part to revise is the ending. It stops suddenly, so add one final sentence telling the audience what you want them to remember.

A: So the ending needs a takeaway?

B: Exactly.

A: How was my practice answer?

B: You answered the question directly, which is good. The second reason needs support. Add one example from your own experience or from the passage.

A: Got it. Keep the answer, add evidence.

A: Any thoughts on this design?

B: The colors are calm and professional. The issue is the call-to-action button. It blends into the background, so people may miss it. Could you make it darker or move it higher?

A: That makes sense.

The three-part feedback habit

When you are not sure what to say, build the sentence in three pieces.

1. Observation: "The second paragraph repeats the first."

2. Effect: "That makes the essay feel slower."

3. Next step: "Cut the repeated sentence and use that space for an example."

Together:

"The second paragraph repeats the first, which makes the essay feel slower. Cut the repeated sentence and use that space for an example."

Here are more:

  • "The subject line only says 'Question,' so the teacher may not know what class this is for. Add the course name."
  • "The first example is funny, and it makes the tone friendly. Keep that."
  • "The instructions use three long paragraphs, so users may miss a step. Turn them into bullets."
  • "The apology sounds sincere. The next step is to explain what will change."

When you only have ten seconds

Helpful feedback does not always require a full paragraph. If you are leaving a quick comment on a draft or speaking between meetings, use a tiny version of the same pattern.

  • "Keep this example. It makes the idea concrete."
  • "Cut this sentence. It repeats the line above."
  • "Add a deadline here so the reader knows when to reply."
  • "Move this point earlier. It explains why the topic matters."
  • "Change this word. It sounds more angry than you probably intend."

These comments are short, but they are not vague. Each one tells the person what to keep or change and why. That is the difference between efficient feedback and lazy feedback. Efficient feedback is brief because it is focused. Lazy feedback is brief because it has not done the work.

Quick practice

Turn each vague comment into helpful feedback using observation, effect, and next step.

  1. "Good job."
  2. "This is unclear."
  3. "The email is bad."
  4. "Nice presentation."
  5. "It needs more detail."

Answer key

  1. "Good job using a real example in the opening. It helps the reader understand the problem quickly."
  2. "The second sentence is unclear because it uses 'this' without naming what 'this' means. Replace it with the specific idea."
  3. "The email may sound too abrupt because it starts with the problem before greeting the customer. Add a brief thank-you first."
  4. "Nice presentation. The slides are easy to follow because each one has one main point."
  5. "The answer needs more detail after the first reason. Add one example that shows how the problem affects daily life."

Recap

  • Vague feedback is easy to say but hard to use.
  • Helpful feedback points to evidence.
  • Use observation + effect + next step.
  • Specific praise tells people what to repeat.
  • Specific criticism tells people what to change.
  • One clear next step beats ten scattered comments.

When feedback is specific, it becomes less mysterious and less personal. The listener does not have to wonder what you meant. They can simply improve the work.