The Mintable
Feedback feels weird when it's an event. When you schedule a meeting specifically to give it, put together a careful structure, and deliver it with the formality of a performance hearing — of course the person on the receiving end is on edge. You've signaled that something significant is about to happen.
The managers who are genuinely good at feedback don't treat it as an event. They treat it as a constant, low-stakes flow of information. Good observation, brief note. Missed expectation, quick conversation. Nothing complicated, nothing ceremonial.
Why most managers avoid it
The most common reason feedback doesn't happen isn't lack of skill. It's conflict avoidance dressed up as "waiting for the right moment." The right moment never comes because there is no version of this that feels comfortable before you've had the conversation.
The longer you wait, the bigger the problem gets, and the higher the stakes feel when you finally do say something. A pattern that could have been addressed with one short conversation in week two turns into a formal sit-down in month four. That's the version that actually is weird.
What good feedback actually looks like
Effective feedback is specific, timely, and about behavior — not character. This isn't a new idea, but it's ignored constantly.
Specific means you describe exactly what you observed. Not "your communication could be better" but "in yesterday's meeting you interrupted two people while they were making their point." One of these is something the person can act on. The other is just a vague feeling.
Timely means as close to the event as possible. Feedback about something that happened three weeks ago is much harder to receive because the person's memory of the situation may be different from yours, and they've moved on. Bring it up within a day or two, ideally the same day.
Behavior, not character, means you're not telling someone who they are. You're telling them what you saw them do. "You don't value other people's time" is a character statement. "The project brief was submitted a day late with no heads-up" is a behavior statement. The second one invites a conversation about what happened and how to fix it. The first one invites defensiveness.
The feedback sandwich doesn't work
Most managers were taught to wrap critical feedback in compliments — say something positive, say the hard thing, end with something positive again. The intention is good. The effect isn't.
People have heard this structure enough that they now mentally filter through the positive parts waiting for the "but." The feedback you wanted them to hear gets less attention, not more. And they leave the conversation unsure which part was the real message.
If you have something difficult to say, say it. You can be direct and kind at the same time. "I want to talk to you about how Monday's client call went, because I think there's something worth adjusting for next time" is direct, clear, and not unkind. No sandwich required.
Give positive feedback just as precisely
Generic praise creates skeptics. "Great job this week" lands flat because it could mean anything. "The way you handled that client escalation was exactly right — you stayed calm, got the facts, and proposed a solution before they had to ask for one" is something a person can remember and repeat.
Specific positive feedback tells someone what's working so they can do more of it. It also signals that you're actually paying attention, which makes the harder feedback easier to receive when it comes.
How to make it less awkward over time
The awkwardness is mostly about unfamiliarity. If feedback only comes during reviews or when something goes wrong, it will always feel loaded. If it's a normal part of how you operate, it becomes routine.
The practical move is to build it into existing rhythms. End each 1:1 with a quick observation — something you noticed, something that landed well, something you'd adjust. Keep it brief. Don't make it feel like a ritual. Just make it normal.
Over time, your team will start expecting it. That's when the dynamic shifts from feedback as judgment to feedback as information — something useful, not something to brace for.