Lesson 54: Managing Up and Across

Lesson 53 addressed negotiation and influence as a discipline applied to specific, often one-time asks — securing another team's engineering time, resolving a particular contentious decision. This lesson addresses something related but structurally different: the ongoing, ambient relationship management a PM maintains continuously with their own manager (managing up) and with peers across the organization (managing across), independent of any single specific request. These relationships are the accumulated context and trust that make Lesson 53's negotiation techniques work when they're actually needed — a PM who has never invested in the ongoing relationship has far less coalition support and goodwill to draw on when a specific, high-stakes ask arrives.

This lesson matters because many PMs treat their relationship with their own manager and peer stakeholders as something that simply happens in the background, rather than something to be actively and deliberately managed — and the PMs who manage these relationships well are consistently better positioned to get support, avoid unpleasant surprises, and navigate organizational friction than those who leave these relationships to develop passively. Managing up is not about flattery or manipulation; it's about proactively ensuring your manager has the information and context they need, adapted to how they actually prefer to receive it, before they have to ask for it.

Learning Objectives

1
Apply the "no surprises" principle to managing up, explaining why proactive disclosure of bad news preserves more trust than delayed or passive disclosure.
2
Adapt communication style to a specific manager's working preferences, using a structured working-styles framework rather than a one-size-fits-all approach.
3
Distinguish managing up (relationship with one's own manager) from managing across (ongoing peer relationships), and explain why each requires a distinct, deliberate maintenance practice.
4
Explain why ongoing peer relationship investment, maintained independent of any specific request, produces more durable cooperation than relationships activated only when something is needed.
5
Diagnose a damaged manager or peer relationship by identifying whether the root cause was a surprise, a style mismatch, or a purely transactional pattern of engagement.

This lesson assumes Lesson 47's power/interest grid and Lesson 51's Altitude Dial concept, since managing up is, in large part, applying those same audience-tailoring principles specifically and continuously to one's own manager. It also assumes Lesson 53's currencies of exchange model, since this lesson's treatment of peer relationships (managing across) extends that model from a single negotiation into an ongoing, maintained relationship.

The "No Surprises" Principle

The single most consequential practice in managing up is ensuring a manager never learns significant bad news about your work from someone else, or later than they reasonably should have. The no surprises principle means proactively surfacing problems, risks, and setbacks to your manager as soon as they're known with reasonable confidence, rather than waiting until a problem is fully resolved (hoping to present only good news) or until someone else raises it first. A manager who consistently learns about problems from a PM directly and early develops confidence in that PM's judgment and transparency; a manager who learns about the same category of problem from someone else, or well after the PM already knew, reasonably begins to wonder what else might be similarly withheld.

This directly extends Lesson 47's difficult-news framework, applied specifically and continuously to the manager relationship: delivering bad news directly, promptly, with clear reasoning, is not just a one-time technique for a specific difficult conversation — it's an ongoing discipline that defines how a manager relationship develops over time.

Adapting to a Manager's Working Style

Managers vary meaningfully in how they prefer to receive information and make decisions, and adapting to these preferences — rather than expecting a manager to adapt to a PM's own natural style — is a core managing-up skill. Some managers prefer detailed written updates they can read at their own pace; others prefer brief verbal check-ins and find long documents a burden. Some want to be looped into decisions early and often; others prefer to delegate broadly and be informed only at key checkpoints. Some communicate primarily through structured 1 meetings; others are more responsive to asynchronous, ongoing updates.

Style Dimension	Question to Ask (or Infer)
Detail preference	Does this manager want comprehensive detail, or a high-altitude summary with detail available on request?
Format preference	Does this manager engage more with written documents, verbal conversation, or a combination?
Involvement preference	Does this manager want to be consulted early and often on decisions, or prefer broad delegation with periodic checkpoints?
Timing preference	Does this manager prefer scheduled, structured updates, or ongoing, as-needed communication?

Adapting to a manager's actual preferences along these dimensions — rather than communicating in whatever style feels most natural to the PM personally — tends to produce a smoother, more trusting relationship, echoing this curriculum's repeated emphasis (Lesson 47, Lesson 51) on tailoring communication to the actual audience rather than a single default style.

Managing Across: The Ongoing Peer Relationship

Managing across refers to the deliberate, ongoing maintenance of relationships with peers — other PMs, cross-functional partners, adjacent team leads — independent of any specific, immediate request. This extends Lesson 53's currencies of exchange model from a single negotiation into a sustained practice: a PM who regularly checks in with peer teams, offers help proactively, and maintains visibility into their priorities and pressures — even when nothing specific is currently needed from them — builds a reserve of goodwill and mutual understanding that makes any future specific request (exactly the kind of negotiation Lesson 53 covers) far more likely to succeed.

A PM who only reaches out to a peer team when they need something specific — never otherwise investing in the relationship — is, in effect, attempting to draw on a currency-of-exchange account they've never actually deposited into, and should not be surprised when that account has little goodwill available when it's finally needed.

Common Mistakes to Avoid

Waiting to disclose bad news until it's fully resolved, hoping to present only good outcomes

As covered in Theory, this risks a manager learning about the underlying problem from someone else, or learning that it existed for longer than they were told, both of which damage trust more than the original bad news itself would have.

Communicating with a manager in whatever style feels most natural to the PM, rather than adapting to the manager's actual preferences

A detail-oriented PM working for a manager who strongly prefers high-altitude summaries (or vice versa) creates friction that has nothing to do with the substance of the work, simply because the communication format doesn't match the manager's actual needs.

Only engaging with peer teams transactionally, when something specific is needed

As covered in Theory, this produces a one-sided relationship pattern that peers reasonably notice, making future requests less likely to succeed than they would be with a peer relationship maintained through ongoing, non-transactional investment.

Assuming a manager's working style preferences are fixed and identical to a previous manager's

A PM moving to a new manager, or a manager changing roles, should actively re-assess working style preferences rather than assuming continuity — applying an old manager's preferred style to a new manager risks the exact mismatch Mistake 2 describes.

Treating managing up as flattery or telling a manager only what they want to hear

This confuses managing up with ingratiation — genuine managing up is about ensuring accurate, timely, well-adapted communication, including uncomfortable information, not about curating an artificially positive picture that will eventually be contradicted by reality.

Mental Model

The Manager Operating Manual

This lesson's core takeaway tool is a structured practice for documenting and applying a specific manager's actual working preferences, rather than relying on assumption or a generic default approach:

Use the Manager Operating Manual as a standing practice: rather than guessing at a manager's preferences indefinitely, ask directly (most managers respond well to a direct question like "how do you prefer to receive updates — detailed written docs, or brief verbal check-ins?") and revisit the answer periodically, since preferences can shift as trust builds or circumstances change, and since a new manager should never be assumed to share an old manager's exact preferences.

Quick Reflection Checkpoint

Key Takeaway: How will you apply "The Manager Operating Manual" when evaluating trade-offs in your product decisions?

Managing Up and Across