A direct report goes over your head, and you find out at the worst possible time. Your manager mentions in passing that one of your reports came to them last week. With a question. With a complaint. With a proposal you had not approved. With something you had not even heard of.
The information lands in the same moment as the realization that you were the last to know.
This is the moment most first-time managers handle badly. The instinct is to feel betrayed. The instinct is to confront the report. The instinct is to spend the rest of the day rewriting the trust relationship in your head until they have become someone you can no longer rely on. None of those instincts are wrong. They are also not useful.
Going over your head is not one thing. It is at least three different things that look identical from your seat. What you do next has to depend on which one you are actually looking at.
The three kinds of going over your head
The complaint. They have a problem with you. Could be something specific, could be a personality fit issue, could be something you did six months ago that has festered. Instead of telling you, they told your boss. This is the version most new managers fixate on because it feels the most personal. Your response here will set the tone for everything that follows.
The end-run. You said no to something and they went looking for a yes. A budget request. A promotion timeline. A project assignment. A vacation conflict. You drew a line, they did not accept it, they went above you to see if your boss would draw a different one. This version is about getting around a no. It is not about you specifically.
The visibility play. Some reports go over your head for reasons that have nothing to do with you. They are building a relationship with your manager because they want exposure and promotion, and they think your manager is in a better position to give them both than you are. You happen to be in the chain, but you are not what they are optimizing around.
From your seat the three look identical. They are not the same problem.
The wrong moves when your direct report goes over your head
Do not confront the report the moment you find out. The temptation to walk to their desk or open a Slack DM is almost overwhelming. The conversation you have inside the first 24 hours is the conversation you will regret. The version that is worth having starts at hour 48 or later, after you have separated what is actually happening from what felt like was happening.
Do not vent about the report to your manager. Your manager is the person who just received the over-the-head contact. Whatever you say next is going to be filtered by them through “is this person upset that their employee came to me, or upset that the employee had a real concern.” If your first reply to your manager makes it sound like you are more focused on the breach of protocol than on whatever the underlying issue was, you have handed them a data point about you that you do not want them to have.
Do not change the working relationship with the report on the basis of the incident alone. The pull is to subtly cut them out. Smaller assignments, less stretch, less time. They notice. You will have created a self-fulfilling reason for them to keep going around you, because you have just confirmed what the relationship is to them.
What to do when your direct report goes over your head
First, find out what they said. Not by interrogating them. By asking your manager. The right question is some version of “I want to make sure I have the full picture. What did they bring you, and what was your read on it.” Most managers will tell you if you ask cleanly. The information matters because the response depends on which of the three categories you are actually in.
Second, separate the substance from the bypass. If your report raised a real issue that you should have heard, the bypass is the smaller problem. The substance is the bigger one. Treat them in that order. If your report raised something that turns out to be a strategic suggestion, a career bid, or a visibility play, the bypass is the bigger problem and you handle the substance only after you have handled the relationship.
Third, decide whether this is a one-time incident or a pattern. Going over your head once happens to almost every manager. It is a normal failure mode of a new working relationship. Going over your head three or four times is not a failure mode. It is a signal that they do not think you are the path to what they need. That is a different conversation and a different problem.
The conversation with the report
You do not have to have it the day you find out. You should have it within a week.
The framing that works is not “why did you go around me,” because that puts them on defense and makes the conversation about protocol. The framing that works is “I want to understand what was going on for you that made the conversation with my manager feel like the right channel.”
Listen to the answer. What they say will tell you which of the three categories you are in. If they say they did not think you would take it seriously, you are in the complaint category and the real conversation is about why they had that read. If they say they wanted a different decision, you are in the end-run category and the real conversation is about how decisions work on this team. If they say they were trying to build relationships with leadership, you are in the visibility category and the real conversation is about how you can help them do that without bypassing you.
Be careful about the close of this conversation. Do not extract a promise that they will not do it again. Promises like that do not survive the next moment of tension. What you want instead is a working agreement: “next time you have something you would take to my manager, talk to me first. If we do not land on something you can live with, you can still go up. I would just rather know.”
That last sentence is the one that matters. You are not banning the behavior. You are asking to be in the loop. The difference is whether your direct report feels managed by you or contained by you.
The conversation with your boss
This one is easier, but you need to have it. Your manager just received information about you, your team, or your decisions, from someone other than you. They are now sitting on a data point they did not ask for and have to decide what to do with it.
You do not want them sitting on that data point alone. The right move is a short conversation, within two or three days, that does three things. Acknowledge you know it happened. Tell them what you learned from it. Tell them what you plan to do about the underlying issue.
That conversation costs you maybe ten minutes. It moves your manager from “thinking about this incident behind my back” to “watching me handle this in front of them.”
What going over your head means longer-term
A direct report going over your head once is information. A direct report going over your head repeatedly is a signal that the working relationship has a structural problem, and the structural problem is usually yours to solve.
The bypass is best treated as a diagnostic. People who never get there usually keep treating it as a personal slight long enough that they stop being curious about what the report was actually trying to accomplish, and that curiosity is the only thing that fixes the relationship. The classic Harvard Business Review piece on the set-up-to-fail syndrome describes the same dynamic from the other direction: managers who write off a report often create the very behavior they were afraid of. The bypass is the visible end of the same loop.
You do not have to make this person your friend, and you do not have to forgive them. You do have to figure out what is broken in the channel between you. They did not go around you out of nowhere. They went around you because they did not think the route through you would get them what they needed. That read might be unfair. It might also be telling you something true about how you have been managing them, which is worth knowing whether you act on it or not.