George from 🕹prodmgmt.world

1/ Most PMs think "managing up" means clearer updates and better alignment.

Wrong.

You’re treating your manager like a stakeholder instead of your highest-leverage product bet.

Flip this mindset, and everything changes.

Let me show you how in 2 minutes.

2/ you know how sometimes you need managing up frameworks that work from daily updates through strategic influence through organizational navigation? Complete PM System has end-to-end stakeholder management, decision documentation, and communication tools:

3/ The core issue isn't about "handling" your manager.

It's about creating *mutual leverage*:
• Your manager gets more done because of you
• You get more done because of your manager

Most PMs focus only on the second part. That's why they struggle.

4/ The best PMs understand a critical truth:

Your manager spends a few hours a week with you, hoping to generate 40+ hours of aligned, high-impact work.

When this breaks down, both sides get frustrated, and micromanagement creeps in.

Here's how to fix it.

5/ Start by reframing your role:
You are not just building products.
You are *extending your manager's capability* to impact the business.

This means you need to deeply understand:
• What keeps them up at night
• What metrics they're judged on
• What battles they're fighting

6/ Most PMs never ask.

The foundation of effective upward management is mastering what I call the "Proposal-Feedback Loop":

1. Always bring proposals, not questions
2. Get feedback to refine your thinking
3. Execute with clear communication
4. Return with results and next steps

7/ A junior PM once told me:
"But my manager just overrides my proposals anyway, so what's the point?"

The point isn't getting your way - it's demonstrating your thought process and learning from theirs.

8/ Starting with solutions builds decision-making muscles faster than asking for direction.

Technical PMs transitioning to strategic roles face a different challenge:

You're comfortable with "how" questions but struggle with "why" and "what" discussions.

9/ Your manager needs you to connect technical details to business outcomes, not the other way around.

This requires a mental model shift.

I spent 2 years as a PM showing architecture diagrams to my VP when what he needed was impact stories.

10/ The breakthrough came when I started every proposal with:

"Here's the business problem, here's how customers experience it, and here's why solving it matters financially."

THEN the technical details.

11/ For solo PMs at startups working under founders/CEOs:

The tension isn't about priorities - it's about creating structure in a chaotic environment.

Your manager probably has no PM experience and doesn't know how to use you effectively.

You must create the framework for

12/ One PM I worked with turned around a failing relationship with her CEO by implementing what she called "Decision Boundaries":

A simple one-pager outlining:
• Decisions she would make autonomously
• Decisions requiring alignment
• Decisions needing approval

Revisited

13/ The most underrated managing-up skill?
Knowing when to escalate problems vs. when to handle them yourself.

Too early: You seem dependent
Too late: Problems grow bigger
Just right: You demonstrate judgment

This balance shifts as you become more senior.

14/ My rule of thumb:

Escalate when:
• The problem affects multiple teams
• It threatens critical metrics/deadlines
• You've tried solutions that didn't work
• Political capital is needed
• It reveals a systemic issue

Otherwise, solve it and communicate afterward.

15/ Communication frequency creates another tension:

Your manager thinks about your work 5% of the time.
You think about it 90% of the time.

This asymmetry means you need to communicate more often than feels natural - but more efficiently than most PMs do.

16/ Master the "inverted pyramid" style:

1. Lead with the conclusion/request
2. Provide essential context next
3. Add details for those who want to dive deeper

This respects your manager's time while ensuring alignment.

17/ Focus on making your updates:
• Scannable
• Decision-oriented
• Future-focused (what's next?)
• Linked to business outcomes

18/ For high-stakes issues, resist the urge to communicate in writing alone.

Text loses nuance. A 5-minute conversation can prevent hours of back-and-forth and misunderstandings.

Follow up in writing to document decisions, not to make the initial case.

19/ As you become more senior, managing up evolves from tactical alignment to strategic influence.

You're no longer just executing your manager's vision. You're helping shape it.

This requires bringing insights they don't have and connecting dots they can't see.

20/ One powerful technique I've seen senior PMs use is the "Pre-1:1 Briefing":

Sending a short note 24 hours before your meeting with:
• What you want to discuss
• Decisions needed
• Context they should know

This primes them to have the right mental models ready.

21/ I've noticed PMs with technical backgrounds often struggle with the emotional aspects of managing up.

It feels like "politics" or "games."

But understanding human dynamics is just another system to master - one that's critical to your impact.

22/ The most successful PMs I've worked with recognize that managing up isn't about manipulation but about empathy and systems thinking applied to human relationships.

It's about making the whole greater than the sum of its parts.

23/ TL;DR: Effective managing up isn't about "dealing with" your manager - it's about creating mutual leverage.

• Bring proposals, not questions
• Connect work to business outcomes
• Create clear decision boundaries
• Master the timing of escalations
• Communicate

24/ I hope you've found this thread helpful.

Follow me @nurijanian for more.

Like/Repost the quote below if you can: