The conversation seemed to go well.

The manager explained the problem. The employee listened carefully, nodded several times, and said they understood. There was no argument. No defensiveness. No uncomfortable confrontation. The meeting ended with a handshake, a smile, and what appeared to be complete agreement.

Two weeks later, nothing had changed.

The same deadlines were being missed. The same communication problems continued. The same behavior showed up in another meeting. The manager became frustrated and began wondering whether the employee cared enough to improve.

But the employee left the original conversation with a very different understanding.

They knew the manager was concerned, but they were not entirely sure what they had done wrong. The examples were vague. The expectations were unclear. The manager had softened the message so much that the employee assumed the issue was minor. They nodded because they wanted the conversation to go well, not because they knew exactly what needed to change.

The manager delivered feedback.

The feedback never landed.

There is a difference.

Managers often judge feedback by whether they said what they intended to say. They prepare for the conversation, work up the courage to address the issue, explain their concerns, and feel relieved when it is over. From their perspective, the responsibility has been fulfilled.

But feedback is not successful because the manager delivered it.

Feedback is successful when the other person understands what happened, recognizes why it matters, and leaves knowing what to do differently.

That distinction matters because feedback is one of the most important tools a manager has. Used well, it can improve performance, build confidence, strengthen relationships, and accelerate someone’s career. Used poorly, it creates confusion, defensiveness, resentment, or embarrassment. Avoided entirely, it allows small problems to become habits.

And habits become reputations.

The Feedback You Avoid May Be the Feedback Someone Needs Most

Most managers do not enjoy giving difficult feedback.

They worry about hurting someone’s feelings. They do not want to damage the relationship or create tension. They tell themselves the issue is not serious enough yet. They hope the employee will recognize the problem and correct it without an uncomfortable conversation.

So they wait.

They drop hints.

They make general comments during team meetings.

They send reminders to everyone instead of speaking directly to the one person who needs the feedback.

Meanwhile, the employee continues doing something that may be limiting their performance, damaging relationships, or quietly affecting how others perceive them.

Avoiding the conversation may feel kind in the moment, but withholding useful feedback is rarely kind in the long run.

Imagine that an employee regularly interrupts coworkers during meetings. Their manager notices it. Their peers notice it. People become frustrated and begin avoiding conversations with them. The behavior may eventually affect the employee’s reputation and limit future opportunities.

But nobody tells them.

Months later, the employee receives a disappointing performance review and hears that collaboration has become a concern.

From the employee’s perspective, the criticism came out of nowhere.

From the manager’s perspective, the problem had been obvious for months.

That is not fair feedback.

If something is important enough to affect an employee’s performance review, compensation, reputation, promotion opportunities, or future with the organization, it is important enough to discuss while they still have time to improve it.

Great managers do not save feedback for annual reviews.

They coach while the information is still useful.

Care Personally. Challenge Directly.

Kim Scott, author of Radical Candor, built her approach to feedback around two responsibilities:

“Care personally. Challenge directly.”

Managers often become comfortable with one and neglect the other.

Some managers care deeply about their people but avoid difficult conversations. They want to encourage employees, preserve relationships, and maintain harmony. When a problem appears, they soften the message until the employee cannot tell that anything really needs to change.

The manager may say:

"You’re doing a great job. There are just a few little things we may want to work on eventually."

The employee hears:

"I’m doing a great job."

Other managers are comfortable challenging people but forget the human being receiving the message. They are direct, but their feedback feels cold, personal, or unnecessarily harsh. They may identify the problem accurately while delivering the message in a way that creates embarrassment instead of growth.

Great managers learn to do both.

They care enough about people to tell them the truth, and they respect people enough to tell them clearly.

One of the stories that helped shape Scott’s thinking came from her time at Google. After she delivered a successful presentation, Sheryl Sandberg praised what had gone well and then pointed out that Scott repeatedly said “um” while speaking. Scott initially dismissed the feedback as unimportant.

Sandberg tried again.

She explained that the habit weakened Scott’s presentation and offered to connect her with a speaking coach. Scott still brushed it aside. Eventually, Sandberg became much more direct and made it clear that the verbal habit was affecting how intelligent Scott sounded.

That finally landed.

The lesson is not that managers should insult employees or become harsh when feedback is ignored. The lesson is that Sandberg cared enough about Scott’s future not to allow her to dismiss something that could limit her effectiveness. Vague language would have been more comfortable, but it would not have helped.

Sometimes clarity is kindness.

Describe What Happened, Not Who You Think They Are

Feedback becomes difficult to receive when managers turn a behavior into a judgment about someone’s character.

Consider the difference:

"You’re unreliable."

That is a label.

The employee may immediately begin searching for evidence that the manager is wrong. They remember the projects they completed successfully, the evenings they worked late, and the times they helped coworkers. The conversation becomes a debate about identity.

Now consider this:

"The last two reports were submitted after the agreed deadline. When that happens, finance cannot complete its review on time, and the customer update gets delayed."

That is observable.

The manager identified the behavior and explained its impact without pretending to know the employee’s motives.

The employee may have a legitimate explanation. Perhaps priorities changed. Perhaps another department failed to provide necessary information. Perhaps the workload is unrealistic. Asking for the employee’s perspective may reveal context the manager needs to understand.

