Receive Critical Feedback About Your Own Manager Behavior

When an employee tells you that your own behavior made their job harder, the first thirty seconds decide whether they ever raise a concern with you again. Most managers want to defend themselves, explain the reasoning behind a decision, or reassure the employee that everything is actually fine. All three responses close the door. The better path is slower, more curious, and more structured, and it protects the trust the conversation is testing.

Why This Conversation Goes Wrong

Hearing feedback about your own behavior triggers a different reaction than hearing feedback about a project or a process. It feels personal, because it is personal. Your instinct is to explain your intent, correct the record, or move quickly to a fix so the discomfort ends. None of that is what the employee needs in the moment.

There is also a power problem underneath the conversation. The employee took a real risk by speaking up. If you react with defensiveness, irritation, or a rushed apology that sounds hollow, you teach that person, and everyone who hears about it later, that raising a concern about a manager costs more than it is worth. Once that lesson lands, you stop hearing about small problems, and you only find out about big ones after they have already grown.

The situation gets harder when the behavior in question was not fully your call. If a senior leader drove the decision you are being asked about, you may feel blamed for something you did not originate. That feeling is valid, but voicing it in the moment shifts the conversation away from the employee's experience and onto your own discomfort. The employee is reporting an effect on their work, not filing a complaint against your character, and treating it as the second thing is where most of these conversations go sideways.

How to Prepare Before the Conversation

Preparation starts with a decision you make before anyone is in the room, which is that your first job is to understand, not to defend or fix. Walk in planning to ask more questions than you answer.

Separate two tasks in your head ahead of time. The first task is understanding what happened and what effect it had. The second task is deciding what you will do about it. Managers who collapse these into one step either promise changes they have not thought through, or they get defensive because they feel pressured to solve the problem on the spot. You can commit to following up without committing to a specific fix in the same breath.

Know your organization's escalation path before you need it. If what comes up involves discrimination, harassment, retaliation, safety, or another serious concern, your job is to follow the designated reporting process, not to run your own informal investigation. Deciding this in advance means you will recognize the line the moment you hear it, instead of trying to sort it out while someone is still talking to you. Most of what reaches you in a one on one will be routine, day to day friction, and for that kind of feedback it is reasonable to say plainly what you will look into and when you will report back.

What to Say in the Moment

During a regular one on one, Kai tells Morgan, "When you change priorities in the team chat late at night, I start the next day unsure which plan still counts." Morgan feels her stomach tighten, because the change actually came from a senior leader above her, not from her own judgment. She resists the urge to explain that and says instead, "Thank you for telling me. Walk me through the last time a message like that changed your work." Kai describes staying up late to finish a draft, then learning the next morning it was no longer needed at all.

Morgan asks, "Would a short morning note that names the one active priority and what can wait help you plan the day?" Kai says it would help, and adds that silence after a late night message makes people assume they have to respond right away, even at midnight.

Morgan does not stop at agreement. She says, "Here is what I can commit to right now, and here is what needs more thought before I promise it." She commits to sending one morning note after any evening change, for the next month. She tells Kai she will ask the wider team at the next staff meeting whether the new routine actually made things clearer, and she writes down Kai's example on the spot so she does not lose the detail later.

Mistakes to Avoid

The most common mistake is arguing from intent. Saying "that's not what I meant" or "I was just trying to help" answers a question nobody asked. Kai is not describing your motives, Kai is describing an effect, and the effect is the only thing you can verify right now.

A second mistake is promising too much too fast. Agreeing to change everything in the first sixty seconds sounds generous, but it usually means you have not actually thought about what is realistic, and employees notice when those promises quietly disappear a month later. A third mistake is treating the conversation as an evaluation of the employee's attitude for bringing it up, which shuts down candor faster than almost anything else you could do.

A fourth mistake is relying on memory instead of writing down what was actually said. It is tempting to summarize the feedback in your own words right away, but your summary usually smuggles in your own conclusion about what happened. The post Record an Employee's Words Without Adopting Their Conclusion covers this in more depth, and the same discipline applies here, write down what the employee actually said before you decide what it means.

Finally, do not let this conversation drift into something it is not. If what starts as feedback about your behavior turns into a request to change who someone reports to, that is a different conversation with different stakes, and rushing a structural decision to resolve interpersonal discomfort tends to create new problems. Clarify an Urgent Reporting Line Request Before Changing the Chart walks through how to slow that particular request down without dismissing it.

Practice and Score the Conversation

This conversation is hard to get right the first time you actually face it, which is exactly why rehearsing it beforehand helps. Run through the exchange with an AI counterpart that plays the employee and pushes back the way a real person would, including the parts where you feel the urge to defend yourself. DealSpeak is built for this kind of rehearsal, and it will score you on specific behaviors rather than a vague impression of how you sounded.

Look for a few concrete signals when you review the practice run. Did you ask for a specific example before offering any explanation of your own. Did you separate the commitment you made from the parts you said you needed more time to think about. Did you name the follow up moment, a staff meeting, a check in, a written note, rather than leaving the next step vague. Did you avoid explaining your intent even once, no matter how strong the pull was.

You can find more scenarios like this one, along with other manager and employee situations, among the HR and Leadership practice conversations built for people managers working through exactly these moments. Rehearsing the awkward part in private is what makes the real version calm instead of defensive.

Kai's feedback did not end the working relationship, it improved it, because Morgan slowed down, asked a real question, and followed through on a small commitment instead of a sweeping one. That is the whole skill. Handle the next moment like it, and your team will keep telling you what you need to hear.