17 leaders share how to give tough performance feedback without losing trust

When a team member is underperforming, the most effective feedback conversations aren’t centered on correction, they’re centered on ownership and relevance.

One approach I often guide leaders toward is this: people are most open to feedback when they both feel the consequence of their actions and can clearly see a benefit they want to achieve.

In practice, this means resisting the urge to immediately “fix” the issue. Instead, I encourage leaders to first help the team member see and articulate the impact themselves. For example, rather than saying, “You need to be more organized,” a more effective starting point is to ask questions to help them uncover challenges they perceive in their work. As an example, “What do you think is causing the disconnect between what’s expected and what’s being delivered?”

This creates space for ownership rather than defensiveness. As a leader, it’s important to recognize that the best feedback comes from their thoughts, not yours.

From there, the conversation shifts to connecting improvement with something the individual actually wants. A simple but powerful framing I’ve seen work is: “If we can solve this, how do you think it will help you in achieving XYZ goal(s)?”

This approach works because it changes the dynamic. Feedback no longer feels like external pressure, it becomes relevant and self-directed. The individual isn’t being “corrected”; they’re being supported in achieving something meaningful to them.

The boundary I often emphasize with leaders is this: don’t carry the weight of the problem more than the person experiencing it. Your role is to guide clarity and alignment, not to absorb responsibility or overcompensate.

Even if their solution isn’t exactly what you would have come up with, their ownership of a 70% effective plan is far more valuable in the long run than your 100% solution. Ownership is what drives follow-through, learning, and growth.

From there, you still have the opportunity to refine and elevate their thinking. Once the problem has been approached collaboratively, you can add input in a way that feels supportive rather than corrective. A simple way to do that is: “That’s a strong direction—would you be open to a couple of ideas that might strengthen it further?”

When someone owns both the consequence and the opportunity, feedback becomes far more productive and morale remains intact because the conversation is rooted in growth, not criticism.

What has worked best for me is making the conversation about the gap, not the person. The phrase I come back to is: “I want to talk about the gap between what the role requires and what I’m seeing right now, because I think that gap can be closed, but we need to be direct about it.” That wording matters because it is candid without being vague, but it also tells the person I am not writing them off. I am addressing performance, not attacking identity.

In my experience, morale drops fastest when feedback feels mysterious, delayed, or personal. People can usually handle hard truth better than they can handle mixed signals. What hurts them is sensing that something is wrong while nobody will say exactly what it is. Because of that, I try to make feedback concrete very quickly. I point to specific patterns, not general disappointment. I do not say, “You need to be more proactive.” I say, “Over the last month, three deadlines slipped without an early warning, and that created cleanup work for other people.” That gives the person something real to respond to.

The other part that makes this work is pairing honesty with a boundary. I try to leave the conversation with a clear improvement path and a clear consequence if the pattern does not change. That protects morale better than false reassurance does, because it replaces anxiety with clarity. A recent version of that sounded like this: “I am not looking for perfection this week. I am looking for two things to change immediately: earlier communication when something is at risk, and clearer ownership of next steps. If that does not improve over the next two weeks, then we need to treat this as a more serious performance issue.”

I think people respect feedback more when they can feel that you are trying to help them succeed, not trying to win the conversation. Tone matters, but precision matters more. Once the person understands exactly what is off, what good looks like, and when you will revisit it, the conversation becomes much less emotional and much more useful.

My advice is to be warm, but not fuzzy. Protect the person’s dignity, but do not protect them from clarity. The best feedback conversations I have had were the ones where the other person walked away knowing, without any doubt, what needed to change and believing that improvement was still possible.

I’ve found that underperformance conversations go wrong when feedback feels like a verdict instead of a shared problem to solve. One approach that’s worked well is separating intent from impact very explicitly, then anchoring the conversation in observable outcomes.

In a prior organization, a team member was bypassing the approval workflow and pushing changes directly to production, which resulted in unapproved content appearing on the official website. This actually happened more than once, which is what made it urgent to address. Rather than framing it as a mistake, I grounded the conversation in intent and impact: ‘I know the goal is to keep things moving quickly. The impact right now is that we’re exposing the business to risk and eroding trust in our release process.’ That made the issue clear without making it personal.

From there, I established a simple rule we stuck to: no approval, no deployment. We agreed on a simple pre-release checklist and a norm of escalating early if timelines were at risk, rather than working around the process. Within weeks, compliance was consistent and there were no repeat issues. More importantly, the tone of the conversation reinforced accountability without creating defensiveness. It felt like tightening the system, not calling out the individual.

The majority of failures to perform well are due to a lack of clarity as opposed to a lack of effort. In other words, people often struggle to meet expectations due to a lack of clarity in the training, communication or priorities; therefore, I try to keep performance feedback connected to the work itself versus who is doing the work. One of the phrases I frequently use is “Let’s go through what success looks like for this role and compare that to the current state of things.” By doing so, we change the nature of the conversation from one of criticism to one of clarity. By using simple tools, such as a role-based task list and/or mobile SOP (standard operating procedure), teams create clarity around what an expectation is and typically see a 20% to 30% increase in completion rates.

