The definition of the product management or product ownership role has long been a subject of extensive debate and varied interpretation across the technology industry. Over decades, countless organizations have attempted to distill this complex function into concise job descriptions and pithy catchphrases, often leading to a kaleidoscope of responsibilities and skill sets. This definitional fluidity stems partly from the diverse operating models employed by companies—ranging from startups to multinational corporations, and encompassing consumer, enterprise, and platform products—each demanding a nuanced approach from its product leaders.
The Elusive Definition of Product Management
The product management discipline, while relatively modern in its current form, traces its roots back to the "brand man" concept at Procter & Gamble in the 1930s, evolving significantly with the advent of software and digital technologies. Early software companies like Microsoft formalized the role, tasking product managers with understanding customer needs, defining product specifications, and guiding development. The rise of Agile methodologies in the early 2000s further complicated matters, introducing the "Product Owner" role, often overlapping or conflating with Product Manager responsibilities, depending on organizational structure and interpretation.
Industry observers frequently note that asking a product professional to define their role can serve as a Rorschach test, revealing their background, the operational model they’ve experienced, their understanding of the role’s purpose, and its perceived contribution to a product team. This diagnostic quality highlights the lack of a universal standard, making it challenging for both practitioners and hiring managers to establish clear expectations and career paths.
According to a 2023 report by ProductPlan, over 70% of product managers cited "lack of clear strategy" or "conflicting priorities" as major challenges, underscoring the necessity for a well-defined and strategically aligned product function. LinkedIn data consistently shows product management as one of the fastest-growing job categories, with a projected demand increase of 12-15% over the next decade. This growth, however, amplifies the need for clarity in a role that commands significant influence over a company’s strategic direction and financial success, with average salaries reflecting its strategic importance.
The AI Revolution and the "Product Creator" Myth
The advent of advanced artificial intelligence (AI) and readily accessible no-code/low-code development tools has injected a new layer of complexity into this ongoing definitional challenge. Initial optimism suggested that these technologies would democratize product creation, empowering a broader demographic of "citizen developers" and "prompt engineers" to build solutions without extensive technical expertise. This vision, encapsulated in concepts like "The Era of the Product Creator," posited that enhanced tools would lower the barrier to entry for product discovery and delivery, leading to an explosion of new solutions from a wider array of individuals.
However, recent analyses suggest that while AI undeniably enhances the capabilities of existing product professionals, it does not fundamentally alter the core competencies required for successful product creation. The perceived ease of tool usage often masks the profound strategic and conceptual challenges inherent in identifying genuinely valuable and viable solutions. This distinction forms the crux of an insightful observation from technology industry analyst Benedict Evans.
Benedict Evans’ Illuminating Perspective
Benedict Evans, a highly respected voice in the broader tech landscape known for his incisive analysis of industry trends, recently offered a perspective that, while not explicitly defining the product role, provides one of the most compelling descriptions of the essential responsibilities and skills of a product manager in the AI era. His article, "Most People Aren’t Tool Builders," and its accompanying podcast discussion, delves into why, despite widespread access to powerful new tools—whether for "vibe-coding" applications or automating workflows with AI agents—most users are unlikely to successfully create their own solutions.
Evans’ central argument posits that the barrier to creation is not primarily the availability or complexity of tools, but rather a fundamental difference in mindset and skill set between a typical user and an effective tool builder. This distinction, though not directly focused on product management, profoundly illuminates the enduring necessity and unique value of the product role.
Dissecting the Core Product Skills
Evans implicitly outlines three distinct and critical skills that characterize effective product professionals, skills that remain vital regardless of technological advancements:
-
Problem Discovery and Generalization: Many individuals can articulate specific pains they experience or propose ideas for immediate remedies. However, a crucial skill—often cultivated over years of practice—is the ability to transcend these individual instances to identify the underlying, more general problem that needs solving. This involves stepping back from a single symptom to diagnose the systemic issue, recognizing patterns, and understanding the broader context of user needs. For instance, a user might complain about a cumbersome reporting process, but a skilled product person would generalize this to an unmet need for actionable data insights, applicable across various departments or user segments. This aligns directly with what product practitioners recognize as problem discovery—the foundational phase of truly understanding customer needs before jumping to solutions.
-
Solution Discovery and Value Risk Assessment: Evans highlights a critical divergence: "People that are really good at using the tool are not the same people as those that are really good at creating the tool." He illustrates this with the example, "You have to know a lot about sales to make good sales software, but being good at sales does not make you good at making sales software." This distinction underscores that domain expertise, while valuable for understanding problems, does not automatically translate into the ability to design effective solutions. Building a tool requires a different cognitive approach—one focused on abstraction, system design, user experience, and the iterative process of solution validation. This skill directly addresses the value risk in solution discovery: ensuring that a proposed solution genuinely provides measurable benefit and solves the identified problem in a way that users will adopt and find valuable. It involves not just building something, but building the right thing that addresses a real need effectively.
-
Business Viability and Holistic Solution Design: Beyond discovering a strong, customer-centric solution, an effective product person must possess the depth and breadth of understanding of their own company to ensure the solution is also viable for the business. This encompasses navigating a complex internal landscape where solutions invariably touch various departments—sales, marketing, finance, compliance, legal, operations, and customer support. A viable solution must consider regulatory requirements, integrate with legacy systems, align with existing business models, and fit seamlessly into diverse organizational workflows. Overlooking these internal constraints can lead to technically sound products that fail commercially or operationally. This third skill directly addresses the viability risk of solution discovery: ensuring that the solution is not only desirable for users and technically feasible, but also sustainable and profitable for the business, aligning with its strategic objectives and operational realities.
The Enduring Value of the Product Professional
Evans’ observations underscore that these three interconnected skills—problem generalization, effective solution design (value), and business viability (viability)—are rarely found in isolation and even less frequently in combination within the general populace. While they may not be exclusive to product professionals, their concentrated presence is a hallmark of the role.
The author of the original article acknowledges a previous misjudgment, having initially celebrated the "Era of the Product Creator" with the assumption that improved tools would naturally foster more product creators. Evans’ analysis serves as a crucial corrective, emphasizing that the issue isn’t merely the tools, but the underlying cognitive framework and specialized craft of product thinking. The ability to identify an opportunity, translate it into a compelling solution, and navigate the complexities of bringing it to market requires a unique blend of strategic foresight, analytical rigor, empathy, and organizational acumen.
Strategic Implications for Industry
The insights from Benedict Evans carry significant implications for how companies approach product development, talent acquisition, and organizational strategy in the AI era:
-
Hiring and Talent Development: Organizations must prioritize candidates who demonstrate these core product skills—strategic problem-solving, value creation, and business acumen—over mere technical proficiency or domain knowledge. Training programs should focus on cultivating these foundational abilities, moving beyond tool-centric instruction to emphasize critical thinking, user research, and cross-functional collaboration. Recruitment specialists and industry analysts concur that the demand for product leaders who can translate complex technical capabilities into tangible business value is at an all-time high, irrespective of the underlying technology stack.
-
Organizational Structure and Collaboration: The product role remains central to bridging the gap between customer needs, technological possibilities, and business objectives. Product managers serve as the "mini-CEOs" or "glue" within product teams, orchestrating efforts across engineering, design, marketing, and sales. Their capacity to identify and articulate problems, de-risk solutions for both value and viability, and align diverse stakeholders becomes even more crucial in an environment where AI offers seemingly limitless technical possibilities.
-
Reframing the AI Opportunity: For many companies, the immediate challenge is not how to build with AI, but what to build with it. Evans’ argument reiterates that AI changes the "thresholds" of what’s possible and how quickly it can be achieved, but it does not change the fundamental "problem" of knowing that a tool should exist and how it should exist. This critical foresight and strategic direction remain firmly within the purview of the product leader. Industry leaders like Satya Nadella of Microsoft have consistently emphasized that AI is a powerful co-pilot, not a replacement for human ingenuity and strategic direction, particularly in areas requiring deep market understanding and business acumen.
In conclusion, Benedict Evans’ "Most People Aren’t Tool Builders" serves as a powerful reminder of why the product role is not only essential but likely to remain so, even as AI reshapes the technological landscape. While AI tools empower individuals with unprecedented capabilities, they do not inherently instill the strategic mindset, problem-solving prowess, and holistic business understanding that define a truly effective product professional. The ability to discern a generalized problem, craft a valuable solution, and ensure its business viability will continue to be the cornerstone of successful product creation, solidifying the product manager’s indispensable position at the heart of innovation.
