Managing up: making your manager's job easier

The quarterly business review has been running for forty minutes. Your director is presenting to the VP and her team. Slide nineteen lands. The VP frowns and asks: “Why did the API latency spike in March?” Your director turns to you. You know the answer — you wrote a post-mortem about it six weeks ago — but you never shared it with her. She looks unprepared in front of her leadership. The meeting ends awkwardly.

You did nothing dishonest. You did nothing malicious. You simply assumed that your work was visible and that your manager had the context she needed. She did not. That gap — between what you know and what your manager knows — is the core problem that managing up is designed to close.

What managing up actually means

The phrase has a reputation problem. It sounds like a euphemism for political manoeuvring, for making yourself look good at others’ expense, for telling the boss what they want to hear. None of that is managing up. That is just flattery with extra steps, and it corrodes teams.

Managing up means treating your manager as someone you have a working relationship with — not just a source of assignments and approvals. In any functional relationship, both parties invest in the other’s success. Your manager invests in yours by giving you interesting work, removing blockers, and advocating for you in rooms you are not in. Your investment in theirs is simpler: reduce their uncertainty about you.

A manager’s most persistent anxiety is not your technical quality. It is the question of what they do not know. What is running behind? What decision has been delayed? What customer is unhappy and has not yet said so? What are you stuck on that you have not flagged? Managing up is the systematic practice of making the answer to all of those questions legible — before they have to ask.

The four practices

There is no proprietary framework here. These are observations from managers and the people who work well with them.

1. Learn their priorities and how they communicate.

Your manager has a strategy they are accountable to, a set of stakeholders they are managing sideways, and a leadership style. If you do not know what they are being measured on this quarter, you are optimising for the wrong things. Ask. “What are the two or three things that would make this quarter a win for you?” is not a presumptuous question. It is a sensible one.

Then pay attention to how they communicate. Some managers want a weekly bullet-point update in Slack. Others want a five-minute verbal sync on Monday morning. Some need everything in writing because they have back-to-back calls and process asynchronously. Find out — ask directly if you have to — and match their style, not yours. Your preferred mode of communication is irrelevant here. The goal is information transfer, and that only happens when the format suits the receiver.

2. Bring solutions, not just problems.

The rule is not “never raise a problem without a solution.” That is a misreading. Complex problems sometimes need to be raised before solutions exist, and pretending otherwise leads to delayed escalation.

The rule is: do the thinking first. When you surface a problem, try to arrive with a read on the situation: what you believe is happening, what you have already tried or ruled out, and what you think the options are — even rough ones, even ones you are uncertain about. This does not mean you hand them a finished plan. It means you have done the first-order thinking so they do not have to do it from scratch.

The practical difference: “The data pipeline is broken” requires your manager to start gathering context from zero. “The pipeline has been failing since Tuesday — root cause looks like a schema change in the upstream system; I’ve flagged it with the data-engineering team and we can either revert the schema or patch our ingestion code — I lean toward patching because revert has downstream effects, but I wanted your read before committing” requires them to make one decision. One is a problem transferred. The other is a problem you have half-solved and are asking for help finishing.

3. The no-surprises rule.

This one is non-negotiable. Your manager should never hear material information about you or your work for the first time in a public setting — a meeting, a review, a client call. That is the specific failure from the opening scene: not that the information was missing, but that it surfaced at the worst possible moment.

The no-surprises rule has two sides. The obvious side is escalation: flag risks and setbacks early, while there is still room to act. If a deadline is at risk on Tuesday, say so on Tuesday — not on the Friday before the Monday deliverable. The less obvious side is credit: share wins through your manager, not around them. If you solved a gnarly problem that is relevant to their stakeholders, tell your manager first. Let them be the one to share it upward. They get to look informed; you get to be the person who keeps them informed. Everyone wins.

The earliest you can surface a problem or a win, the more useful the information is. By the time it becomes visible to everyone, it is no longer information — it is news.

4. Ask for what you need — directly.

Many people wait for their manager to notice that they need clarity, protection, or a decision. Managers are busy and working with incomplete information about everyone on their team. If you need something, ask for it explicitly. There are three things people most commonly need and most rarely ask for clearly.

Clarity. “I have been working on this for two weeks and I realise I am not sure whether the goal is X or Y. Can we align on that before I go further?” This is not a sign of weakness. It is efficient. The alternative is two more weeks of building the wrong thing.

Air cover. Sometimes you need your manager to run interference — to absorb pressure from a stakeholder so you can do the actual work, or to represent your constraints in a meeting you are not invited to. “I need you to set expectations with the product team that this will take three weeks, not one. I can handle the work, but I cannot handle the daily status requests while doing it.” That is a reasonable ask. Say it.

A decision. You may be stuck on something that only your manager can resolve — a prioritisation call, a budget question, a conflict between two teams. Do not leave it vague. “I need a decision from you by Thursday on whether we build this in-house or integrate the vendor solution. I have laid out the trade-offs in this doc.” A specific deadline and a specific document make it easy to decide. Vague asks get deferred.

The trust gauge

Trust between you and your manager is not a fixed property — it is a variable that shifts with every interaction. The diagram below shows the dynamic.

The key insight in the diagram is asymmetry. Trust builds slowly, through dozens of small consistent actions. It erodes fast — a single public surprise can undo two months of reliable updates. This is not unfair. It is how risk-sensitive systems work. Your manager’s relationship with their manager depends partly on what they can credibly promise about you. Every time you validate that promise, trust rises a notch. Every time you make them look unprepared, it falls several notches.

A word on the politics of this

Some people resist managing up because it feels like self-promotion, or like they are playing a game rather than just doing the work. That discomfort is worth examining.

If you are technically excellent and you produce results but your manager does not have a clear picture of what you are doing or why, two things follow. First, your manager cannot advocate for you. Promotions, stretch assignments, interesting projects — these all require someone to make a case for you. They cannot make that case if they do not have the information. Second, in a downturn or a reorg, the people who are hardest to evaluate are the first to be cut. Visibility is not vanity. It is risk management.

The alternative framing: you are not doing this to look good. You are doing it so that your manager can do their job, which is to make decisions and to allocate resources effectively. The better their information, the better their decisions. Some of those decisions affect you. You have a direct interest in the quality of those decisions. Giving your manager the context they need is both professionally rational and straightforwardly helpful.

What to do this week

Pick one. Start with the update cadence if you do not have one. Ask your manager how they prefer to receive status updates and then set a recurring reminder to send one. Keep it short: what you shipped, what is in progress, what is at risk, what you need from them. Five bullet points. Once a week.

If you already do that, try the next-level version: before your next one-on-one (1:1), spend five minutes writing down the one thing that is at risk that you have not mentioned yet. Mention it in the meeting. Not as a confession — as a professional update. “I want to flag that the integration with the payments API is taking longer than I expected. We are still on track for the overall deadline, but only if I do not hit another snag. I wanted you to know now rather than later.”

That sentence, repeated consistently, is the core skill. Early, honest, matter-of-fact. It does not make you look weak. It makes you look like someone who can be trusted with harder problems.

That is the return on investment for managing up. Not a better relationship with your manager as an end in itself. A track record as someone whose information can be relied on — which is, in the long run, the rarest and most valuable professional asset you can build.