Nobody teaches you this part. You learn to manage your team, and you assume managing your own manager will just sort itself out. It doesn't. It's a skill like any other, and most people either ignore it and end up invisible, or overdo it and end up performing instead of working. Neither builds real trust.
Seven moves for working well with your own manager.
01
Learn what your manager actually gets measured on
Your priorities land better when you can connect them to what they're accountable for. Ask directly if you don't already know, most managers have never been asked this and are happy to answer it. If you can't say what your manager is measured on this quarter, you're guessing at what matters to them.
02
Bring a recommendation when you raise a problem
Show up with a recommendation, even a rough one. It's easier for a manager to react to a proposal than to generate one from scratch on your behalf, and it changes how you're seen in the room, from someone who surfaces issues to someone who moves them forward. A rough recommendation beats a well described problem, every time. For the full system on what to surface and when, see Your Boss Never Gets Surprised →.
03
Ask for feedback before it becomes a review surprise
Don't wait for the formal cycle to find out what's not landing. Ask directly and often, a surprise in a review is usually a sign you weren't asking enough, not a sign the feedback came out of nowhere.
04
Say no when the ask doesn't make sense
Managing up includes protecting your own time and your team's. A well reasoned no builds more trust over time than silent overcommitment does, a manager who can predict your judgment trusts you with more, not less.
05
Send a weekly update, even if nobody asked for one
A manager who has to ask "what's going on with your team" has already lost visibility they should have had by default. A short, consistent update prevents that question from ever needing to be asked, and it's one of the cheapest ways to build trust that exists.
06
Name your projects so a stranger could follow them
A project called "Phase 2" means nothing to someone two levels up. A project called "Checkout Speed" gets remembered, referenced, and asked about later, which is most of what visibility actually is.
07
Celebrate wins loudly, not just inside the team
Recognizing your team privately is necessary but not sufficient. Say it in the update, say it in the channel your manager reads, say it where the people who decide what happens next can actually see it. A win only your team knows about didn't fully happen, as far as visibility goes.
A Simple Weekly Update
Wins: [what shipped or landed this week] In progress: [what's actively moving, and when it's expected] Blockers: [anything you need from someone above you] Coming up: [what's next]