The Art of Giving Feedback Without Creating Fear

A practical look at how trust, psychological safety, and consistent support turn feedback from a source of anxiety into a shared tool for growth.

The Art of Giving Feedback Without Creating Fear
Sandeep Varma
8 min readFeb 6, 2026
The Art of Giving Feedback Without Creating Fear
Photo by Sandeep Varma on EMDock

Feedback is one of the most talked about responsibilities of an engineering manager, and also one of the most misunderstood. Many managers intellectually understand that feedback is important, yet still struggle with when to give it, how to give it, and why it so often feels tense for both sides.

What makes feedback difficult is not usually the message itself. It is the context in which that message is delivered. Feedback does not exist in isolation. It lives inside a relationship, inside a power dynamic, and inside a history of past interactions. When those elements are ignored, even well intentioned feedback can create fear, defensiveness, or disengagement.

This post is about reframing feedback as a long term partnership rather than a moment in time. When done well, feedback reduces tension instead of creating it, and builds trust instead of eroding it.


Why Feedback Feels So Tense

For many engineers, feedback is associated with performance reviews, promotion cycles, or moments where something has already gone wrong. Over time, this conditions people to hear feedback as a signal of danger rather than growth.

Tension often comes from surprise. When feedback shows up without warning, especially if it is corrective, the brain immediately shifts into self protection mode. Instead of listening, people start defending. Instead of reflecting, they start explaining. This is not a character flaw. It is a natural response to uncertainty and perceived risk.

Another source of tension is vagueness. Feedback that lacks concrete examples or clear intent leaves too much room for interpretation. When people are forced to guess what you really mean, they often assume the worst. Ambiguity amplifies fear far more than clarity ever will.

Finally, tension increases when feedback feels one directional. If feedback only flows downward, or only appears when something is wrong, it begins to feel less like support and more like judgment.


The Hidden Cost of Treating Feedback as an Event

One of the biggest mistakes managers make is treating feedback as a discrete event. Something that is delivered, acknowledged, and then moved on from. This framing unintentionally turns feedback into a report card.

When feedback is delivered this way, the implicit message is that the responsibility now fully sits with the individual. They received the input. They are expected to fix it. The manager moves on.

This creates distance rather than alignment. It also reinforces the idea that feedback is about evaluation rather than development. Over time, people stop being curious about feedback and start being cautious around it.

Feedback should not feel like a verdict. It should feel like an ongoing conversation.


What Actually Creates Tension in Feedback

Tension is rarely created by honesty alone. It is created by how honesty is introduced and supported.

Feedback creates tension when it is delayed until frustration has built up. By the time it is delivered, the emotional weight is already high. Even neutral wording can feel charged because the underlying energy has been accumulating silently.

Tension also shows up when feedback feels personal rather than behavioral. When the focus shifts from specific actions to perceived traits, people feel attacked rather than guided. This makes growth feel threatening instead of achievable.

Another major contributor is inconsistency. If expectations are unclear, or if standards feel like they shift depending on the situation, feedback feels arbitrary. People struggle most when they do not know what success actually looks like.


How to Reduce Tension Before Feedback Ever Happens

The most effective feedback is rarely about the moment it is delivered. It is about the environment you have already created.

Setting expectations early is one of the simplest and most powerful ways to reduce tension. When people know what good looks like, feedback becomes a calibration conversation rather than a correction.

Regular feedback also matters. When feedback is continuous and balanced, it loses its shock value. Positive reinforcement and constructive input should coexist naturally. This signals that feedback is about growth, not fault finding.

Anchoring feedback in observable behavior further reduces defensiveness. Concrete examples ground the conversation in reality and remove the need for interpretation. People may still disagree, but they are no longer guessing what you are referring to.


Psychological Safety Is Not Optional

Feedback only works when people feel safe enough to hear it.

Psychological safety is the belief that you can speak, try, fail, and learn without being punished or abandoned. Without this foundation, feedback becomes performative. People nod, agree, and then quietly disengage.

One critical but often overlooked aspect of psychological safety is reassurance of partnership. Your team needs to know that feedback is not a handoff. It is not you pointing out a gap and walking away. It is you saying that you are in this together.

This means explicitly communicating that growth is a shared responsibility. When you give feedback, you are not just identifying an issue. You are committing to support, guidance, and follow through. That commitment changes how feedback is received.

Standing by your team does not mean lowering standards. It means making it clear that standards exist alongside support, not instead of it.


Feedback as Collaboration, Not Correction

The most effective feedback conversations feel collaborative rather than corrective.

Instead of positioning yourself as the evaluator, position yourself as a thinking partner. Invite reflection rather than forcing agreement. Ask how the individual sees the situation before explaining your perspective.

This approach does not dilute accountability. In fact, it often increases it. When people feel respected and involved, they are more likely to take ownership rather than comply superficially.

Collaboration also means following up. Feedback should evolve over time, with check ins that reinforce progress and recalibrate direction. This reinforces the idea that feedback is a process, not a judgment.


When Feedback Becomes a Trust Multiplier

Over time, consistent and supportive feedback becomes one of the strongest trust builders you have as a manager.

When people see that feedback is fair, predictable, and rooted in care, they stop bracing for it. They start seeking it out. At that point, feedback shifts from something you deliver to something you exchange.

This is where teams grow fastest. Not because mistakes disappear, but because learning accelerates.


Final Thoughts

Feedback is never just about words. It is about relationship, safety, and intent.

If feedback feels tense, the answer is rarely to soften the message. More often, the answer is to strengthen the foundation. Trust built outside the feedback conversation determines how feedback lands inside it.

When people know you are with them in the journey, feedback stops feeling like a threat and starts feeling like support.

That is when feedback does what it is meant to do.


If you are an engineering manager, I would love to hear how you think about feedback. What has reduced tension on your team, and what has unintentionally increased it?

Enjoyed this post?

Comments

Loading comments...

Please log in to post a comment.

About the author

I write about leadership and software engineering through the lens of someone who’s worked as a software engineer, product owner, and engineering manager. With a Bachelor’s in Computer Science Engineering and an MBA in IT Strategy, I bring together deep technical foundations and strategic thinking. My work is for engineers and digital tech professionals who want to better understand how software systems work, how teams scale, and how to grow into thoughtful, effective leaders.

View full profile →
Continue reading
← Previous
Monoliths vs Microservices Without the Buzzwords

A Practical Story of How Backend Systems Grow Over Time

Next →
Should EMs Code? A Balanced Perspective

An experience-driven argument for why writing production code often feels right in the short term, but quietly undermines the real responsibilities and long-term impact of engineering management.

Related posts
Building a Culture Where Teams Truly Stick Together
Building a Culture Where Teams Truly Stick Together

A practical look at turning siloed groups into teams that genuinely support each other.