Does Your PM Really Need Industry Experience?

Why do so many companies prioritize a deep resume in banking or healthcare over actual product skills? Many hiring managers believe product management domain expertise is the secret sauce for success, but they're often looking in the wrong place. This preference usually leads to hiring people who know the past but can't invent the future.

Marty Cagan argues in Inspired that prioritizing industry tenure is a common hiring trap. While some highly specialized fields require deep background, most business problems need someone who can master the process of discovery. A manager who knows how to validate ideas with real users is always more valuable than one who relies on industry status.

Defining Domain Experience

Domain experience refers to the specific industry knowledge, like fintech or logistics, that a professional acquires over years of working within that sector. In his book Inspired, Marty Cagan explains that this is often the primary filter used by recruiters to find candidates. They assume a person from a similar background can skip the learning curve and start contributing immediately.

This background matters in the real world because it helps a person navigate complex regulations or technical constraints. However, Cagan points out that for about 80% of product roles, this knowledge is a secondary asset. The core of the job is not knowing the industry's history, but discovering a product that is valuable, usable, and feasible.

80% Rule of Product Management Domain Expertise

Cagan observes that the vast majority of skills required for the role are universal across different industries. These skills include running opportunity assessments, conducting user research, and collaborating effectively with engineers. A PM who excels in these frameworks can move from an infrastructure company to a consumer app without losing their effectiveness.

Blind Spots of the Industry Veteran

Deep expertise can actually become a liability if it creates mental rifts between the PM and the user. When a manager has spent a decade in one industry, they often fall into the trap of believing they are the customer. They stop asking "why" and start relying on their own assumptions instead of doing actual product discovery.

Veterans in a field are also more likely to be risk-averse, focusing on how things have always been done. They might miss a breakthrough technology because it doesn't fit the established implementation models they've used for years. Innovation usually comes from looking at an old problem with a fresh, inquisitive perspective.

Fast Paths to Learning New Product Domains

A talented technical product manager doesn't need years to master a new sector. Cagan notes that a sharp mind can usually come up to speed on the economics and constraints of a new domain within one to three months. They achieve this by aggressively studying the market and interviewing target customers rather than relying on a passive history in the field.

This learning process involves building a deep understanding of the customer's emotional triggers, such as fear, greed, or pride. By focusing on these core human drivers, a PM can see through the noise of industry jargon. They identify the underlying problems that existing products have failed to solve properly.

Real-World Examples

Cagan shares the story of a product leader named "David" who illustrates this principle perfectly. David was first hired as an infrastructure software expert, then moved into enterprise applications, and eventually succeeded in a large consumer internet firm. He wasn't an expert in any of those domains initially, but he was a master of product discovery.

In contrast, Cagan recalls his early days at HP working on a high-profile artificial intelligence product. The team spent a year building a $100,000 workstation that was technically impressive and backed by industry experts. It was a total failure because no one actually wanted it, proving that domain knowledge cannot replace the need for validating value.

Product Team Growth Without Industry Bias

1. Shift the interview focus away from industry history and toward problem-solving intelligence and product passion. Ask candidates how they would tackle a specific user struggle in a domain they know nothing about to see their thought process.
2. Connect every new hire with a "finance friend" who can teach them the specific economics and revenue models of the company within their first 30 days. Understanding where the money comes from is the fastest way to master a new business environment.
3. Mandate that every new product manager completes at least 15 direct customer visits or user interviews within their first month on the job. This forced immersion builds direct empathy and ensures their decisions are based on current evidence rather than outdated industry wisdom.

Where Industry Knowledge Still Wins

There are certain "edge cases" where industry expertise is truly essential for safety and compliance. If you are designing a life-saving medical device like a defibrillator, you need a manager who understands the nuances of cardiac care. In these high-stakes niches, a lack of deep domain knowledge can lead to dangerous errors.

Critics of Cagan’s view also argue that complete outsiders might waste time relearning basic industry pitfalls that a veteran would avoid. In highly regulated fields like legal tech or government contracting, the learning curve can be steep enough to stall a startup. However, even in these cases, the ability to learn and adapt remains the most critical long-term skill.

Hiring for industry knowledge over core product talent often results in safe, uninspired products. Real value comes from a manager who knows how to validate ideas and discover what users truly love. Hire for intelligence and the ability to product management domain expertise through discovery.

Assign one veteran team member to mentor a new hire on industry-specific jargon and regulations while letting the new hire lead the discovery process.