15 professionals share their approach to high-trust feedback conversations

Leading with curiosity is a lesson I learned from my sister, an HR consultant, who has saved me multiple times over the years.

Before any tough feedback conversation, I write down 2-3 questions that will help me understand what happened. Feedback can go sideways when I walk in having already decided the outcome — the meeting becomes a verdict delivery instead of a dialogue. Leading with curiosity means I assume a gap in my understanding, not just problem with my team member’s performance.

At WideFoc.us, I’ve been managing creatives, strategists, and community managers for almost 20 years, and the single most reliable trust-protector is showing up ready to listen before I correct.

During the meeting, I open by sharing positive things the employee contributes to the team, then ask about the behavior or mistake in specific, observable terms — not interpretations. I go in assuming positive intent out loud. Something like: “Here’s what we saw, and I’m assuming you had a good reason. Help me understand it before I share my read.” That approach does more work than any other framework I’ve tried. It signals the relationship matters more than the mistake, and it gives the other person room to be honest instead of defensive. From there I ask, I listen, I share my concerns, and we co-author next steps — consequences and corrections. That way, we both leave with the same plan in the same words.

Tough feedback doesn’t benefit from just being nice or just being blunt. We focus on open, honest, and direct communications with the team — but most importantly, we start by being authentically curious. Over the last 18+ years, I’ve become a better leader because this approach has allowed me to slow down, check my emotional response, and lead with respect for our people. Protect the team, challenge the work, and ask before you dictate.

The thing that lands feedback well isn’t the meeting itself. It’s the 24 hours before it. I write down the specific behavior, what changed downstream, and what good would look like. If I can’t fit those three into a paragraph, I’m not ready yet, and the meeting becomes about me venting instead of helping.

Running an RV resort, I once had to tell a long-tenured front desk lead that his check-in pace was costing us guest scores. He’d been doing it the same way for two years. Going in, I’d written down the exact average dwell time at the desk, the three reviews that mentioned it by name, and what “good” looked like — key, cold drink, map, two-minute walk-and-go. I led with what was working, then put those three pieces on the table. He had a fix by the next morning.

The one step I take every single time: open with the future, not the past. “Here’s what I want next month to look like” disarms the room before the hard part. Once that frame is set, the past becomes data, not blame. The conversation stops being about who failed and starts being about what we’re building.

I despise the “feedback sandwich.” It is completely insulting. When you bury a performance issue between two fake compliments, your team stops trusting your praise. Before I walk into a review, I write down the exact problem in one single sentence. Not a paragraph. Just one clear, undeniable fact. If my head of SEO tanked a campaign by ignoring our backlink guidelines, I don’t start by telling him I appreciate his punctuality. I sit down and say, “Your recent link strategy violated our core protocol, and it put our organic traffic at risk.” The band-aid is off. We can actually talk.

The single best step I take during these meetings is physically shifting my position in the room. I refuse to sit across the desk like a judge. I sit right next to them. We look at the monitor together. It immediately changes the psychological dynamic from a personal attack to a joint problem-solving session. If an insurance agent’s policy conversion rates are suddenly slipping, we pull up the lead logs side-by-side. I point to the drop-off and ask them what happened. But I never let them off the hook. You have to be absolutely ruthless on the business standards, but completely supportive of the human trying to meet them.

Setting clear expectations from the start helps to ease defensiveness before it even has a chance to kick in. When someone enters a feedback conversation unexpectedly, their mind is already on high alert, scanning for threats. Every word feels heavier than it should. They’re only half-listening, the other half is focused on self-protection.

So, I make it clear right away: “I’m going to be straightforward in this conversation. You might not like what you hear, but I’m saying this because it’s important for your future.”

That simple statement shifts everything. They stop bracing themselves and start truly listening. Now they understand that what’s coming isn’t an attack; it’s an investment in their growth. My bluntness is seen as a sign of respect, not aggression.

And here’s what I’ve found: when people know to expect a tough conversation, they rise to the occasion. They don’t fall apart; they engage. Some of the most fruitful discussions I’ve had with my direct reports began with this kind of setup and ended with them expressing gratitude for my honesty.