Additionally, the interaction between tone and boundary are equally important. I am very straightforward about individual accountability while also providing support. For example, I will say, “I am going to assist you in removing obstacles; however, you need to take responsibility for following through.” Therefore, we also track progress visually (with a simple checklist and/or a weekly completion metric). This type of visibility dramatically changes a person’s behaviour, as they do not perceive the conversation as a personal attack, but rather they appreciate the guidance provided through the directed conversation. Then, morale will be maintained because the focus of the conversation will be on progression versus judgment.

I think that making the conversation about the gap between what I know they are capable of and what I am currently seeing is what holds value, not about what they are doing wrong.

With one team member who was dropping the ball on seller follow-ups, I said something like, “I have seen how good you are when you are locked in, and right now I am not seeing that person.” That framing opens a conversation instead of closing one down.

The boundary I set early is that feedback happens fast and privately. Letting underperformance sit for weeks while hoping it corrects itself is a leadership failure, not a kindness, and I learned that the hard way. The longer you wait, the harder the conversation becomes and the more damage is already done.

Ending every difficult feedback conversation with a specific and agreed next step works for me like an actual measurable thing that we agree on.

Early in my career, I would hold feedback back because I wanted to be respectful, give people space, and address things privately. And that intention was good, but often it backfired. By the time I raised the issue, it carried more weight than it needed to: the correction felt formal.

So now, I try to speak up in the moment, while the context is still fresh and the stakes are still low. That does not mean being blunt or critical in front of others, but it does mean addressing small things as they happen, in a casual and direct way, and then moving on.

One phrase I’ve come back to is, “Let’s tighten that up a bit.” It’s simple, not loaded, and opens the door to a quick adjustment without turning it into a larger conversation than it needs to be. From there, I might add a sentence or two of context, but I keep it grounded in the work, not the person.

The key is tone and timing. You are not delivering a verdict, you are making a small course correction. It’s not always easy, because you are balancing clarity with respect in real time, but it is a skill that can very well be developed; I know because I’ve worked on it myself. And when I succeed — when feedback is immediate and proportionate — it rarely escalates into something bigger, and I wind up keeping both performance and morale on track.

I’ve found that the most effective feedback conversations start with one simple reframe: this isn’t critique, it’s investment.

When I need to address underperformance, I begin with clarity about what success looks like, then create space for the person to reflect on the gap. The phrase that consistently works is: “I’m investing this conversation in your growth because I see your potential.” It shifts the entire dynamic from judgment to partnership.

The boundary I hold is this: feedback is always about the work and the impact, never about the person. I’ve learned through leading teams at Seuss+ that when people feel psychologically safe, they can hear difficult truths and act on them. The goal isn’t to make them feel good in the moment, it’s to help them grow into the leader they’re capable of becoming. That took longer than I expected to admit.

The phrase I come back to is simple: “What’s getting in the way?” When someone is underperforming, my instinct used to be to explain the gap between where they are and where they need to be. But I’ve learned that statements land like verdicts. They put people on the defensive before you’ve even finished the sentence.

Questions do something different. They signal that you’re trying to understand, not just correct. When I ask “What’s getting in the way?” I’m inviting the person into the conversation as a partner rather than positioning myself as a judge handing down a ruling. That shift changes everything about how the feedback is received.

The other boundary I hold is staying focused on one thing. It’s tempting to use a feedback conversation as an opportunity to address every concern you’ve been quietly cataloging. But people can only act on one clear issue at a time. Piling on creates overwhelm, not improvement. I pick the behavior that matters most and stay there.

Candid feedback doesn’t have to feel like an ambush. When you lead with curiosity and keep the scope tight, you create room for the person to actually hear you. That’s when real change becomes possible.

When I need to have a conversation with someone on the team that’s underperforming, I always keep it focused on the work and not the person. I keep it clear and direct, but also constructive.

One way of saying it that’s worked very well for me is saying that I liked “so and so” or “so and so” was done well in this scenario (if there’s reason to say this) and then proceed to say that we’re not there yet. This helps the other person feel like it’s a work in progress and so there’s scope for improvement, vs making it feel like an end goal there’s no going back from, which can be very demotivating.

I also don’t just stop at saying something isn’t working. I make sure that I let the person know that we can work through the stronger version.

Timing is also extremely important. The longer you wait, the heavier the conversation gets and the harder it is to fix the mistake. Early conversations also feel like course correcting instead of criticizing.

A firm boundary that I have in place is that I will not compromise on my expectations and standards just to avoid hard conversations. Standards are non-negotiable, but I’m always around to help meet these and I make sure the team knows that.

Honesty and respect is the best way to manage underperformance. When a team member is not doing well, I don’t complain personally but rather give examples of actions and behaviours that can lead to the expected outcome. For example, “By missing your deadlines, this impairs the chances for everyone else to deliver both safely and on time.” By maintaining this line of thinking, the focus stays on performance not personal failures.

