Managing Up: Be the Co-Pilot, Not Just a Passenger

WHY IT EXISTS: In any hierarchy, your manager is the gatekeeper for resources, information, and opportunities. Simply doing your job well isn't enough; your work needs to be visible and aligned with what your manager and the organization value. Managing up was created to bridge this gap, turning a passive reporting relationship into an active, productive partnership.

THE MENTAL MODEL: Think of yourself as your manager's co-pilot. Your job is to help them succeed, which in turn helps you and your team succeed. This means understanding their priorities, pressures, and preferred communication style, and then proactively providing the information and support they need to make good decisions. It's about making their job easier, not just doing what you're told.

HOW IT WORKS: First, deeply understand your manager's goals, their key performance indicators (KPIs), and the pressures they face from their own boss. Second, learn their communication preferences: do they prefer a detailed email, a quick chat, or a formal document? Third, proactively communicate. Provide regular updates, flag potential risks early, and always bring solutions, not just problems. Frame your requests and updates in terms of how they help your manager achieve their goals.

WHEN TO USE IT: This skill is crucial for middle managers and individual contributors alike, especially in large organizations. Use it when you need to secure budget for a project, advocate for a promotion for a team member, get buy-in for a new technical direction, or simply ensure your daily work is aligned with what leadership considers important. It's a continuous process, not a one-time action.

WHEN NOT TO USE IT: Avoid using these techniques for purely political gain or to undermine others. Managing up is about mutual success, not manipulation. If your manager is unethical, managing up is not the tool; escalation or seeking a new role might be. It's also ineffective if it becomes simple flattery or constant, unhelpful communication that just creates noise.

ONE CANONICAL EXAMPLE: A software engineer notices that a critical library their team depends on will be deprecated in six months. Instead of just mentioning it in passing, she manages up. She writes a one-page brief for her manager outlining the risk, the impact on the product roadmap, and a proposed solution with a timeline and resource cost. This allows her manager to easily take the proposal to their director and secure the necessary resources, making both the engineer and the manager look proactive and competent.