Feedback    Ugh!

Picture the scene. It’s annual review season. You sit in a glass meeting room while your manager scrolls through a template, delivering “balanced feedback” that feels anything but. Or worse, you receive a blunt Slack message—“This isn’t quite right”—with no context, no tone, and no clue what to do next. We’re told we work in feedback-rich cultures, yet most people still brace themselves when they hear the word.

That’s the paradox. Organisations invest heavily in feedback frameworks, yet employees continue to find the experience awkward, unhelpful, or quietly demoralising. According to Gallup, only a small proportion of employees strongly agree that the feedback they receive actually helps them improve. Meanwhile, research from Harvard Business Review suggests that poorly delivered feedback can actively reduce performance rather than enhance it.

The problem isn’t just what we say. It’s how, when and why we say it. In hybrid workplaces, where tone is flattened across screens and conversations happen asynchronously, feedback can easily lose nuance. Add to that the growing emphasis on psychological safety, now treated as a measurable driver of team performance, and the stakes are higher than ever.

So, this could be a good time to rethink the whole exercise. Feedback is no longer a formal, top-down event. It’s a continuous exchange, happening in meetings, messages and quick follow-ups. The smartest organisations are shifting from evaluation to iteration, and from judgement to shared problem-solving.

This article sets out three practical ways to give feedback and three equally important ways to receive it. The aim is simple. Treat feedback not as a verdict on who you are, but as useful data on what you or the person you feedback to could do next.

PART I: How to Give Constructive Feedback

Method 1: Shift from ‘Critique’ to ‘Co-Design’

Most feedback still sounds like a verdict. “This isn’t clear” or “You missed the point” shuts people down fast. A smarter approach is to turn critique into co-design, where the goal is improvement, not judgement.

In practice, that means swapping fault-finding for forward motion. Instead of “Your presentation lacked clarity”, try “What if we framed this around three key takeaways so the audience can follow it more easily?” The difference is subtle but powerful. You are inviting someone to build with you, not defend themselves.

This shift reflects how modern teams actually work. Agile and design thinking models, widely discussed by IDEO (a human-centred design firm that uses a design thinking approach to solve complex problems and innovate products, services and spaces) emphasise iteration and shared ownership. The best feedback now asks better questions. “What would make this stronger?” is far more useful than “What went wrong?”.

Method 2: Use ‘Micro-Feedback’ in Real Time

Annual reviews are far too late. By then, the moment has passed and the detail has faded. Micro-feedback fixes that by making feedback immediate, bite-sized and routine. Think less speech, more signal.

In practice, it’s a quick message after a meeting or a short comment on a draft. “That opening slide worked really well, clear and engaging.” Or, “Quick thought, tightening that email could make it more persuasive.” No drama, no build-up, just useful input while it still matters.

This approach reflects the shift towards continuous performance management, highlighted by Deloitte, where frequent, informal feedback replaces rigid review cycles. It works particularly well in remote teams, where silence can be mistaken for approval. Regular, low-stakes feedback normalises improvement and removes the anxiety that comes with saving everything for one big conversation.

Method 3: Anchor Feedback in Impact, Not Opinion

Most feedback fails because it sounds like personal opinion dressed up as fact. “I didn’t like it” or “It wasn’t strong enough” invites argument, not improvement. A sharper approach is to focus on observable impact.

Try structuring feedback in three parts. Start with what you saw. Explain what happened as a result. Then ask a forward-looking question. For example, “In the meeting, your point was raised briefly, but the discussion moved on quickly. That meant it didn’t get full attention. How could we make sure it lands next time?”

This method reduces defensiveness because it removes guesswork. Research discussed by Center for Creative Leadership shows that behaviour-based feedback is more likely to drive change. It shifts the conversation from judgement to problem-solving, which is where real progress happens.

PART II: How to Receive Feedback Constructively

Method 4: Treat Feedback as ‘Raw Data,’ Not Truth

Think of feedback less as a verdict and more as incoming data. It’s filtered through someone else’s mood, priorities and blind spots. A manager saying “you lack leadership presence” isn’t delivering gospel; it’s one perspective. The smart move is to interrogate it. Ask yourself, “What part of this is actually actionable?” For instance, if a client says your presentation felt “flat”, that may translate into a practical tweak such as stronger storytelling or clearer visuals.

This approach reflects modern, data-driven thinking, where signals are tested rather than swallowed whole. It also creates distance between you and the critique, reducing defensiveness and helping you improve with precision rather than ego.

Method 5: Respond with Curiosity, Not Defence

Your first reaction to feedback is the hinge on which everything turns. Snap back defensively and you shut the conversation down. Pause, even for a few seconds, and you create space to learn. The trick is to replace instinctive resistance with genuine curiosity.

Instead of arguing, ask sharper questions. “Can you give me a specific example?” or “What would ‘better’ look like in practice?” turns vague criticism into something usable. If a colleague says you dominate meetings, probe further. Do they mean interrupting, or not inviting input? The answer can then shape your response.

This reflects the coaching cultures now common in high-performing organisations, where feedback is a dialogue rather than a verdict. Curiosity signals confidence, not weakness, and transforms critique into collaboration.

Method 6: Close the Loop—Show What You Did With It

Most people nod at feedback, then quietly do nothing. That’s where feedback cultures die. The real skill is closing the loop and making your response visible. If a manager suggests tighter emails, don’t just agree. A week later, say, “I tried shortening my updates. Does this hit the mark?”

This simple follow-up signals that feedback led somewhere. It also sharpens future input. Colleagues are far more likely to invest effort when they see results rather than silence. For example, a product lead who shares revised prototypes after critique turns feedback into momentum, not memory.

In fast-moving teams, this builds trust quickly. It shows you are not just receptive, but responsive. Without that loop, feedback feels like it disappears into a void, and people stop bothering.

Feedback as a Competitive Advantage

Organisations that truly master feedback do not just improve performance, they accelerate learning at every level. That is the real edge. Constructive feedback is not about being endlessly nice or brutally critical. It is about being clear, timely and focused on growth, even when that feels uncomfortable.

The difference shows up in everyday moments. A team that addresses issues quickly will adapt faster than one that tiptoes around them. A leader who invites challenge will outperform one who avoids it. Over time, those small habits compound into serious advantage.

In modern business, success belongs to those who learn faster than their competitors, not those who pretend to get everything right first time. Feedback is not a soft skill, it is a system, and the best professionals know how to work it from both sides.

And what about you…?   

•  When receiving feedback, do I tend to become defensive, or do I pause and explore what might be useful in it?

•  When giving feedback, am I prioritising clarity and growth, or simply trying to be “nice” and avoid discomfort?