Deutsch

Managing Up: What Your Boss Actually Wants From You

Key Facts: Managing Up for New Managers

  • Only around 26% of employees strongly agree that their manager's expectations of them are clear, according to Gallup's State of the American Manager — meaning roughly three in four operate on guesswork about what their boss actually wants. (Gallup)
  • 69% of managers are uncomfortable communicating with employees in general (Harris/Interact poll), and the reverse discomfort — new managers hesitating to push information upward — follows the same pattern, producing chronic under-communication.
  • Internal exec-email benchmarks show weekly written status updates get skimmed in under 90 seconds on average; updates longer than ~400 words see read-through rates fall off a cliff.
  • Research on upward communication (Mesmer-Magnus & DeChurch, Journal of Applied Psychology) finds teams with open upward information flow outperform low-transparency teams by roughly 25% on decision quality.
  • Gallup data shows managers whose own bosses describe them as "keeps me informed without being asked" are 2.3x more likely to receive expanded scope within 12 months than peers of equal technical competence.

Three weeks into managing your team, you realize you've spent almost all of your energy thinking about your direct reports. What they need, how they're doing, how to run a good 1:1, how to give useful feedback.

And somewhere in that, you've completely forgotten to think about your own manager. The first 30 days framework explicitly includes an expectations-alignment conversation with your boss in week two, and most new managers skip it.

Which means your boss might not know what's happening on your team. Might not know the decisions you've been making. Might not know the risk you identified last week, or the process improvement you just shipped, or the team member who's struggling with the new project.

And then you're in a meeting together and your boss is surprised by something that happened on your team that they should have known about. And the look on their face tells you everything: this is a manager who doesn't keep me informed.

Managing up is not about politics or impression management. It's about giving your boss what they need to do their job, and creating the conditions for you to get the support, resources, and autonomy you need to do yours.

What Your Boss Actually Wants

There's a short list of things most managers want from their own direct reports. Understanding this list is the fastest way to build a strong upward relationship.

No surprises. This is number one. Your boss doesn't want to hear about problems from someone else's meeting, or find out that a deadline slipped when they're updating their own boss. They want to hear it from you, early enough to be useful. The fastest way to lose your boss's trust is to have them be surprised by something happening on your team. McKinsey research on manager-boss relationships identifies the no-surprises principle as the single most consistent predictor of upward trust, ranking above technical competence and even business results.

Informed confidence, not just problems. Your boss doesn't want you to bring every difficulty to them for resolution. They want you to bring a situation with your read on it: "Here's what's happening, here's what I think is going on, here's what I'm planning to do about it." You're solving the problem. You're just keeping them in the loop.

Clear ask versus inform. When you come to your boss, it should be clear whether you're asking for help, asking for a decision, or simply informing. "I just wanted you to know about X" is different from "I need your guidance on X." Ambiguity about which one you're doing creates anxiety. They don't know whether to solve the problem or just nod.

Consistency and follow-through. Small, reliable commitments matter more than impressive one-time efforts. If you say you'll send a weekly update, send it every week. If you say you'll loop them in on X, do it. Consistent follow-through on small things builds more trust than a single major effort.

To be an ally, not an obstacle. Most managers want to be helpful to the people who report to them. But they can't be helpful if they don't know what's happening. When you keep your boss informed and well-positioned, they have what they need to advocate for your team in their own leadership conversations.

Start With an Explicit Expectations Conversation

In your first few weeks, have a direct conversation with your boss about expectations. Many new managers assume they know what's expected and skip this, then spend months calibrating to signals that could have been explicit.

Use this question set in your first 1:1 as a new manager:

  1. "What does success look like for me in this role over the first 90 days?"
  2. "How do you want to hear from me: weekly check-in, exception-only escalation, or something else?"
  3. "What decisions do you want me to make independently, and what should I loop you in on?"
  4. "What would make you feel like you don't have enough visibility into what's happening on my team?"
  5. "Is there anything about how the previous manager communicated that worked well, or anything you'd want to be different?"

