In a recent LinkedIn post, Lenny Rachitsky discusses a concerning trend he’s observed in the tech industry: the potential dissolution of the product management role in favor of a “builder”-centric approach. Rachitsky, a prominent voice in the product and startup community, argues that this shift is a misguided one, potentially leading companies to discard valuable expertise and best practices.
The core of Rachitsky’s concern stems from the perceived abandonment of established product development methodologies. He highlights the risk of overlooking the accumulated knowledge and lessons learned within the product discipline.
“This whole discipline of product has been built up over the years, and has real best practices, and real things that have been tried and failed. That just gets abandoned because people are like, oh I wrote some code.”
The Erosion of Specialized Skills
Rachitsky emphasizes that specialized roles, including product management, are built on a foundation of unique skills and experience. He criticizes the notion that proficiency in one area, such as coding, automatically equips individuals to excel in entirely different disciplines.
According to Rachitsky, this oversight is a common failing among engineers who may not fully recognize the distinct skill sets required for various professional functions.
Challenging the “Builder” Mentality
The former OpenAI Codex app lead, whose insights were shared by Rachitsky, posits that companies are increasingly doing away with dedicated product roles, encouraging everyone to simply be a “builder.” Rachitsky counters this by drawing an analogy to other professional fields.
“Not everybody can work on everything. Every discipline has a skill component. Which a lot of engineers are guilty of not recognizing. Yes, you can use Excel, but you cannot work on the finance team.”
This analogy underscores Rachitsky’s argument that while individuals might possess basic familiarity with tools used in other departments, it does not equate to the specialized knowledge and strategic thinking required to perform effectively in those roles. He advocates for the continued recognition and value of distinct professional disciplines.
The Importance of Product Acumen
Rachitsky’s commentary serves as a strong defense of the product management discipline. He suggests that its established practices and historical learnings are crucial for navigating the complexities of product development and market fit.
As Rachitsky points out, the product role involves more than just technical execution; it requires a deep understanding of user needs, market dynamics, and strategic foresight—elements that are often honed through years of dedicated practice and learning from past failures.
“I think that’s a terrible idea.”
This direct quote encapsulates Rachitsky’s firm stance against the trend of devaluing product expertise. He implies that such a move could lead to suboptimal product strategies and missed opportunities, ultimately hindering a company’s long-term success.
The discussion, originally shared by Rachitsky, prompts a broader conversation about the evolving nature of tech roles and the enduring necessity of specialized expertise in driving innovation and building successful products.
📝 About This Content
This article is based on insights shared by Lenny Rachitsky on LinkedIn.
📅 Originally posted on July 3, 2026 | View original post on LinkedIn →