06:41
product management
Being "product led" is not a universal goal a company should chase — a PM's real job is product and business success, and for most individual-contributor PMs at large, old, bureaucratic companies, trying to make the org product led is a waste of energy; only senior leaders willing to spend personal career capital can actually drive that kind of change.
Product led is not always the right answer for a company; the PM's job is to make the product successful, not to convert the organization into a product-led one.
Many highly successful companies are not product led — Oracle and Salesforce are given as examples, and these are not rare exceptions.
Google was product- and user-focused but was engineering led, not PM led, for roughly its first 15 years; PMs supported, they did not lead.
At Google, if you disagreed with your engineering manager, the engineering manager won; dissenters weren't fired but were given bad ratings.
Google has been tremendously successful despite (or alongside) being engineering led rather than PM led, though it lost its product-and-user focus in the later part of its journey.
Product led is not the goal — product success and business success are the goal; product-ledness is sometimes a path to that, sometimes not.
An individual-contributor PM inside a huge, old, bureaucratic company (e.g., a 50,000-person telco or bank) cannot make that company product led, and no amount of complaining will change that.
Concrete examples given: a PM at General Motors or Bank of America cannot make those 100+-year-old companies product led — it's not going to happen.
Phrases like "we need better processes," "we need to be product led," and "we need to be more customer-obsessed/customer-oriented" are always-true statements anyone can say in any meeting with zero context and get nodding agreement.
Being right that a company needs to be more product led doesn't mean the company will change, because it also needs 60 other things, and everything involves trade-offs.
Only a senior leader within the company actually has the ability to make the company product led, and the mechanism is convincing the senior executive team that a change is needed — that is the only way.
Marty Cagan's book "Transform" is recommended as the resource for the specific tactics of moving a company from not-product-led to adopting product-led practices and principles.
Driving this kind of change requires a senior leader to put their personal reputation on the line and take real career risk to convince the CEO, executive team, and board.
Doshi says he would take that risk himself if he truly believed it was what the company needed, but flags it as high-risk.
For an IC PM who dislikes a non-product-led environment, the recommended path is: learn what you can for a few years, upgrade your skills to the right levels, then move to a company that actually understands how to do product well.
IC PMs can still make their own team more product led, even if they can't change the whole company — that is where Doshi says they should focus their energy.
The one point Doshi says doesn't usually get shared: product led is not the goal, and for an individual-contributor PM the pursuit of it is useless anyway.
Doshi separates "product led" from "PM led" as distinct axes — Google is his proof case that a company can be deeply product- and user-focused while being engineering led rather than PM led, which cuts against the common conflation of the two terms.
He categorizes "we need to be product led" in the same rhetorical bucket as "we need better processes" and "we need to be more customer-obsessed" — statements that are always true and always win nodding agreement in a meeting, which is exactly why their truth doesn't imply the company will or should act on them given competing trade-offs.
He inverts the common advice given to IC PMs (advocate for change, push for product-led culture) by calling it a waste of energy with zero leverage, redirecting effort instead toward improving one's own team or leaving for a better-fit company.
He reframes organizational transformation toward product-led practices as fundamentally a political/executive-sponsorship problem — requiring seniority and willingness to risk one's career and reputation — rather than a matter of methodology, conviction, or bottom-up advocacy.
He notes Google's later loss of its product-and-user focus as a caveat even to his own positive example, suggesting that a company's product culture can erode over time independent of whether it was ever PM led.
«Not every company has to be product led.»
— 00:53
«So, Google was engineering led. It was not PM led. But at Google, always thought about the product and the user.»
— 01:41
«the point is product led is not the goal. Product success and business success is the goal.»
— 01:35
«There is nothing you can do to change it.»
— 02:44
«If you work for General Motors and you work on some website or some procurement product or something else, I'm sorry, you're not making General Motors, which is more than 100 years old, product led. It is not going to happen.»
— 03:13
«We need to be product led is another such thing.»
— 04:09
«just because you're right doesn't mean this company is going to change because there are 60 other things this company also needs. And it all comes with trade-offs.»
— 04:22
«Your job will be to convince the very senior executive team that a change is needed. That is the only way.»
— 04:42
«product led is not the goal. If you're an individual contributor PM, it's useless anyway.»
— 05:48
«learn what you can in that environment for a few years. Upgrade your skills, figure out your LMS, upgrade your skills to the right levels, and then go to a company that actually understands how to do product better.»
— 05:54
Reception
Comments are neutral and clarifying rather than evaluative, with no clear positive or negative sentiment toward the video itself.
This is a deliberately contrarian corrective to the common online advice that PMs should push their organizations to become product led, aimed specifically at recalibrating where IC PMs spend their effort versus where senior leaders might justifiably spend political capital.
06:41