To give and receive feedback at work well, describe a specific situation and behaviour and its impact instead of judging the person, and when you receive it, ask one clarifying question before you reply. That single habit separates people who grow fast in their first job from people who stall.
Most of us were never taught this. You finish your final-year project, you start your internship or first full-time role, and suddenly a manager is telling you your slides are "a bit confusing" or asking why you didn't flag a problem earlier. Nobody handed you a manual. So you either say sorry too fast and learn nothing, or you go quiet and feel attacked. Both waste a chance to get better.
This guide gives you a repeatable way to do it. The same skill shows up in the Critical Core Skills that SkillsFuture maps for the Singapore workforce, where communication and self-management sit alongside problem solving as the abilities employers screen for across roles. You can read the full framework on the SkillsFuture Critical Core Skills page.
Why feedback feels harder than it should
Feedback triggers a quick threat response. When someone points out a gap, part of your brain reads it as a hit to your status, especially when you are 22, new, and trying to prove you belong. That reaction is normal. The problem is that acting on the reaction, getting defensive or shutting down, is what makes you look junior.
There is also a Singapore-specific layer. Many of us grow up in environments where you do not question a senior, and where saying "I disagree" to a boss feels rude. So people swing to one of two extremes. They either never give upward feedback at all, or they bottle it up until it leaks out as resentment. Neither helps you, and neither helps the team.
The fix is not to become blunt. It is to make feedback small, specific, and frequent, so it stops feeling like a verdict and starts feeling like a normal part of working together. The Tripartite Alliance for Fair and Progressive Employment Practices treats open, respectful workplace communication as part of fair employment, and you can see how that is framed on the TAFEP site.
The SBI framework: situation, behaviour, impact
SBI is the simplest structure for giving feedback that lands. You name the situation, describe the behaviour you actually saw, then explain the impact it had. You leave out judgement of the person and leave out your guess about their intentions.
Here is why each part matters. The situation anchors the feedback to a real moment, so it cannot be brushed off as a vague feeling. The behaviour is something observable, not a label like "careless" or "unprofessional." The impact tells them why it matters, which is the part people usually skip.
| Part | Question it answers | Weak version | SBI version |
|---|---|---|---|
| Situation | When and where? | "You're always late." | "In yesterday's 10am client call..." |
| Behaviour | What did they actually do? | "You weren't prepared." | "...the figures in slide 4 didn't match the email you sent." |
| Impact | What was the result? | "It looked bad." | "...so the client asked us to recheck everything, which pushed the timeline back a week." |
Put together, that becomes: "In yesterday's 10am client call, the figures in slide 4 didn't match the email you sent, so the client asked us to recheck everything, which pushed the timeline back a week." Notice there is no "you always" and no character attack. It is a description a reasonable person can agree with, which means the conversation can move to what to do next instead of arguing about whether it even happened.
A worked example of giving feedback upward
Say your manager keeps assigning you tasks over chat at 7pm with no context, and you are guessing at what they want. Most juniors say nothing and quietly burn out. Here is the SBI version you could actually send or say:
"The last two times tasks came through on chat in the evening, I didn't have the background on who the deliverable was for, so I redid the work the next morning after you explained it. Could we do a quick 5-minute brief when something new comes up? It would save the rework."
That is honest, specific, and it ends with a concrete ask. You are not telling your boss they are a bad manager. You are describing a pattern and proposing a fix. Most reasonable managers respond well to this, because you have made their life easier, not harder.
How to receive feedback without getting defensive
Receiving feedback well is the rarer skill, and the one that gets you noticed. The instinct is to explain, justify, or correct the record the moment someone criticises your work. Resist it. Use this sequence instead.
- Pause before you speak. Two seconds of silence is fine. It stops the defensive sentence that is already forming.
- Ask one clarifying question. "Can you give me an example of where that happened?" This buys you facts and shows you are listening, not bracing.
- Separate the message from the delivery. Your manager might phrase it badly or pick a bad moment. The point underneath can still be true. Take the point, ignore the tone.
- Say what you'll do, instead of only apologising. "Got it. Next time I'll send the draft a day earlier so there's time to review" beats a string of apologies.
- Follow up later. A week on, show the change. Nothing builds trust faster than feedback that visibly stuck.
The trap to avoid is the over-apology. Saying sorry five times feels humble but reads as fragile, and it makes the other person manage your feelings instead of focusing on the work. One clean acknowledgement and a plan is stronger than ten apologies. Learning to hold that composure is part of the wider self-management most fresh grads underrate, and it connects directly to how you improve your communication skills at work.
What to do when the feedback feels unfair
Sometimes the feedback is wrong, or based on a misunderstanding. You still do not win by getting defensive on the spot. Take the same steps: pause, ask a clarifying question, and find out what they actually observed. Often you will discover a real signal underneath, even if the conclusion was off. If after that you genuinely disagree, you can say so calmly with your own situation-behaviour-impact: "I see why it looked that way. From my side, the delay came from waiting on the data, which arrived Thursday." That is a correction, not a defence.
How to ask for feedback so you actually get useful answers
If you wait for feedback to come to you, you mostly get it during formal reviews, which is too late and too vague. Asking for it puts you in control. But "any feedback for me?" almost always gets you "no, all good," because it is too broad and people do not want to seem harsh.
Make the question small and specific instead. The tighter the question, the more honest and useful the answer.
| Instead of asking | Ask this | Why it works |
|---|---|---|
| "Any feedback?" | "What's one thing I could do to make these reports easier to read?" | Names a single behaviour, so it's easy to answer concretely. |
| "How am I doing?" | "If you had to pick one thing for me to improve this month, what would it be?" | Forces a priority instead of a polite summary. |
| "Was that okay?" | "What would have made that presentation a 10 out of 10?" | Reframes criticism as an upgrade, which feels safe to give. |
Ask people other than your manager too. A peer who sits next to you often sees more of your day-to-day habits than your boss does. And ask close to the event, while the details are fresh, rather than three weeks later. Getting into this rhythm early matters most in your first stretch at a company, which is why it overlaps so heavily with how you succeed in your first 90 days at a new job.
Building feedback into a habit, not an event
The people who grow fastest treat feedback as a small weekly loop, not a yearly performance review. Pick one question, ask one person, act on the answer, and show the change. Do that often enough and two things happen. Your work improves, and you build a reputation as someone who is easy to manage and genuinely coachable. In a small Singapore team, that reputation travels fast and it is the kind of thing managers remember when promotions or full-time conversion comes up.
This is also exactly the muscle we build in the FINternship apprenticeship. You get a real mentor giving you direct, specific feedback every week on actual work, which is the fastest way to learn the difference between feedback that helps and feedback that just stings. The Public Service Division frames continuous skills development the same way, treating regular learning as part of the job rather than a one-off, as outlined on the Public Service Division site.
Frequently asked questions
How do I give feedback to someone more senior than me?
Use the same SBI structure, but lead with a specific situation and end with a question or a proposed fix rather than a demand. Keep it about the work and the impact, not about them as a person. Most senior people value junior staff who can flag problems calmly, because it means they hear about issues before they blow up.
What if I get defensive in the moment and only realise later?
It happens to everyone. Go back the next day and say, "I've thought more about what you said, and you're right about the X part. Here's what I'll change." Following up after the fact actually builds more trust than a perfect reaction, because it shows you process feedback seriously instead of just nodding in the room.
How often should I ask for feedback at work?
Roughly once a week is a healthy rhythm for someone new, focused on one specific thing each time rather than a broad "how am I doing." That keeps it low-pressure for the other person and gives you a steady stream of small corrections instead of one big shock at your formal review.
Is it rude to ask for feedback too often in a Singapore workplace?
No, as long as your questions are specific and you act on the answers. Asking "how am I doing" daily gets annoying, but asking one sharp question after a project and then visibly improving signals that you take the work seriously. That reads as initiative, not neediness.
Feedback is a skill you can practise. It is not a fixed personality trait you either have or do not. Start with one SBI sentence and one specific question this week. If you want a structured place to build it with a mentor who gives you that feedback on real work, take a look at the FINternship masterclass or apply to the apprenticeship.