"Managing up" sounds like a euphemism for flattery, and that reputation is deserved by a lot of bad advice on the topic. The actual skill has nothing to do with managing your boss's opinion of you and everything to do with managing the flow of information between you, so decisions get made with what they actually need to know, at the moment they need to know it, in a form they can use quickly.
Most friction between employees and managers is not a personality conflict. It is a mismatch in communication format: the employee gives detail-first updates when the manager needs conclusions first, or the employee waits for a scheduled check-in to raise something that needed to surface three days earlier.
Lead With the Conclusion
Managers are almost always processing more simultaneous threads than the people reporting to them, which means they need the bottom line before the reasoning, not after it. "The launch will slip two weeks because of a vendor delay, here's what we're doing about it" gives a manager everything they need in the first sentence. The same update delivered as a chronological account of the vendor problem, ending with the delay as a final reveal, forces the manager to hold uncertainty through the entire explanation before getting to the part they actually needed.
This is not about hiding complexity. The detail still belongs in the update, it just belongs after the headline, available for whoever wants to go deeper, not as a prerequisite everyone has to sit through first.
Surface Problems Before They Become Surprises
Nothing damages a working relationship with a manager faster than them learning about a serious problem from someone other than you, or later than they needed to act on it. The instinct to wait until a problem is fully solved before raising it, out of a desire to look competent, usually backfires: managers overwhelmingly prefer an early flag with an incomplete plan over a late reveal with a complete one, because early flags give them time to redirect resources or manage expectations upward themselves.
The format that works well here is short and forward-looking: what happened, what you are doing about it, what you might need from them. Skipping straight to "here's what I need from you" without the first two pieces tends to read as escalating a problem rather than managing it, even when the underlying facts are identical.
Disagreeing Without It Reading as Defiance
Disagreeing with a manager's decision is not insubordination, but the way it is phrased determines how it lands. Naming your reasoning and the specific risk you see, then explicitly deferring to their call once you have made your case, keeps the disagreement useful rather than adversarial: "I think this timeline is tight given X, here's the risk I'd flag, but I'll move forward as you've directed if that's the call." This is closely related to assertive communication that is direct without being aggressive: the goal is making your view fully legible, not making it prevail by default.
Match Their Preferred Channel
Some managers absorb information best in a two-minute verbal summary, others in a short written note they can read on their own time, and others only in the structure of a recurring one-on-one. Guessing wrong on channel is a common, avoidable source of friction: a manager who reads email at the end of the day will feel blindsided by an urgent issue you only mentioned verbally in passing. Asking directly, "when something urgent comes up, do you want a quick message or should I wait for our next check-in," removes the guesswork.
Workplace research organizations such as the Society for Human Resource Management have published extensively on manager-employee communication breakdowns, and a recurring finding across that research is that mismatched expectations about frequency and format, not disagreement over substance, account for a large share of reported friction in reporting relationships.
Asking for What You Need Without Apologizing for It
Employees frequently soften legitimate requests, more time, clearer priorities, a resource they are missing, with so much hedging that the actual ask gets lost. "Sorry to bother you, this is probably a dumb question, but" buries a request under apology before the manager has even heard what is being asked. Stating the need plainly, then briefly noting the reasoning if it helps, reads as more competent and easier to act on than a heavily hedged version of the same request, and it respects the manager's time by getting to the point they actually need to respond to.