Most feedback fails before the other person has a chance to use it.
It is too vague.
"Be more proactive."
"Communicate better."
"Show more leadership."
"Be more polished."
The person leaves knowing that something is wrong but not knowing what behaviour should change.
If you want to know how to give feedback at work, make the feedback specific enough to become an action.
Good feedback turns an impression into something a person can see, test and improve.
Use Specific, Impact, Alternative, Next Time
A simple feedback structure has four parts.
1. Specific
Name the behaviour or moment.
Not:
"Your communication is confusing."
Try:
"In the steering meeting, you spent the first seven minutes walking through the background before giving the recommendation."
Specific feedback gives the other person somewhere to look.
2. Impact
Explain why the behaviour matters.
"The group started debating details before they understood what decision you wanted."
Now the person knows why you are raising it.
Impact is not a moral judgement.
It is the consequence of the behaviour in that context.
3. Alternative
Offer a more useful behaviour.
"Next time, lead with the recommendation and the decision you need. Then use the background to support it."
This is the bridge many feedback conversations miss.
People are told what not to do without being shown a better option.
4. Next Time
Anchor the feedback to the next opportunity.
"You have the commercial review on Thursday. Try it there and see whether the discussion stays closer to the decision."
Feedback becomes more useful when it points forward.
Feedback should describe behaviour, not identity
Compare:
"You are not confident enough."
with:
"When you presented the forecast, you gave the recommendation and then immediately softened it three times with 'maybe' and 'I am not sure.'"
The first statement asks the person to become a different kind of person.
The second gives them something they can practise.
Identity language often creates defensiveness because it sounds permanent.
Behaviour can change.
Give examples while they are still useful
If you wait three months, the person may barely remember the meeting.
Timely feedback is easier to connect to a real moment.
You do not need to interrupt every mistake immediately.
But avoid saving routine feedback for a formal review simply because the calendar says feedback happens then.
When the moment is fresh, the lesson is easier to see.
Ask whether feedback is wanted when the context is informal
Some situations require feedback because you are responsible for the work.
Others are optional.
If a colleague gives a presentation and you have an observation, you can ask:
"Would it be useful if I gave you one thing I noticed?"
That small question changes the interaction.
They know what is coming.
They can say yes.
And you avoid turning every conversation into unsolicited coaching.
Do not overload the person
A page of feedback can feel thorough to the giver and useless to the receiver.
Choose the change that would make the biggest difference.
Suppose a presentation had six minor problems but one major one: nobody understood the recommendation until slide twelve.
Start there.
One useful change applied is worth more than twelve observations forgotten.
Positive feedback should be specific too
"Great job" feels good.
Specific positive feedback teaches.
For example:
"The way you opened with the decision and then gave only the two numbers supporting it made that update much easier to follow."
Now the person knows what to repeat.
Positive feedback is not only encouragement.
It can be instruction.
Distinguish standards from preferences
Not every difference is a performance problem.
You may prefer short emails.
Someone else may write longer ones.
The question is whether the difference affects an agreed standard, an outcome or another person's ability to work.
Before giving feedback, ask:
Is this about effectiveness, or is it about my personal preference?
Both can be discussed.
They should not be presented as the same thing.
Use questions when you do not know the cause
Suppose someone's work has become slower.
You could say:
"You need to manage your time better."
Or you could say:
"I have noticed the last three analyses have taken longer than the earlier ones. What is making them harder to complete?"
The second approach gathers information before prescribing a solution.
Maybe the data changed.
Maybe the brief is unclear.
Maybe workload increased.
Feedback improves when diagnosis comes before advice.
A feedback conversation can be short
Useful feedback does not need a formal meeting.
"One thing from that client call. When they challenged the price, you answered immediately. I think we would have learned more if you had first asked what they were comparing it with. Try one question before defending the price next time."
That may take thirty seconds.
Length is not the same as usefulness.
When the feedback is sensitive
For meaningful criticism, privacy usually helps.
Do not correct someone publicly simply because the mistake happened publicly, unless the situation requires an immediate factual correction.
You can fix the work in the room and discuss the behaviour later.
Protecting dignity makes it easier for the person to focus on the message rather than the embarrassment.
Do not hide the point inside a speech
Some people become so worried about sounding harsh that the feedback disappears inside five minutes of reassurance.
"You are doing really well, and everyone likes working with you, and this is tiny, and maybe I am wrong, but there was just one little thing..."
The receiver is now anxious and confused.
You can be warm without becoming vague.
Try:
"Overall the analysis was strong. There is one change that would make the next version more useful."
Then say it.
Make the standard visible
If the person does not know what good looks like, feedback can feel arbitrary.
Show an example.
Share a previous strong version.
Explain the decision rule.
For example:
"For these executive updates, the standard is recommendation first, evidence second, detail only if asked."
Now the person can judge their own work before you do.
When feedback is about repeated behaviour
One instance may need a correction.
A pattern may need a clearer conversation.
Use the same structure, but name the repetition.
"This is the third time the handoff has arrived after the review deadline. The impact is that the next person has to compress their work. From now on, I need a warning at least a day earlier if the deadline is at risk."
Specific.
Impact.
Alternative.
Next time.
Try this today
Think of one piece of feedback you need to give.
Write it in four lines:
Specific: What exactly happened?
Impact: Why did it matter?
Alternative: What would be more useful?
Next Time: Where can they try the change?
Then remove any sentence that describes the person's character rather than their behaviour.
Give the feedback while the example is still recognisable.
What to remember
Feedback is useful when the receiver can do something with it.
Use:
Specific. Impact. Alternative. Next Time.
Describe what happened.
Explain why it mattered.
Offer a better behaviour.
Point to the next opportunity.
Do not aim to sound like a brilliant coach.
Aim to make improvement easier.
