Key Takeaways
- • Keith Rabois, managing director at Khosla Ventures and veteran PayPal/Square executive, contends that the conventional product manager role "makes no sense" in the AI era due to rapidly changing technical capabilities that render year-long roadmaps obsolete.
- • Rabois argues that traditional PM functions—collecting customer inputs and sequencing them into organized roadmaps—are fundamentally misaligned with the current pace of AI capability improvements, where features shift from impossible to feasible within months.
- • The investor predicts the PM role is evolving into a CEO-like function focused on strategic decision-making and organizational alignment around "what to build and why," rather than tactical roadmap execution.
- • Rabois emphasizes that organizations must become "incredibly adept at changing the road map almost on the fly" as foundation model capabilities improve at rapid rates, making static annual planning cycles counterproductive.
- • The convergence of AI-assisted development tools (such as Lovable) with declining execution barriers suggests the traditional intermediary PM function is becoming redundant as developers gain capability to handle both building and customer context simultaneously.
Summary
Keith Rabois, a prominent venture capital figure at Khosla Ventures with substantial operating experience as an early PayPal executive, COO of Square, and VP of Corporate Development at LinkedIn, has publicly argued that the product manager role as traditionally constructed has become obsolete in the current AI-driven technology environment. Speaking on industry platforms, Rabois asserts that conventional PMs—whose primary function involves aggregating customer feedback and translating it into sequenced annual roadmaps—operate under a flawed model that no longer reflects market realities.
The core of Rabois's argument centers on the accelerating pace of capability change within foundation models and AI development tools. He contends that features and functionality considered impossible to build in November 2025 became relatively straightforward to implement by March 2026, rendering year-long product roadmaps strategically incoherent. In an environment where technical constraints dissolve at this velocity, static planning cycles lose relevance and organizations require the flexibility to pivot priorities continuously rather than execute against predetermined schedules.
Rather than predicting the outright elimination of PM expertise, Rabois suggests the role is undergoing fundamental transformation. He characterizes the evolved position as resembling that of a CEO—focused primarily on strategic judgment, determining organizational priorities (what to build and why), and aligning teams around those decisions. This represents a shift away from execution-oriented roadmap management toward higher-order strategic decision-making that AI tooling cannot easily replicate. The tension lies not in whether judgment is required, but in whether traditional PM organizational structures remain necessary to provide it.
A critical implication of Rabois's thesis involves the blurring of traditional role boundaries. As AI tools like Lovable enable rapid prototyping and reduce technical execution barriers, and as developers gain deeper customer context and product intuition, the distinctions between developer and PM functions narrow considerably. This convergence suggests that future organizations may consolidate these responsibilities rather than maintain them as separate functions with intermediary coordination requirements.
The core of Rabois's argument centers on the accelerating pace of capability change within foundation models and AI development tools. He contends that features and functionality considered impossible to build in November 2025 became relatively straightforward to implement by March 2026, rendering year-long product roadmaps strategically incoherent. In an environment where technical constraints dissolve at this velocity, static planning cycles lose relevance and organizations require the flexibility to pivot priorities continuously rather than execute against predetermined schedules.
Rather than predicting the outright elimination of PM expertise, Rabois suggests the role is undergoing fundamental transformation. He characterizes the evolved position as resembling that of a CEO—focused primarily on strategic judgment, determining organizational priorities (what to build and why), and aligning teams around those decisions. This represents a shift away from execution-oriented roadmap management toward higher-order strategic decision-making that AI tooling cannot easily replicate. The tension lies not in whether judgment is required, but in whether traditional PM organizational structures remain necessary to provide it.
A critical implication of Rabois's thesis involves the blurring of traditional role boundaries. As AI tools like Lovable enable rapid prototyping and reduce technical execution barriers, and as developers gain deeper customer context and product intuition, the distinctions between developer and PM functions narrow considerably. This convergence suggests that future organizations may consolidate these responsibilities rather than maintain them as separate functions with intermediary coordination requirements.
Go deeper than the headline
Research every firm in this story, track the ones that matter and get the daily briefing — free for 7 days.