Also, the feedback is paired with some next steps: specific actions to take, avenues of support and timelines for improvement. When delivered with candor and compassion, feedback not only clarifies performance but builds the trust between members of the team.

Simply explaining to them what I’m observing and what needs to be different. There are no conciliations and no filler comments between compliments and compliments. I explain to them specifically what is being produced that does not meet the performance criteria. People can take direct feedback depending on how much they feel the person who provided the feedback wants them to succeed. If there is any perceived vagueness that leaves them guessing, and they then discover after months that they weren’t on solid ground, it lowers their motivation.

Therefore, I split my comments between the performance and the person. The focus of the conversation is always going to be about doing the job correctly and not their value as humans. I stay with giving them examples, illustrations and activities that demonstrate the performance gap. I would never attack someone’s character. Because I have that boundary, we keep things productive rather than defensive.

To be honest, the follow-up and checking to see if anything has changed is more important than the initial conversation. I check within one week after our meeting to determine if anything has changed. If they are even a little better, then I will hold them accountable. Most people perform to the expectation when they know that someone will be watching to see if they have.

It would be phrased best as “let me show you where the gap is, and we can fix it together.” A statement like this is non-accusatory and requests partnership. This is imperative as in clinical settings where underperformance is most commonly the result of a broken process, or a source of confusion, not of ill intent. Addressing the gap as a problem of joint ownership instead of a personal issue provides the most direct form of communication, which is most likely to spur the most positive change, as the individual feels assisted rather than attacked.

The greatest respect to yourself and others is to refrain from giving feedback in the moment. A simple time lapse, like bringing the current task to completion before having the conversation, drastically reduces defensiveness. With this technique, morale is maintained as respect is not lost in the conversation, and in medical aesthetics, preservation of clinical confidence is as important as patient safety.

Been through this many times. I make sure I’m direct about it. I tell them what went down, the problem, and how it needs to be fixed. I keep it concise, I don’t overexplain, nor do I try to soften the blow. Only concrete examples, and then set up some realistic expectations for improvement – how it’s supposed to look, what my deadline is, and how I’ll evaluate it. The formula I go with is “Here’s what you need to improve upon, and here’s how I’m going to evaluate it within the next 30 days.” After that, I hold them accountable. Consistent check-ups, same expectation every time, no moving the goal posts. And at the end of the day, they don’t need to agree. Just make some progress.

Especially with younger employees, my first step in these conversations is to reassure them. People hear they’re having a performance talk with the boss and they panic. Sometimes they’ll just assume they’ve been fired. So, I start by making it clear that they aren’t being fired, and what their performance so far suggests about their next review. From there, we can start talking about solutions. I want my employees to learn and grow, and that can’t happen if all I represent to them is a threat.

Most corporate trainers recommend that negative feedback should be smoothed with involuntary commendations everywhere. Forced compliments just get employees mixed up and postpone the needed changes in behavior. I never sugarcoat the facts and give it an emotional weighting. All you have to do is to make certain inquiries and give a definite time-limit within which the desired results are supposed to be delivered. Direct communication prevents repeat mistakes by 40% in our agency (managers are always afraid that this will appear too rude and cause unnecessary tension). On top of that, we trace performance measurements per week so unexpected interventions are not of any surprise to anyone. This approach assisted our team in doing 150 accounts of clients without any hiccups in the first year.

I will only question my employees about how they will correct the particular mistake immediately without putting any personal blame on it. Clarity is brought immediately to direct questions. This blunt questioning tactic in our marketing agency has reduced repeated errors by 60% after I have at least implemented it in our legal marketing agency. Employees like to be aware of specific actions that they should take. Quick fixes help avoid prolonged periods of downtime and maintain a high morale throughout the production floor. You most often get the quickest time results by removing all the corporate jargon out of it.

The editorial review method I use has evolved into a system for giving constructive feedback. Constructive feedback is difficult to give to employees. The majority of business leaders struggle with providing successful constructive feedback.

Many business leaders are mainly focused on evaluating how poorly an employee performed; therefore, they usually identify failure instead of how/why a particular outcome did not meet expectations. When employees at MKB Media Solutions fail to satisfy their clients’ expectations, the most common reason is that employees were outside of their normal routine and provided subpar products compared to their typical product quality.

In the case of MKB Media Solutions, I take all tasks through the editorial review method as if each task is just one version of a draft needing improvement. I recently requested that my colleague show me evidence that he had skills/knowledge in multiple areas. Using the word “show” creates a distinct separation between behaviors and actions. This creates a small but significant opportunity for applying logic.

Criticism or dissatisfaction with co-workers may appear to be mutually exclusive ideas. However, viewing criticism/dissatisfaction with co-workers as part of a collaborative relationship vs. opposing views will decrease tensions. Business leaders can create workplace cultures that promote converting potentially negative conversations into positive ones by defining language about working as a team.