Trust doesn’t shatter when you’re truthful. It breaks when people feel caught off guard or when they sense you’re trying to manage them instead of being upfront. Setting the tone at the beginning is how you ensure you’re on the same side, even when the message is tough to deliver.

Before any tough feedback conversation, I write down specifically what outcome I want for the person, not what behavior I want to stop, but what I actually want for them on the other side of the conversation. That reframe changes how the whole meeting goes. When you walk in clear on what good looks like for them, the conversation feels collaborative rather than corrective, and the person can tell the difference immediately.

The step I take during the meeting that consistently helps: I stop talking after delivering the hard part and let the silence sit. Most people want to fill silence with qualifications and softeners, which dilutes the message. Giving someone 10 or 15 seconds of actual quiet after hearing difficult feedback lets them process without an audience. They almost always respond more thoughtfully than if I kept talking. It’s uncomfortable every single time, which probably means it’s working.

Given that I personally struggled for years with accepting feedback (both positive and negative), I tend to start from my own experience. There were times when I would receive negative feedback or performance reviews and immediately conclude – Yeah, I totally suck at everything.

Of course, that was never the truth, but it took me a lot of self-work to even recognize that pattern.

So, nowadays, I try to do this when I’m about to give tough feedback:

I start by being explicit: “Your job is not at risk.”

The reason I say this upfront is because I don’t want the conversation to trigger a survival (well, fight or flight) response. We work in a very fast paced environment with high expectations, but I don’t believe in operating through fear or uncertainty. I’m not a member of the Lannister family, so using paranoia and fear and what not is not something I’m really comfortable with.

I ask: Do you feel like you always have to be that green dot on Slack?

We’re a fully remote team, and this helps me understand whether there is invisible pressure people put on themselves. I’ve felt that myself, it’s easy to think you always need to look available even when you’re not supposed to be working. When I did that in the past, and didn’t have any boundaries between my work and personal life, both suffered. So I think this is a super relevant question for this situation.

Then I ask them how they are overall, of course, without crossing any lines. Like if they feel like they are overworked or if they just need a little bit of time off because of something – of course I don’t need to know what that something is if they don’t want to share.

If I reaaaally had to pick one thing that makes a real difference, it would be that first step. If you tell someone right away that their job is safe, it completely changes the atmosphere. You can feel the tension drop, literally. People can listen, think, and have a normal conversation about what’s going on, rather than getting defensive or worrying about the worst-case scenarios, which is usually the case.

The step that consistently leads to a better outcome for me is writing down the specific behavior I want to address and then reading it back to myself as if I were the person receiving it. If the note sounds like a character judgment rather than a description of what happened, I rewrite it until it does not. That rewrite is the entire preparation. Everything else follows from it.

At GpuPerHour we are a small team, which means feedback conversations carry more weight because there is nowhere to hide. If an engineer’s code reviews have been getting sloppy, I cannot say “your code reviews need to be better.” That sounds like I am telling them they are bad at their job. What I can say is “in the last three PRs I noticed the review comments were shorter and the merge happened before the CI run finished, and I want to understand what is going on.” That framing protects trust because it describes an observable pattern and opens a door instead of delivering a verdict.

The other thing I do before every tough feedback conversation is ask myself whether I have given this person enough positive, specific recognition recently that they have context for how I see their overall contribution. If I have not, I do not lead with the tough feedback. I lead with the recognition first, in a separate conversation, on a separate day. Tough feedback lands differently when the person already knows you see their value. If the only time you give detailed feedback is when something is wrong, every feedback conversation becomes a stress event.

During the meeting itself, I ask one question before I say anything critical. “How do you feel about how the last few weeks have gone?” About half the time, the person names the exact issue I was going to raise. When that happens, the conversation shifts from me delivering feedback to us solving a problem together, and the trust impact is completely different.

