Managing up is one of the most misunderstood professional skills. It is not about flattery, office politics, or gaming your performance review. It is about building a working relationship with your manager that reduces friction, increases your autonomy, and makes sure your contributions are understood. In 2026, as distributed teams make invisible work the norm, managing up is no longer optional — it is how good work gets credited.
What changed in 2026
- Remote and hybrid work made visibility the central challenge. Proximity bias is documented and real — if your manager does not see your output, they tend to underestimate it. Managing up is partly about closing that gap honestly.
- Flatter organizations mean managers often have wider spans of control and less time. Brief, structured communication is more valued than ever.
- AI tools have raised output expectations. Managing up now includes being clear about what AI assisted versus what required your judgment — context that matters when evaluating contribution.
- Mental-health literacy at work increased; managers and reports are more willing to discuss workload and capacity explicitly, which makes managing up conversations easier.
Start by understanding your manager
Before you change anything you do, spend two weeks observing:
- How do they prefer to receive updates? Slack message, weekly email, verbal at 1:1?
- What is their biggest current pressure? Shipping a product, reducing cost, managing a reorg?
- What does "good work" look like to them? Some managers care most about deadlines; others, quality; others, stakeholder relationships.
- When are they most receptive to feedback or hard conversations? Not on deadline day.
This is not research for manipulation — it is how you communicate in a way that actually reaches them.
The five practices
1. Make your work visible proactively.
Send a short weekly update — 3–5 bullets: what you completed, what is in progress, any blockers you resolved. Do not wait for your manager to ask. This prevents the "what have you been doing?" conversation.
2. Bring solutions, not just problems.
When you surface an issue, have a recommended path forward ready. "Here is the problem, here are two options I see, I think option A is better because X — what do you think?" This is not about removing their role; it is showing you have thought it through.
3. Clarify expectations before starting, not after.
When you receive a new task, confirm: what does done look like, what is the deadline, how much latitude do you have? Misaligned expectations account for the majority of performance frustration.
4. Share bad news early.
A problem caught early is manageable. The same problem disclosed after it has become a crisis is a trust-breaker. Err on the side of early disclosure.
5. Disagree directly, not sideways.
If you think your manager is wrong, say so in your 1:1, with your reasoning. Do not air disagreements to teammates first. If you cannot change their mind, decide whether you can commit anyway or whether it is worth escalating.
Communication format table
| Situation |
Best approach |
| Routine update |
Weekly written summary (async) |
| Blocker requiring decision |
Slack/message with proposed solution |
| Disagreement on direction |
1:1, in person or video, with your reasoning prepared |
| Mistake or bad news |
Sooner is always better; do not wait for the weekly |
| Career conversation |
Scheduled dedicated meeting, not tacked onto a 1:1 |
Common mistakes
Over-reporting. Daily updates on routine work are noise. Weekly is usually right; more frequent for high-stakes projects only.
Complaining without asking. "This process is broken" with no proposal lands as a gripe. "This process is broken — here is what I'd change and why" is a contribution.
Managing up only when you need something. If your manager only hears from you when you have a problem or a request, the relationship will feel transactional.
Assuming your manager knows your career goals. They usually do not unless you have said them out loud, explicitly, in a dedicated conversation.
Waiting to be recognized. In a distributed team, invisible work gets forgotten. It is not bragging to make your contributions clear — it is professional communication.
What to skip
- Constant agreement — a manager who never hears pushback is being managed, not worked with. Respectful disagreement builds credibility.
- Managing optics over substance — visibility hacks that outpace actual output create a gap that review cycles expose.
- Going around your manager to their boss before addressing the issue directly — it almost always backfires.
FAQ
What if my manager is the problem?
Document issues, address them directly first, then escalate through HR or your skip-level if the direct approach fails. "My manager is hard" is worth naming explicitly — many are.
How do I bring up a workload that is too heavy?
Frame it as a capacity and priority problem: "I have X, Y, and Z this week with these deadlines — which one should slip if I can only complete two?" This turns a complaint into a decision request.
How often should I have a career conversation with my manager?
At minimum twice a year in a dedicated slot. Not shoe-horned into a 1:1 at the end.
Is managing up manipulation?
No more than clear communication is. The intent matters: are you trying to be more effective together, or are you gaming someone? The practices above are the former.
Where to go next
How to delegate tasks in 2026, How to handle workplace conflict in 2026, and How to ask for feedback in 2026.