But the conversation now has something concrete to work with.

Useful feedback focuses on behavior because behavior can change.

Labels create defensiveness.

Specific examples create clarity.

Explain Why It Matters

Managers sometimes assume the impact of a behavior is obvious.

It usually is not.

An employee may know they submitted a report late but have no idea that the delay affected three other departments. Someone may not realize that checking their phone during a customer meeting appears dismissive. A team member may believe their blunt communication style is efficient without recognizing that coworkers have stopped bringing them ideas.

Connecting behavior to impact gives feedback meaning.

Instead of:

"You need to communicate better."

Try:

"When the project timeline changed and the team did not hear about it until Friday, two people continued working from the old schedule. Going forward, I need you to communicate timeline changes as soon as they are approved."

Now the employee understands what happened, why it mattered, and what success looks like next time.

That is feedback someone can use.

Make It a Conversation

Feedback should not feel like a courtroom where the manager presents evidence and announces a verdict.

After describing what you observed and explaining its impact, ask for the employee’s perspective.

"How did you see the situation?"

"What was happening from your point of view?"

"Is there something I may be missing?"

"What obstacles made this difficult?"

You may learn something that changes your understanding.

The employee may also need a moment to process what they are hearing. A thoughtful manager creates room for that without abandoning the message.

Listening does not mean the original concern disappears. It means the manager is willing to understand before deciding what happens next.

Feedback works best when it is something you work through with someone, not something you do to them.

Stop Hiding Criticism Inside a Sandwich

For years, managers were taught to use the feedback sandwich:

Start with praise.

Insert criticism.

Finish with more praise.

The intention was good. Managers wanted difficult feedback to feel easier to receive.

The problem is that employees learn the pattern.

The moment the manager says, “You’ve been doing such a great job,” the employee braces for the sentence that begins with “but.”

Even worse, the important message can become buried between compliments. The manager leaves believing the concern was clearly addressed. The employee leaves remembering the praise.

Praise should be genuine, specific, and frequent. It should not be bread used to disguise difficult feedback.

When correction is needed, be respectful and clear.

You can care about someone without confusing them.

Positive Feedback Should Teach, Too

Feedback is not only for correcting problems.

Some of the most valuable feedback tells people what they did well and why they should repeat it.

"Great job" feels good, but it provides very little information.

Compare it with:

"The way you summarized the customer’s concern before offering a solution changed the tone of that conversation. The customer felt heard, and that made the problem easier to solve. Keep doing that."

Now the employee knows what behavior created the positive result.

Specific praise reinforces performance.

It also shows people that their work is being noticed.

Managers often assume high performers know they are doing well. Then they spend most of their coaching time addressing problems and very little time reinforcing excellence. Over time, their strongest employees may hear far more about what needs improvement than what makes them valuable.

Catch people doing things right.

Then tell them exactly what they did and why it mattered.

Feedback Is Not Finished When the Conversation Ends

One of the most common reasons feedback fails is that nobody defines what happens next.

The manager explains the concern.

The employee agrees.

Everyone returns to work.

Then both people wait.

The manager watches for improvement but says nothing. The employee makes a few changes but is unsure whether they are enough. Weeks later, the manager becomes frustrated because progress has been inconsistent.

Good feedback ends with clarity.

What should change?

What does success look like?

What support is needed?

When will you follow up?

A feedback conversation about missed deadlines might end this way:

"Going forward, I need the report submitted by noon every Thursday. If something may prevent that, let me know by Tuesday so we have time to adjust. Let’s check in two weeks from now and talk about how the new process is working."

Now everyone knows what is expected.

The follow-up matters because feedback without follow-up can feel like criticism.

Feedback with support becomes coaching.

A Simple Way to Make Feedback CLEAR

When you need to give feedback, use this approach:

• C: Choose the right moment. Give feedback while it is still relevant, but avoid delivering it when emotions are running high.
• L: Lead with observable behavior. Explain what happened without assigning motives or labeling the person.
• E: Explain the impact. Help the employee understand why the behavior matters to the team, customer, organization, or their own growth.
• A: Ask for their perspective. Listen for context you may not know and make the feedback a conversation.
• R: Reinforce the next step. Agree on what will change, what support is needed, and when you will follow up.

The framework is simple because feedback should create clarity, not complexity.

What Have You Been Hoping They Would Figure Out?

Think about the people you lead.

Is someone struggling with a behavior you have never clearly addressed?

Is there a high performer with a blind spot that could limit their future?

Is someone doing excellent work without hearing specifically what makes their contribution valuable?

Is there a conversation you have postponed because you are waiting for the perfect moment?

Your willingness to give useful feedback determines how quickly the people around you can grow.

Avoiding feedback may preserve comfort today, but it can quietly limit someone’s future. Delivering feedback poorly creates defensiveness. Delivering it clearly, respectfully, and with genuine investment can improve performance, strengthen trust, and change the trajectory of a career.

The best managers do not tell people only what they want to hear.

They tell people what they need to know, in a way that helps them become better.

So here is the question for this week:

What have you been hoping someone on your team would figure out on their own?

Maybe it is time to stop hoping.

Maybe it is time to help.
​
Onward!
​
The Boundless Team