I like to pull up the person’s last three wins and write one clear sentence of their specific behavior that I will address prior to any tough discussion. This is my personal checkpoint to make sure I have the correct sentence written down before scheduling the meeting. The thing I have learned over the years is that not being specific in the feedback is what causes trust to be broken, it’s not the content of the feedback itself. When I am able to go into the conversation with both pieces of information, the positive recognition along with the specific behavior that I want to address, it creates a grounded base for the feedback to take place. When individuals have been recognized for what they contribute, being given hard feedback is heard differently than not. This creates a shift in the conversation from an uncomfortable experience to a productive experience.

I also do not skip the habit of sending a short heads-up message 24 hours before the meeting. Lots of managers walk into tough conversations cold and expect the person receiving the feedback to emotionally keep up with them; that almost never happens. By giving the person 24 hours to process the feedback, it enables the person receiving the feedback to be prepared for the conversation and to have their own thoughts started upon arrival, which helps move through the conversation more quickly. In my experience, the focus of the meeting is about determining next steps together, which is where the real progress takes place, instead of delivering the news.

Delivering tough feedback to a direct report requires strategy, especially in today’s landscape. Most feedback sessions revolve around praise, then criticism, and finally end with praise again. But it no longer works, as this does not directly solve the issue.

That is why I ask myself a whole lot of questions before I schedule the meeting. First, I check for any bias, for instance, I will ask myself if the question being asked revolves around business outcomes or whether it is about personality or their style of work. If it falls into the latter category, I know it is preference and not performance.

Then I will get specific examples. Telling someone that they need to be more active or work faster is vague, and it only breaks trust. Instead, I will use specific examples of what the issue is. I feel this creates a map of where, when, and how.

From the examples that I have gathered, I will create a support plan. I am a firm believer that all tough feedback should be accompanied by a solution. Not just stating that they have our full support, but explaining how we will support them.

A step I take during the meeting is to allow them to give feedback while in the meeting. I want to make it clear that this is not a one-sided conversation, and everything has 2 sides. I believe that trust is only protected when everyone is given a fair opportunity to share their perspective, even if the news is bad.

Trust is not something that is built by avoiding truth; the only way to build it is through open and honest feedback where there is an intent to support the individual.

Pinpoint the exact moment the trust gap started. My strategy is simple; go beyond the performance issue and identify the exact moment trust started to slip. This ensures that I go into the conversation focused on how the issue has shaped team perception and reliability, framing it as a credibility gap rather than a one-off error.

During the discussion, I shift the focus from blame to rebuilding trust. I make it clear what pattern needs to change and what actions will restore confidence. That reframing helps people see feedback as an opportunity to strengthen their reputation, which leads to more honest and productive outcomes.

Tough news can activate the fight-or-flight response in employees. Beginning requests by requesting such permission decreases physiological signs of defensiveness by 30% in these very specific conversations, resulting in more productive encounters.

You surrender control to them when you ask if it is an okay time to deliver feedback. Such an opening works well. It’s a signal that I care about their headspace so much that I won’t proceed without permission.

This makes all the difference. This was one of the reasons we had a 15% drop in output early on. In fact, as it turns out, people accept the solution more quickly when they first accept the feedback.

Relations are maintained when they feel they have the option to speak. I wait for their verbal agreement. It increases the connection and keeps the meeting participatory for all parties. That’s when the magic happens.

Open communication should be the key here. Before the call, give the employee a brief email explaining the why behind the call, and also highlight the main pain points to be discussed. It’s important that the managers emphasize how this conversation is only to help employees succeed and support them better. There is no other intention or backlash they might face.

The managers should make sure the employee is aware that the conversation is confidential and would not be discussed with anyone else. Give employees proper time to prepare and encourage them to come with questions and any concerns or roadblocks they’re facing that is affecting their job performance.

I think it is important to consistently practice radical candor, not just when things get tough. That way, you create a culture of honesty being the kindest thing you have to offer, and uncomfortable conversations naturally become part of this practice and are less uncomfortable as a result because everyone knows that they won’t have a long-term detrimental effect on your professional relationship with each other. Not having these conversations is actually the worst thing to do, and I believe it is important and kind to cultivate this approach to allow people to grow and improve.