What Nobody Tells New Managers About Managing Up

Leadership just announced a priority shift. Or a new initiative on top of everything already in flight. Or that your team is absorbing the responsibilities of a role that was eliminated.

You do the math immediately — not dramatically, just the actual math. The strategy makes sense from where they're sitting. You can see that. But you're also the one who knows what's currently in flight, what gets dropped or delayed when priorities shift, what it costs the team to context-switch mid-project, and what morale looks like in a room that has been asked to do more with less for the third time this year.

You have information they don't have. Not because they're not paying attention — but because the execution costs of a strategic decision are invisible from the level where the decision gets made. The pivot looks clean on a roadmap. The cost shows up in your one-on-ones.

And you have a split second to decide: do you say something now, in this room — or do you take it back to your team, figure it out, and quietly absorb it?

It's not that you don't have the standing to push back. It's that you don't want to be the one who always has a problem with things. The person who can't just rally and execute. The manager who makes every announcement harder than it needs to be.

That calculation — the "go team" vs. "say the real thing" tension — is what managing up actually is for new and middle managers. And almost nothing written about it accounts for how complicated that moment really is.

The advice skips the hard part

The standard managing-up playbook is practical: understand your manager's priorities, communicate proactively, build the relationship before you need it, push back diplomatically. All of this is true.

What it doesn't address is the specific fear that stops most new managers before they ever get to the tactic: the fear of being seen as the negative one.

Leadership doesn't always know what a decision costs at the team level. They're not in the weeds. They're making calls based on the information available to them from where they sit — which often doesn't include your team's actual current capacity, the morale implications, or the tradeoffs that only become visible once you're close to the work. You're not pushing back because you disagree with the strategy. You're pushing back because you have information they don't have.

But that distinction doesn't always survive the room. Push back too directly, too often, or at the wrong moment, and the read on you shifts — not to "raises valid concerns" but to "hard to work with," "not a team player," "always has a problem with something." It doesn't matter that you were right. The label sticks.

This isn't just a credibility problem. Credibility is part of it — but so is the relationship you have with the people in the room, the trust they have in your intentions, whether the environment is one where dissent is welcome or quietly noted, and the culture of how leadership receives challenge. All of it is in play at once.

The squeeze is structural

A 2026 survey of nearly 1,000 middle managers by Simon Sinek's Optimism Company found that 75% report extreme burnout — and the primary driver they name isn't hours or workload. It's responsibility without authority: being accountable for outcomes they don't fully control, while trying to influence the people above them who do.

That's the managing-up problem in a single phrase.

You're accountable for your team's performance. If the new workload breaks something — a deadline, a person, the team's confidence in leadership — that lands on you. But you didn't make the call. You're the one absorbing it, translating it, and managing the fallout on both ends.

The gap between what leadership sees from above and what you can see from where you stand is real — and it's structural, not personal. They're evaluating at the strategic level: does this initiative align with our goals, do we have the budget, does the timeline make sense given what the business needs. You're evaluating at the execution level: what's currently in progress, what the cost of a priority change actually is in hours and momentum, where the team's capacity actually sits, and what happens to morale when people are asked to drop work they've invested in and pick up something new.

Both views are necessary. The strategic view without the execution reality produces decisions that look sound until they hit the ground. The execution view without the strategic context produces managers who fight every decision because they're only seeing the cost, never the reason.

Managing up is the bridge between those two levels. It's getting your ground-level information to the people making decisions before the consequences show up in the data — the missed deadline, the resignation, the quiet drop in output that takes a quarter to show up in any metric.

The problem is that most new and middle managers were never taught how to do that without it backfiring. According to Forbes/McKinsey data, 58% of new managers received no formal training before taking the role — which means most of them are figuring this out in real time, usually right after an announcement that just changed everything their team is working on.

How to surface the real impact without becoming the problem

The goal isn't to not push back. It's to push back in a way that positions you as someone who is solving the problem with leadership, not someone who has a problem with leadership.

A few things that actually change how it lands:

Lead with the business impact, not the team experience. "My team is already at capacity" sounds like a people problem, which is easy to interpret as a management problem — meaning yours to solve. "Adding this to the current sprint risks the Q3 deliverable" sounds like a business problem, which is everyone's problem. The concern is identical. The framing determines whether leadership hears it as information or complaint.

