How to Give Feedback to Your Own Boss

You’re in your weekly 1-on-1, and your boss just said it. “I ran into the client in the hallway and told them we’d have the beta ready for them by Thursday. Just get it done.” Your stomach feels like it’s full of cold gravel. The project plan you both agreed to last week is now garbage. Thursday is impossible without burning your team to the ground, and you’re the one who will have to look them in the eye and tell them to cancel their evenings. You nod, a tight, mechanical motion, while your mind races through a dozen half-formed sentences you know you won’t say. Your internal search engine is screaming, “how to tell my boss he is making a huge mistake” but the only sound coming out of your mouth is, “Okay, will do.”

The reason this moment feels like walking a tightrope over a canyon is because you’re caught in a specific kind of communication trap. It’s the gap between responsibility and authority. Your boss has given you ownership of the team and the project, making you accountable for morale, quality, and deadlines. But they retain the authority to unilaterally change the rules, pulling the rug out from under you while leaving you responsible for the fall. Any attempt to push back feels like you’re challenging their authority, but staying silent feels like you’re failing at the job they gave you. It’s a classic double bind: you are set up to fail, and any move you make feels wrong.

What’s Actually Going On Here

This trap isn’t usually born from malice. It’s a function of pressure and habit. Your boss is likely responding to pressure from their boss or the client. When squeezed, people don’t rise to the occasion; they default to their training. For many leaders, that training is command and control. They see a problem, they “solve” it with a decisive command, and they feel effective. They see their intervention not as an act of destabilisation, but as “clearing a path” or “making a tough call.”

You see this in smaller ways, too. The boss who says, “I trust you, just keep me in the loop,” then jumps into an email thread to give conflicting instructions to one of your direct reports. They see it as being helpful and “hands-on.” You experience it as being undermined. They’ve told you to steer the ship, but they keep grabbing the wheel.

The wider organisation often rewards this behaviour. The boss gets a reputation for being “decisive” and “getting things done.” The chaos and burnout on your team are invisible two levels up. They see the result, the client got the beta on Thursday, and praise your boss for their leadership. This reinforces the pattern. Your attempts to create a more stable, predictable process can be misinterpreted as you being “rigid” or “not a team player.” The system itself is set up to reward the very behaviour that makes your job impossible.

What People Usually Try (and Why It Backfires)

Faced with this no-win situation, most managers make one of a few predictable moves. They all feel logical in the moment, but they all reinforce the trap.

• The Soft-Pedal. You say something like, “Okay, Thursday will be tough, but we’ll do our best to make it happen.” This is an attempt to sound cooperative while flagging a concern. But your boss doesn’t hear the concern. They hear the “we’ll make it happen” and mentally tick the box. You’ve just implicitly agreed to an impossible standard.

• The Vague Warning. You try to hint at the problem without being confrontational: “The team is pretty burnt out right now.” This is an invitation for your boss to misunderstand you. They might reply with a sympathetic but useless, “I get it, it’s a busy quarter for everyone,” and move on, the core issue completely unaddressed.

• The Evidence Folder. You come prepared with spreadsheets and Gantt charts to prove, logically and definitively, that the Thursday deadline is impossible. This feels like the right thing to do, you’re using data. But to a boss who just made a promise, it doesn’t feel like data; it feels like an accusation. The conversation shifts from “how do we solve this?” to “why are you being so difficult?”

• The Hallway Complaint. You say “yes” to your boss, then go to a trusted colleague and vent about how unreasonable the demand is. This provides a moment of relief and solidarity, but it changes nothing. It reinforces your own sense of powerlessness and builds a culture of learned helplessness on the team.

A Different Position to Take

The way out is not a better argument. It’s a different position. You have to stop seeing your role as needing to get your boss to admit they are wrong. That is a battle you will almost always lose. You also have to let go of the idea that your job is to protect your team from your boss. This puts you in an adversarial position from the start.

Your new position is this: You are the person who makes the consequences of your boss’s decisions visible and concrete. You are not a resistor; you are a translator. You translate their optimistic, high-level commands into on-the-ground operational reality.

You shift from saying “We can’t do that” to “Here is what it will take to do that.” Your job is to describe the cost of “yes” so clearly that your boss is forced to own the trade-offs. You aren’t there to block their decisions; you’re there to ensure they make them with their eyes open. This reframes your feedback from insubordination to essential data. You are no longer the problem; you are a partner in executing their goals successfully in the real world.

Moves That Fit This Position

The language that comes from this position isn’t a script; it’s a reflection of your new goal. These are illustrations of what it can sound like.

• Present a Choice of Trade-offs.

  • What it sounds like: “We can hit the Thursday deadline. To do that, I’ll need to pull Sarah and Jin off the Acme project. Are you good with me telling the Acme account manager that their rollout is being delayed by a week?”
  • What it does: This is not a “no.” It’s a “yes, and…” It respects the boss’s authority to set the priority while forcing them to acknowledge the cost. The decision to delay another project is now theirs, not a problem you are simply complaining about.

• Reframe as a Request for Direction.

  • What it sounds like: “This new deadline conflicts with the quarterly goals we set last month. I’m not sure how to prioritise the two. Could you help me understand which one is more important for the business right now?”
  • What it does: This presents the conflict as a puzzle to be solved, not a mistake to be fixed. It frames your boss as the strategic leader whose guidance you need, which is a much more comfortable role for them to step into than “person who was just wrong.”

• Name the Pattern, Propose a Systemic Fix. (For recurring problems)

  • What it sounds like: “I’ve noticed a pattern where urgent client requests often derail our planned sprints. It’s impacting our ability to hit our larger roadmap goals. Could we experiment with creating a ‘fast-track’ lane for these, with its own dedicated resources, so we can protect the core project?”
  • What it does: It elevates the conversation from a single frustrating event to a systemic business problem. You’re not blaming them for being impulsive; you are co-designing a better process to handle a predictable business reality.

• Buy Time to Get Grounded.

  • What it sounds like: “Okay, I hear you. Let me go back to the project plan and figure out exactly what it would take to make that happen. I’ll come back to you in an hour with a couple of options.”
  • What it does: It prevents you from reacting from a place of frustration or fear. It breaks the cycle of immediate pressure and allows you to calmly formulate a response based on the position of making consequences visible, rather than just reacting with a panicked “yes” or a defensive “no.”