You do careful, excellent work. You hit your deadlines, you catch the errors nobody else catches, and you assume that’s enough. Then the interesting project, the one you’d have been perfect for, goes to the colleague who talks more in meetings and ships less than you do. You tell yourself it’s a visibility problem, that you just need to be louder.
It usually isn’t a visibility problem. The real issue is quieter and more fixable: your manager doesn’t have a clear model of what you’re working on, what you’re deciding, or what you actually want next. They’re not ignoring you. They just can’t see you well enough to hand you the right thing.
The skill that fixes this is managing up. Done well, it isn’t currying favor and it isn’t reading your boss’s moods. It’s communicating your own priorities, reliability, and judgment so clearly and consistently that your manager starts managing around you instead of over you. This post covers the line between managing up and sucking up, the four things your manager structurally needs, scripted moves for the three boss types that make this genuinely hard, and word-for-word language for the conversations most people avoid.
One distinction up front, because it’s the one people get stuck on: managing up changes how clearly your manager understands you. It never changes what you actually believe or do. The moment it touches the second thing, it stops being a skill.
What managing up actually means, and what it is not
The working definition
Managing up is deliberately shaping how you and your work get understood, resourced, and prioritized by the person you report to. The goal is making sure the picture in their head matches the reality of your work, so the decisions they make about you (projects, scope, growth) are based on accurate information. Pleasing your manager is a side effect at best, and a distraction at worst.
The foundational idea comes from a 1980 Harvard Business Review article by John Gabarro and John Kotter, “Managing Your Boss,” still in print decades later. Their core point: you and your manager are in a relationship of mutual dependence between two fallible people. Your manager needs your work and your honesty to do their job, and you need their support and resources to do yours. Managing up is just taking responsibility for your half of a relationship most people treat as one-directional.
The line between managing up and sucking up, drawn not disclaimed
The cleanest test is behavioral. Ask yourself: am I changing how I communicate something, or what I actually do or believe?
Changing how you communicate is the skill. You lead with the conclusion instead of burying it. You flag a risk in writing before it becomes a fire. You frame your update around what your manager cares about. None of that touches your real judgment. It just makes your judgment legible.
Changing what you do or believe is deference, and it quietly erodes your effectiveness. Three behaviors cross the line. You volunteer agreement you don’t actually hold, just to end the friction. You soften an honest assessment because the real version might land badly. You drop your own priorities to chase whatever your manager got visibly excited about this week. Each one makes you easier to be around and worse at your job, and over time your manager learns they can’t trust your yes, because you say it too easily.
Why every IC needs this skill, not just people who want to manage managers
The IC-specific stakes
Managing up is often pitched as a stepping stone to becoming a manager. For an individual contributor who has no interest in managing anyone, it matters just as much, because it controls concrete things you care about.
It decides which projects you get. Managers assign the interesting, high-growth work to the people whose judgment they can see, not necessarily the people doing the best work in silence. A manager who can’t quite see your reasoning will hand the ambiguous, career-making project to someone they trust to make calls without supervision, and trust is exactly what visible judgment buys. It creates visibility above your direct manager, because a manager who understands your work represents it accurately to their own boss, and most of the decisions about your trajectory get made in rooms you’re not in. It protects your bandwidth. A manager who knows what’s already on your plate is far less likely to quietly pile more on, which means you have the standing to push back on scope creep instead of silently absorbing it. It’s also a close cousin of influence without authority, the broader skill of getting expertise recognized when you don’t hold positional power. And it’s the main lane for growth when there’s no management track in front of you, because senior IC progression runs on trusted judgment, which is exactly what managing up makes visible.
The Gallup number, framed carefully
It’s worth being honest about why this relationship deserves deliberate effort. In its 2015 State of the American Manager study, drawing on 2.7 million employees, Gallup found that managers account for at least 70% of the variance in team engagement scores.
Read that carefully, because the direction matters. The study measures the manager’s effect on the team, not the report’s effect upward, so managing up does not somehow cause that 70%. What the number does tell you is that the relationship with your manager is the single biggest structural driver of whether your work feels engaging. That’s exactly why managing it deliberately, from your side, is worth the effort. You’re not trying to manufacture engagement. You’re tending the one relationship that most shapes your daily experience of the job.
The four things your manager actually needs from you
Notice that this section is about what managers structurally need, not what any individual manager personally prefers. Preferences vary. These four hold across almost all of them.
No surprises
Your manager can absorb a lot of bad news. What they can’t absorb is bad news they learn about too late to do anything with. Anything that changes your timeline, your output, or your confidence in a deliverable should reach them while there’s still room to act.
The phrasing that works is simple: “I wanted to flag this before it became a problem.” Said early, a slipping deadline is a manageable adjustment. Said the day it’s due, it’s a crisis with your name on it. Same information, completely different experience for the person receiving it, and the only variable you controlled was timing. The no-surprises principle is the foundation everything else in managing up sits on, because it’s what earns you the trust to be given room. Managers extend autonomy to the people who never blindside them, and they tighten their grip on the people who do.
Punchline-first communication
Most people communicate by reconstructing how they arrived at a conclusion: context, then analysis, then finally the point. Operator and writer Wes Kao calls the fix punchline-first. Lead with your conclusion or your ask, then give the reasoning for anyone who wants it.
Here’s the before and after. Before: “So I looked into the latency issue, and it turns out the caching layer was misconfigured, and there’s also a query that’s scanning the whole table, and I think if we don’t address this soon it could affect the launch.” After: “I think we should push the launch by three days. There are two database issues that will cause user-facing slowness, and here’s what each would take to fix.” The second version hands your manager the decision they actually need to make, then supports it. A busy person can act on the second one in ten seconds.
The say-do-report loop
Wes Kao also names the loop most ICs leave open: say what you’ll do, do it, then report that it’s done. The report step is the one people drop, because once the work is finished it feels redundant to mention it.
It isn’t redundant. The report is what builds your manager’s model of you. Every closed loop is a small data point that says “this person does what they say they’ll do,” and those data points accumulate into trust. The compounding effect is the whole point: a manager who has watched you close fifty loops stops checking on you, because your reliability has earned you the room. Silence after you finish something feels efficient. It actually keeps your manager guessing, which keeps them hovering.
Task-relevant maturity
Andy Grove, in “High Output Management,” gave the concept that ties this together: task-relevant maturity. How closely a manager should monitor you isn’t fixed. It scales inversely with how much experience you’ve demonstrated on that specific task. New task, low maturity, more oversight is appropriate. Proven track record on that task, high maturity, oversight should recede.
This reframes a lot of what gets labeled micromanagement. Often the root is a maturity-legibility problem: your manager doesn’t yet have evidence of your maturity on this particular task, so they default to monitoring. Personality has less to do with it than most people assume. Your job in managing up is to make that maturity visible faster, which is exactly what the playbooks below are built to do.
Playbooks for the three boss types that make managing up genuinely hard
Most managing-up advice quietly assumes a reasonable, present manager who responds well to clear communication. Three types break that assumption. The point isn’t that these managers are bad people. It’s that the structural dynamic with each one needs a different set of moves than the standard advice gives you.
Before the playbooks, the most important caveat in this entire post. Managing up is for the normal-dysfunction manager: the one who’s busy, anxious, overloaded, or disorganized. It is not a tool for managing a genuinely abusive or dysfunctional one. Chronic credit theft, retaliation, undermining, or outright bullying is not a communication problem you can script your way out of. That’s an HR, escalation, or exit problem, and treating it as a managing-up challenge keeps you absorbing harm that you should be documenting and reporting. Hold that line as you read what follows. The scripts are for normal friction, not for mistreatment.
The micromanager
What’s really happening is usually task-relevant maturity, not pathology. Your manager doesn’t yet have enough evidence of your judgment on this specific work, so their default is to watch closely. The trap is resenting the oversight and quietly working around it, which removes the very evidence they need and makes them watch harder.
The move is to flip the timing. Give them the information before they ask for it, and explicitly signal your maturity on the task. A script: “Here’s where the migration stands as of this morning: two of the three services are cut over and tested, the third is scheduled for Thursday, and I’ve already validated the rollback path in case anything breaks. I’ll send the same update Thursday evening.” You’re not waiting to be checked on. You’re making checking unnecessary.
Before: your manager pings you three times a day asking for status, and you feel watched. After: you send one proactive update each morning, the pings stop within two weeks, and the oversight quietly recedes because you’ve made your reliability visible.
The absent boss
This one is usually over-allocation, not neglect. Your manager is stretched across too many people and priorities, so the gap you’re feeling is structural, not personal, and almost certainly not aimed at you. The trap is waiting for direction that simply isn’t coming, then stalling, then resenting being stalled.
The move is to stop asking open questions and start bringing decisions that are ready to approve. Replace “what should we do about the vendor contract?” with a default and a deadline: “I’m going to renew the vendor contract for twelve months at the current rate unless I hear otherwise by Friday. The alternative is a month-to-month at a 15% premium, which I don’t think is worth it.” Silence becomes a yes, you keep moving, and your manager gets a zero-effort way to redirect you if your default is wrong. You’ve made it easy for an overloaded person to stay involved without spending time they don’t have.
Before: three decisions sit blocked for two weeks waiting on a manager who never replies. After: you send each as a default-with-deadline, two go through on silence, and your manager weighs in on the one that actually needed them.
The credit-taker
Here the honest framing matters most. The move I’m about to give you does not promise the credit-taker stops. It can’t. What it does is build an independent, visible record of your work that protects you regardless of what your manager does. The trap is the two reactions that both fail: confronting them in the moment, which reads as petty and rarely lands, or staying silent, which lets the record stay wrong.
The move is to create a visible evidence trail that lives where stakeholders can see it, not just between you and your manager. Send written summaries of what you delivered. Present your own work in the rooms where the people who matter are sitting. When it’s appropriate, give a brief, factual update to a skip-level. A script for a follow-up after a meeting where your work was presented as someone else’s: “Quick recap for the thread so everyone has it in writing: I built the forecasting model and ran the scenarios we walked through today. Happy to dig into the methodology with anyone who wants the detail.” No accusation. Just a clear, dated, public record with your name on the work.
One firm boundary, which loops back to the caveat above. The visible-record move is for occasional or careless credit-blurring. If the credit theft is deliberate and persistent, that’s not a managing-up problem anymore. That’s a pattern of undermining, and the right response is to document it and escalate it through HR, not to script your way around it indefinitely.
Scripts: exactly what to say in the four conversations most ICs avoid
Pushing back on a directive you think is wrong
The goal is to register your reasoning, not to win an argument. Lead with the shared objective, present what you’re seeing rather than a verdict, and keep it a conversation. “We both want this launch to hold its date. I’m seeing a risk in the current plan: the QA window is only two days, and the last two releases of this size needed four. Can we talk through whether to cut scope or move the date?”
If your manager hears you out and still decides to proceed, you disagree and commit. You’ve put your view on the record, which is the no-surprises principle working in your favor, and now you execute the decision fully and in good faith. That combination, honest pushback followed by genuine commitment, is what makes your next objection land as judgment rather than resistance. It’s professional influence, never insubordination.
Flagging a problem before it becomes a crisis
This is no-surprises in practice. The instinct is to wait until you have a solution before you raise the problem. Resist it when the problem affects a timeline or commitment your manager owns. “I want to flag something early. The data migration is more tangled than we scoped, and I think it adds about a week. I’m working three options to claw some of that back, and I’ll have a recommendation by Thursday, but I didn’t want you to hear about the slip later.” You’ve surfaced it while there’s still room to act, and you’ve shown you’re already on it.
Asking for visibility, for yourself, not as a complaint
The reframe that keeps this from sounding like grievance is to borrow the SBI model (Situation, Behavior, Impact) and aim it upward, factually. Anchor it to a situation, describe what happened plainly, name the impact, then make a specific ask. “In last week’s review (situation), the dashboard work I led got rolled up under the team summary without attribution (behavior), and a couple of the directors there didn’t realize I’d driven it (impact). For the next one, could I present that section myself?” It’s specific, it’s not an accusation, and it asks for one concrete thing. If you want to get sharper at framing this kind of upward feedback, it’s a skill worth assessing and practicing.
Owning a missed expectation when you dropped the ball
When you genuinely missed something, the move is to own it cleanly, state the correction, and close the loop, with no defensiveness padding it out. “I missed the deadline on the report, and that’s on me. I underestimated the data cleanup. Here’s what I’m doing: the draft is with you by tomorrow noon, and I’m building in a buffer on the next two so this doesn’t repeat.” Owning it fully actually builds trust faster than a flawless record does, because it shows your manager you’ll tell them the truth when it costs you something.
A note on where most of these conversations should happen: your recurring one-on-one is the natural home for the visibility and pushback conversations, the ones that need a little air. The crisis-flag and the dropped-ball owning shouldn’t wait for it.
What your manager wishes you would do differently
It’s worth a brief turn to your manager’s side of the table, without this becoming a post about how to be a manager. Three frustrations come up again and again, and the useful part is that each one maps to something you can change on your own.
The first is not knowing what you’re actually working on day to day. The fix is yours entirely: a short, regular update that keeps your manager’s model of your work current, no permission required. The second is being handed problems with no proposed solution attached, which turns your manager into your task queue. You can change that by bringing one recommendation with every problem, even a tentative one. The third is learning about timeline changes after the fact, which is just the no-surprises principle from your manager’s point of view. Surface the slip early and that frustration disappears.
None of these requires your manager to change first. That’s the quiet power of managing up: almost all of the leverage sits on your side of the relationship. Which raises the only hard part left, which is knowing what to actually say in the moment, to your specific boss.
Rehearse the conversation before you have it
Most people get managing up intellectually. The frameworks make sense on the page. The hard part is the live conversation with the specific boss in front of you: the micromanager who needs reassurance, the absent one who needs a default to approve, the credit-taker who needs a record on file. Reading about it doesn’t prepare you for saying it out loud when it counts.
That’s the gap Merlin closes. Merlin is Risely’s AI coach, native inside Slack and Microsoft Teams, and it lets you rehearse the conversation first. Describe your situation, and Merlin surfaces the underlying pattern and walks the exchange with you line by line, so you’ve already said the hard sentence once before you say it for real. Practice your next managing-up conversation with Merlin before it’s the one that counts.