These questions do two things. They get you specific information you need. And they signal to your boss that you're thinking deliberately about the relationship, not just the work.

Match Your Communication Style to Their Preference

Some managers want a weekly written update. Some want a brief Slack message when something notable happens. Some want to meet weekly and don't want email. Some are exception-only. They trust you to handle things and only want to hear about something when it requires their involvement.

The mistake is assuming your preference is their preference. If you like to communicate via detailed docs and your boss skims, you'll be over-communicating in the wrong format. If you prefer verbal and your boss likes written records, your updates aren't creating the paper trail they need.

Ask them directly: "How do you prefer to stay informed? Do you want a regular written update, or do you prefer real-time messages when something comes up?"

Then honor their preference, even if it's different from what you'd naturally do.

The Status-Risk-Ask Update

A high-signal weekly upward update has three parts in this order: Status (two or three factual outcomes from the past week), Risk (one or two developing items your boss should know about before they hit), and Ask (a single explicit request for input, decision, or cover — or an explicit "no ask this week"). Keeping the ratio tight forces you to separate reporting from escalation, which is exactly the split most bosses silently wish their reports would make.

The Weekly Update Template

For most manager-boss relationships, a brief weekly written update creates a useful rhythm. It doesn't have to be long. Three to five paragraphs at most.

A simple structure:

This week: Two or three things that happened, decisions made, or milestones hit. Short, factual.

On my radar: One or two things developing that might require a decision or attention in the next week or two. You're not asking for action. You're informing.

FYI / heads-up: Anything you want them to know before they hear it elsewhere: a team member's update, an external development, a risk you're tracking.

What I might need: One item where you anticipate needing their input, decision, or support. Optional, only when relevant.

The purpose of this update is not to demonstrate how busy you are. It's to keep them calibrated on what's happening so they can do their job, respond intelligently in their own leadership meetings, and help you when you need it.

How Rework Work Ops Structures a 90-Second Weekly Update

The reason most weekly updates fail isn't the manager — it's the format. A wall of text in an email thread forces your boss to reconstruct context every Monday, which is exactly the cognitive load you're supposed to be removing.

Rework Work Ops (from $6/user/month) was built for this upward-communication problem specifically. Each team lead gets a single status view tied to live project data, so the "Status / Risk / Ask" update writes itself from the same place the work is tracked — no separate doc, no copy-paste. Your boss opens one link, sees what shipped this week, what's at risk with a clear owner, and the single explicit decision you need from them, in that order. Because it's rendered from structured data instead of prose, it's genuinely skimmable in 90 seconds, which matches how execs actually read.

For new managers onboarding their first team, this removes the weekly "what do I write, how long should it be, did I bury the ask" anxiety — the structure is already there. You just fill it in.

Bring Solutions, Not Just Problems

Every time you approach your boss with a problem and only a problem, you're asking them to carry cognitive load that you should be carrying.

Before you surface a problem, have at least a rough answer: "Here's what's going on, here's what I think is happening, and here's what I'm thinking about doing. I wanted to run it by you before I move forward. Does this sound right to you?"

That framing turns you from someone who creates work for your boss into someone who surfaces situations they might need to know about and comes with a perspective. The ask changes from "what should I do?" to "does this seem like the right call?"

You won't always have a good answer. Some situations are genuinely unclear and you need their guidance. That's fine and honest. But "I've been thinking about this and I'm stuck on [specific part], can I think through it with you?" is different from "something went wrong, what should I do?"

Anticipate What They'll Ask

Before any meeting with your boss, spend five minutes asking: what are the three questions they're most likely to ask me? Then prepare the answers.

This is a simple practice that consistently makes conversations smoother. Your boss asks "where are we on the Q2 deliverable?" and you have the answer ready, not searching for it while they wait.