Be specific about the tradeoff, not the difficulty. Vague concerns are easy to absorb and not act on. "This feels like a lot" gives leadership nothing to work with — they can nod, express confidence in you, and move on. "If we take this on as scoped, the two things most at risk are X and Y — I want to flag that before we commit" forces a real conversation. Name the actual tradeoff. Make the decision visible.

Bring a recommendation, not just a problem — when you have time to prepare one. Walking in with a concern and a proposed path forward reads completely differently than walking in with a concern alone. It signals that you're trying to help solve it, not just register that it's hard. It also gives leadership something to respond to other than whether they agree the situation is difficult. This doesn't apply when you're hearing something live in a meeting for the first time — in that moment, you don't have enough information to propose anything, and pretending otherwise will show. In a live announcement, the better move is usually a clarifying question rather than a position: "Can you help me understand how this sits relative to X that's currently in flight?" buys you time, surfaces the information you need, and signals that you're thinking about the execution without sounding like you're pushing back before you've even processed it.

Build the relationship before you need it. This one is harder to deploy in the moment, but it's the context everything else runs on. How well leadership knows you, how much they trust that your concerns are team-focused rather than self-protective, whether you've shown you can handle hard things before — all of that is already running in the background when you open your mouth in that meeting. The relationships you build in quieter moments are the ones that make the harder moments possible.

The pattern that trips people up

Most new managers end up in one of two failure modes, and neither is what they think it is.

The first is over-adaptation. They say yes to everything. They absorb every ask from leadership without pushing back, then carry it back to their team and over-promise on what they can deliver. The team eventually stops trusting that what they're being asked to do is actually realistic. And leadership, paradoxically, stops trusting the manager too — because someone who never surfaces concerns is either not looking closely enough, or not confident enough to say what they see.

The second is over-advocacy. They push back early, often, and hard — before the credibility is there to back it up. Leadership reads it as poor judgment, poor culture fit, or an inability to operate within real constraints. The intention is good. The timing is wrong.

The balance — knowing when to absorb, when to redirect, and when to actually push — is the skill. It develops over time. But understanding where you tend to default makes it possible to catch yourself before the pattern becomes established.

What this looks like by archetype

Your natural operating style shapes which of these patterns you're more likely to fall into.

Firefighter — Your instinct is to make the problem go away. When leadership hands you something difficult, you take it, absorb the urgency, and get to work. That responsiveness reads well early — you're the person who handles things. But it can slide into over-adaptation without you noticing, because you've built your credibility on execution, not on pushing back. The issues that need escalating get solved instead, and leadership never sees the cost. Until it compounds.

Architect — You manage up through logic. Your impulse is to build the case: the data, the analysis, the documentation that makes the problem undeniable. This works — but it can come across as challenging rather than collaborative when the relationship is new. Leading with "here's why this doesn't work" before you've established that your judgment is worth engaging with can create friction you didn't intend.

Strategist — You can already see where this is heading. Two moves ahead, maybe more. The managing-up trap for Strategists is trying to have the strategic conversation before you've been invited into it — signaling foresight in ways that read as overreach when you're still in the credibility-building phase. The instinct is right. The timing and framing need calibrating.

Connector — Your instinct is to protect the relationship. You don't want to create tension with leadership early, so you tend to adapt — take the ask, manage the fallout with your team, smooth things over. Your team likes you. They also, over time, start to notice that what comes down from leadership doesn't always match what you said you'd advocate for. The relationship-first instinct is a strength. It becomes a liability when it consistently overrides what your team actually needs you to do upward.

What this is actually about

Managing up as a new or middle manager isn't just a communication problem. It's a conditions problem. Whether you can say the real thing — and have it received as useful rather than difficult — depends on the relationship, the trust, the environment, and whether you've built enough of a track record that your concerns read as informed rather than reflexive.

None of that is fully in your control. But your operating style — how you naturally show up in these moments, what you default to under pressure, where you tend to over-adapt or over-push — is something you can actually work with.

Understanding your defaults is the more honest starting point than a list of tactics.

Your Leadership ROI Score shows you where you're creating traction and where you're compensating for the gaps — including in the upward relationship most managers get the least honest feedback on.

Sources: Simon Sinek's Optimism Company Middle Manager Survey (2026) | Forbes/McKinsey (2026) | Gallup State of the Global Workplace 2026