The headline stat that tells the story: Over 80% of product managers have experienced burnout, yet PM remains one of the most sought-after roles in tech. What's going on?
If you've ever felt confused about what product managers actually do—or if you're a PM drowning in impossible expectations—you're not alone. The industry has created a role that's simultaneously everywhere and nowhere, critically important yet fundamentally undefined.
This blog was compiled with the assistance of an AI Agent.
Product management exploded in popularity over the past decade. Glassdoor ranked it the 4th best job in the United States, McKinsey called it "the new training ground for future CEOs", and companies scrambled to hire PMs faster than they could define what PMs should actually do.
The result? A field flooded with people carrying the same title but doing completely different jobs. Recent job market data shows PM hiring down 14% in 2025, yet each posting still attracts hundreds of applicants. The market is simultaneously oversaturated and desperate for talent—because truly great PMs remain incredibly rare.
It's absurdly context-dependent. A systematic review identified 662 distinct PM tasks across 122 activities. That's not a job—that's a small department. What you do as a PM depends on your company size, industry, product stage, organizational maturity, and whether your executives even understand what PMs should be doing. Only 5.73% of studies even attempted to define the role for specific contexts.
It's still evolving. Product management only formally began in 1931. Unlike medicine or law with centuries of standardization, PM has transformed multiple times in less than a century—from brand management to cross-functional coordination to data-driven strategy to AI oversight. Each evolution added responsibilities without removing old ones.
It overlaps with everything. Is it Product Manager or Product Owner? PM or Project Manager? Who owns user research—PMs or UX? Research shows PMs and UX professionals fundamentally disagree on who should handle key responsibilities like product vision and feature prioritization. When nobody agrees on boundaries, chaos follows.
It has no professional standards. There's no required education, no universal certification, no regulatory body, no clear progression framework. Most PMs fall into the role from engineering, marketing, or design—each bringing different interpretations of what "product management" means.
Here's the dirty secret: the breadth of PM responsibilities is mathematically impossible for one person to master.
Product managers are expected to be experts in:
Technical: Software architecture, APIs, technical debt
Business: Financial modeling, pricing strategy, market analysis
Design: UX principles, user research, information architecture
Data: Analytics, A/B testing, statistical analysis
Leadership: Influence without authority, stakeholder management
Domain: Deep industry and customer knowledge
Oh, and AI fluency is now mandatory too.
The job operates on a brutal paradox: all responsibility, zero authority. PMs are accountable for product success but typically can't hire, fire, or directly control the teams they need. They lead through persuasion, not command—requiring exceptional soft skills on top of everything else.
Worse, PMs become organizational gap-fillers. No dedicated research team? PM does research. Designers won't handle strategy? PM fills the gap. Engineers won't talk to customers? PM becomes the liaison. Everything that doesn't fit elsewhere lands on the PM's desk.
The result? 43% of PMs report being overwhelmed, with 62% citing documentation and communication as their biggest time drains. A recent poll found over 80% of Digital Product Managers have experienced burnout at some point, and 66% of Senior Product Managers are actively seeking new jobs despite high salaries.
As one industry expert put it: "The Product role is demanding and often undefined. This means everything gets piled on to the Product Manager… so there's a lot of context switching… you can feel like you're always disappointing people and saying no".
Scarcity of true talent. The skills required—vision, technical understanding, business acumen, and interpersonal excellence—represent a rare combination that "can't be taught". The tech industry needed 100x more PMs than actually existed, so companies hired whoever they could find.
Organizational misunderstanding. Many companies, especially startups, fundamentally don't understand product management. They hire PMs but don't empower them with authority or resources. PMs are often first to go during budget cuts despite being positioned as strategic leaders.
The absence of Product Ops. Product Operations—the function that streamlines processes and supports PMs—is only recently emerging. Without this support layer, individual PMs handle both strategic thinking and operational grunt work.
Market immaturity. The hype cycle of 2015-2020 created oversupply of unqualified PMs through quick certification programs. By September 2024, open PM roles globally fell under 24,000, yet hundreds apply for each position. The market is crowded with mediocre PMs while excellent ones remain in short supply.
If you're a PM: You're not failing—the system is broken. The confusion and overwhelm are features, not bugs. Focus on what you can control: clear communication, ruthless prioritization, and building support networks. And seriously, watch for burnout signs.
If you're hiring PMs: Stop looking for unicorns. Decide what you actually need—strategy, execution, research, stakeholder management—then build a team with complementary strengths. Invest in Product Ops. Give PMs actual authority matching their responsibility.
If you're considering becoming a PM: Go in with eyes open. The role offers incredible impact and career growth (it really is a path to CEO). But it demands comfort with ambiguity, masterful communication, and the ability to influence without authority.
Product management isn't a fake profession, as some frustrated PMs claim. It's a real, critical role suffering from growing pains in a young industry. The confusion around responsibilities and the unrealistic burden on individual PMs are systemic issues rooted in rapid evolution, extreme context-dependency, organizational immaturity, and lack of professional standards.
The industry is slowly improving—Product Operations is emerging, executive recognition is growing, career frameworks are developing. But significant work remains to transform product management from a heroic individual endeavor into a sustainable, well-defined, properly supported profession.
Until then, expect the confusion to continue. Just remember: if you can't clearly define what a product manager does, you're in good company. Nobody else can either.