The Short Answer
The biggest PM challenge is influence without authority—you own the outcomes but work through people who do not report to you—and the solution is transparency, relationship-building, and clear prioritization frameworks.
Most PMs cite influence without authority as the hardest part of the job—being accountable for outcomes while working through people who do not report to you. The fixes are relational, not positional: transparent prioritization frameworks, early stakeholder involvement, proactive communication, and delivering quick wins to build credibility.
Key Takeaways
| Detail | At a Glance | Notes |
|---|---|---|
| Hardest Challenge | Influence without authority | Accountable for outcomes, no direct reports |
| Stakeholder Conflicts | Transparent prioritization | Share framework; involve them in tradeoffs |
| Scope Creep | Frame as tradeoffs | Lock scope upfront; "add X if we cut Y" |
| Building Credibility | Listen, then quick wins | Be reliable; ask good questions |
| Missing Deadlines | Communicate early | Offer options; run blameless retros |
Stakeholder Alignment
Regular roadmap reviews, data-driven decisions
Saying No
Prioritization frameworks (RICE, ICE), transparent criteria
Scope Creep
Clear PRDs, change request process, MVP mindset
Cross-functional Friction
Shared OKRs, empathy mapping, regular syncs
Data Overload
North star metrics, focused dashboards, weekly reviews
Imposter Syndrome
Document wins, seek mentors, continuous learning
The Nature of PM Challenges
Product management is inherently challenging because you're at the intersection of multiple functions with different priorities, timelines, and success metrics. You have responsibility for outcomes but limited direct control over execution.
The good news: these challenges are predictable. Every PM faces them, which means there's accumulated wisdom on how to navigate them effectively. This guide synthesizes that wisdom into practical strategies you can apply immediately.
Each challenge section includes the core problem, proven solutions, and common antipatterns to avoid. Focus on the challenges most relevant to your current situation, and revisit others as you encounter them.
Stakeholder Management
Competing stakeholder demands
Sales wants feature A, marketing wants feature B, engineering wants technical debt reduction.
✓Solutions
- Create a transparent prioritization framework everyone understands
- Run regular stakeholder prioritization sessions with real tradeoffs
- Build relationships before you need them
- Document decisions and reasoning for reference
✗Antipatterns
- Promising everything to everyone
- Making decisions in private without context
- Avoiding difficult conversations
Executive misalignment
Leadership gives conflicting direction or frequently changes priorities.
✓Solutions
- Seek clarity on company strategy and how your product fits
- When direction conflicts, ask "help me understand the priority between X and Y"
- Document agreed priorities and reference them when challenged
- Build direct relationships with executives where possible
✗Antipatterns
- Assuming you can please everyone
- Not pushing back on unrealistic expectations
- Taking every pivot personally
The HiPPO problem
Highest Paid Person's Opinion overrides customer data and research.
✓Solutions
- Bring data proactively—don't wait to react
- Frame recommendations in terms of business outcomes, not opinions
- Run experiments to validate hypotheses
- Build credibility through past successes
✗Antipatterns
- Simply acquiescing to opinions
- Being confrontational without data
- Not understanding their underlying concerns
Prioritization & Saying No
Everything is urgent
Unable to focus because everything seems equally important or urgent.
✓Solutions
- Force-rank everything—nothing can share position 1
- Ask "what would happen if we didn't do this?"
- Distinguish urgent from important
- Get executive alignment on true top priorities
✗Antipatterns
- Working on whatever is loudest
- Starting many things, finishing few
- Avoiding the prioritization conversation
Saying no damages relationships
Fear of disappointing stakeholders leads to overcommitment.
✓Solutions
- Say "not now" instead of "no"—put requests on visible backlog
- Explain the why: "Here's what we're prioritizing and why"
- Offer alternatives that might address underlying needs
- Follow up when priorities change and requests become feasible
✗Antipatterns
- Saying yes to everything then underdelivering
- Being dismissive or not acknowledging valid needs
- Hiding behind "engineering said no"
Balancing quick wins vs. big bets
Tension between shipping incremental improvements and pursuing transformative work.
✓Solutions
- Allocate capacity explicitly: 70% core, 20% adjacent, 10% experimental
- Define success criteria for big bets before starting
- Use quick wins to build credibility for bigger investments
- Kill underperforming big bets early
✗Antipatterns
- Only doing quick wins (death by incrementalism)
- Only doing big bets (nothing ships)
- Not having explicit allocation philosophy
Cross-Functional Collaboration
Engineering pushback on requirements
Engineers question the value of features or resist implementation.
✓Solutions
- Include engineers early in problem discovery, not just solution delivery
- Share customer context and business rationale
- Listen to technical concerns—they often reveal real constraints
- Build relationship outside of requirements discussions
✗Antipatterns
- Treating engineers as implementation resources
- Dismissing technical concerns as resistance
- Going around engineering to leadership
Design disagreements
PM and design have different visions for the solution.
✓Solutions
- Align on problem definition before solutions
- Let design lead on how, while PM defines what and why
- Use customer data to resolve subjective disagreements
- Build relationship through collaboration, not handoffs
✗Antipatterns
- Overriding design decisions with PM opinion
- Not involving design early enough
- Treating design as pixel-pushers
Working with remote/distributed teams
Collaboration challenges across time zones and locations.
✓Solutions
- Over-document decisions and context
- Find overlap hours for synchronous critical discussions
- Use async communication effectively (Loom, detailed docs)
- Build relationship through regular video touchpoints
✗Antipatterns
- Expecting real-time availability across time zones
- Making decisions in hallway conversations
- Not adapting communication style for async
Influence Without Authority
Getting buy-in for your ideas
Difficulty convincing others to support your product direction.
✓Solutions
- Involve stakeholders in problem discovery—co-creation builds ownership
- Build the case with data, not opinion
- Find champions who can advocate with you
- Address concerns directly rather than avoiding them
✗Antipatterns
- Presenting fully-formed plans and expecting agreement
- Not understanding others' constraints and motivations
- Relying on authority (yours or borrowed) vs. persuasion
Leading without direct reports
Being responsible for outcomes while not having formal authority over the team.
✓Solutions
- Lead with context and vision, not directives
- Make others successful—help them achieve their goals
- Build trust through reliability and competence
- Recognize and celebrate team contributions publicly
✗Antipatterns
- Acting like a manager when you are not
- Not respecting actual reporting relationships
- Taking credit for team accomplishments
Dealing with organizational politics
Navigating complex power dynamics and competing agendas.
✓Solutions
- Understand the landscape: who has power, what are their goals
- Build relationships broadly, not just with your immediate team
- Stay focused on customer and business outcomes
- Avoid being drawn into factional conflicts
✗Antipatterns
- Pretending politics do not exist
- Becoming overly political yourself
- Burning bridges unnecessarily
Execution Challenges
Scope creep
Projects expanding beyond original boundaries.
✓Solutions
- Define MVP clearly upfront with stakeholder alignment
- When new requests come, frame as tradeoffs explicitly
- Maintain visible backlog so additions are clearly additions
- Build change request process for significant scope changes
✗Antipatterns
- Accepting "just one more thing" repeatedly
- Not having clear scope documentation
- Letting scope creep then surprising stakeholders
Missed deadlines
Projects consistently taking longer than estimated.
✓Solutions
- Communicate risks early—as soon as you see them
- Build buffer into estimates for unknowns
- Run retrospectives to improve estimation over time
- Cut scope before extending timelines when possible
✗Antipatterns
- Waiting until deadline to communicate delays
- Blaming engineering for estimates
- Not tracking actuals vs. estimates to learn
Technical debt accumulation
Pressure to ship features prevents addressing underlying problems.
✓Solutions
- Allocate explicit capacity for tech debt (e.g., 20%)
- Translate tech debt to business risk for stakeholders
- Prioritize debt that blocks future work
- Build quality into definition of done
✗Antipatterns
- Ignoring tech debt until crisis
- Treating tech debt as engineering's problem alone
- Promising features without considering tech health
Career & Growth Challenges
Imposter syndrome
Feeling unqualified or like a fraud despite success.
✓Solutions
- Recognize PM requires breadth—you are not meant to be expert in everything
- Track your wins and impact to reference when doubting
- Talk to other PMs who share the experience
- Focus on continuous learning rather than proving competence
✗Antipatterns
- Overcompensating by acting overly confident
- Avoiding challenges that might expose gaps
- Not asking for help when needed
Unclear career progression
Difficulty understanding how to advance as a PM.
✓Solutions
- Seek explicit feedback on growth areas
- Find mentors who have navigated similar paths
- Take on stretch projects that build new skills
- Document your impact for promotion discussions
✗Antipatterns
- Waiting to be noticed rather than advocating
- Assuming tenure equals promotion
- Not having career conversations with manager
Gaining credibility as a new PM
Building trust when joining a new team or company.
✓Solutions
- Listen first—spend initial weeks learning, not proposing
- Deliver quick wins to build trust
- Acknowledge what you do not know and learn from team
- Show curiosity about others' expertise and context
✗Antipatterns
- Coming in with all the answers
- Criticizing past decisions without context
- Trying to change too much too fast
Framework for Any Challenge
While each challenge has specific tactics, a consistent framework helps you approach any new PM challenge:
Understand the perspective
Before reacting, understand others' constraints, motivations, and pressures. Most conflicts stem from different contexts, not bad intentions.
Find common ground
Identify shared goals (customer success, business outcomes, team wellbeing). Frame solutions in terms of mutual benefit.
Use data over opinion
When possible, let data inform decisions. "Let's test this" is often better than "I think this."
Communicate proactively
Over-communicate context, decisions, and reasoning. Most problems are information problems.
Build relationships before you need them
Invest in relationships during good times so you have trust to draw on during conflict.
Learn from patterns
If the same challenge keeps recurring, address the system not just the symptom.
Frequently Asked Questions
What is the hardest part of being a PM?
Most PMs cite "influence without authority" as the hardest part—you are responsible for outcomes but must work through others who do not report to you. This requires exceptional communication, relationship-building, and the ability to create alignment without positional power. Close seconds include prioritization (saying no) and managing competing stakeholder demands.
How do I handle stakeholders who always want their features prioritized?
Create transparency around prioritization: share your framework, show the full list of requests, and explain tradeoffs. Involve stakeholders in prioritization discussions so they understand constraints. Build relationships outside of conflict moments. When saying no, offer alternatives (timing, scope, or different solutions). Track requests and follow up.
How do I gain credibility as a new PM?
Start by listening and learning—avoid coming in with all the answers. Deliver quick wins to build trust. Demonstrate that you understand the customer, business, and technical realities. Be reliable: do what you say you will do. Ask good questions rather than having all the answers. Show curiosity about others' expertise.
How do I deal with scope creep?
Set clear scope at project start and get stakeholder sign-off. When new requests come in, frame as tradeoffs: "We can add X if we cut Y or extend timeline." Maintain a visible backlog so additions are clearly additions. Resist "just this one small thing" that accumulates. Build buffer into estimates for legitimate discoveries.
How do I work with a difficult engineering lead?
First, understand their perspective and motivations—often "difficult" stems from misalignment or past frustrations. Find common ground (both want to ship quality products). Include them early in problem definition. Respect their technical expertise while holding your ground on customer value. Build the relationship outside of conflict moments. If truly dysfunctional, escalate appropriately.
How do I handle missing deadlines?
Communicate early—as soon as you see risk, not when the deadline passes. Explain what changed and why. Present options: cut scope, extend timeline, or add resources. Take ownership while being honest about causes. After the fact, conduct a blameless retrospective to prevent recurrence. Build more accurate estimation practices over time.
How do I manage up effectively?
Understand your manager's priorities, communication preferences, and pressures. Keep them informed proactively—no surprises. Bring solutions, not just problems. Make their job easier by handling what you can independently. Ask for feedback and act on it. Understand how they are evaluated and help them succeed.
How do I handle imposter syndrome as a PM?
Recognize that imposter syndrome is especially common in PM because the role requires breadth without deep expertise in any one area. Focus on your unique contributions: customer insight, problem framing, facilitation. Accept that you will not have all the answers—your job is to find them, not know them. Talk to other PMs who share the experience.
About the Author
Aditi Chaturvedi
·Founder, Best PM JobsAditi is the founder of Best PM Jobs, helping product managers find their dream roles at top tech companies. With experience in product management and recruiting, she creates resources to help PMs level up their careers.