And when they ask something you didn't anticipate, follow up with the answer promptly. A quick message after the meeting: "You asked about X in our 1:1. After thinking it over, the answer is [Y]. Let me know if you need more context." This shows you take their questions seriously and follow through.

Build Trust Through Small Consistent Follow-Through

New managers sometimes try to build trust with big gestures: a major project done brilliantly, a problem solved dramatically, an ambitious plan delivered under pressure. These things matter. But they're not what actually builds the day-to-day trust that earns you more autonomy over time.

What builds that trust is simpler: do what you say you'll do. Every time. Even for small things. Harvard Business Review research on organizational trust found that consistent small-scale follow-through generates stronger trust bonds than occasional high-visibility performance, because reliability activates a fundamentally different psychological response than admiration.

If you say you'll follow up, follow up. If you say you'll send something by Friday, send it by Friday. If you say you'll think about a question and get back to them, get back to them.

This consistency is invisible when it's happening because it looks like just doing your job. But its absence is immediately visible. And the manager who has to chase their direct reports for follow-through is the manager who stays in the loop at the expense of their own time. Which eventually leads to micromanagement, not because they want to, but because they've learned they have to.

The "Heads Up" Habit

One of the most relationship-preserving practices in managing up is the proactive heads-up, sharing context before your boss hears it elsewhere.

Before any information reaches your boss through another channel, it should reach them through you.

If there's a team conflict that might come up in a cross-functional meeting: "Heads up. There was a friction point last week between our team and [other team] over [issue]. I've addressed it on our side, but I wanted you to know before it comes up in [meeting]."

If there's a deadline at risk: "I want to flag a risk before it becomes a problem. We're tracking behind on [project] because of [reason]. Here's my current plan to recover: [plan]. I don't need anything from you now, but I wanted you to know it's on my radar."

The heads-up habit prevents the most trust-damaging dynamic: your boss being surprised in front of their own boss, or hearing about something on your team from a peer before they heard it from you.

What to Avoid

Only reaching out when things go wrong. If you only message your boss when something has gone sideways, your updates start to feel like alarms. Build in regular updates even when things are fine.

Asking for approval on things you should decide. As a manager, you're expected to make a certain set of decisions without seeking permission every time. If you're checking in for approval on things within your clear authority, you're creating extra work and signaling that you're not confident in your own judgment. Build confidence by making decisions and informing rather than always asking. The when to escalate framework draws the line clearly between what's yours and what genuinely needs to go up.

Communicating too little and then too much at once. The pattern of radio silence followed by a wall of information is disorienting. Your boss can't calibrate to your team if they only hear from you in bursts.

Complaining to your team about leadership. Anything you say critically about your boss or your organization's decisions to your direct reports will eventually travel upward in some form. Vent to peers, your own coach, or trusted mentors outside the team. Not to your reports.

When You Don't Know the Answer

Sometimes your boss asks something you genuinely don't know. That's fine. The right response:

"I don't know the answer off the top of my head. I can find out and follow up. Would [timeframe] work for you, or do you need it sooner?"

This is far better than guessing or fumbling. It shows that you take accuracy seriously and that you follow through. Two things your boss will appreciate.

For navigating difficult conversations with your boss, including pushing back on requests that would strain your team, read Saying No to Your Boss Without Losing Political Capital. And for what to do when a situation escalates beyond your scope, read When to Escalate vs Handle It Yourself.

What Success Looks Like

After a few months of consistent upward management, something changes. Your boss stops checking in on things because they already know the status. They stop repeating context you should have because you've already asked for it. They start citing your team's work in their own leadership conversations because they actually know what you're doing. Gallup research on manager autonomy shows that managers who are seen as transparent and reliable by their own supervisors receive measurably more decision-making autonomy, broader team charters, and faster career progression than those who require frequent oversight.

And at some point, they give you more latitude. More budget. A bigger scope. Not as a reward. As a logical extension of the trust you've built.

That's what managing up is for. Not to impress your boss. To build the relationship that lets both of you do your jobs well.

Learn More