The product management profession, a cornerstone of innovation in the technology sector and beyond, has long been characterized by a perplexing diversity in its definition. For decades, industry observers and practitioners have grappled with myriad interpretations of what precisely constitutes the "product role," encompassing titles like Product Manager and Product Owner. This definitional fluidity is not merely an academic exercise; it reflects the dynamic nature of the product landscape, influenced by evolving operating models, technological advancements, and the perpetual quest for succinct yet comprehensive descriptions of complex responsibilities. Recent insights from prominent technology analyst Benedict Evans, though not directly aimed at defining the product role, offer a remarkably trenchant framework for understanding the essential skills of product leadership, particularly pertinent as artificial intelligence reshapes the contours of creation and problem-solving.
A History of Definitional Flux: The Product Management Rorschach Test
The inherent ambiguity surrounding the product role is deeply rooted in its history. Originating in the brand management practices of consumer packaged goods companies in the mid-20th century, the concept of a "product manager" evolved significantly with the advent of software development. Early iterations often saw product managers acting as project coordinators, bridging the gap between engineering and sales. With the rise of Agile methodologies in the early 2000s, the "Product Owner" role emerged, often focused on backlog management and tactical execution within development sprints. Simultaneously, the "Product Manager" role expanded to encompass broader strategic responsibilities, including market analysis, user research, and defining product vision.
This evolution has led to a fragmented understanding. A 2023 survey by ProductPlan indicated that while 85% of product leaders believe their role is critical to company success, only 30% feel their company fully understands their responsibilities. This disparity underscores the internal challenge of communicating the product manager’s value proposition. Asking a product professional to define their role often serves as a "Rorschach test," revealing their unique experiences, the organizational models they’ve navigated, and their personal emphasis on what drives product success. Some might highlight market strategy, others user empathy, and still others, technical oversight. This kaleidoscope of perspectives, while rich, contributes to the ongoing challenge of establishing a universally understood and valued role.
The AI Revolution: Lowering Thresholds, Not Problems
The current era, dominated by the rapid acceleration of artificial intelligence, particularly generative AI and no-code/low-code platforms, introduces a new layer of complexity and optimism. There has been a prevailing sentiment, sometimes celebrated as "the era of the product creator," that these powerful new tools would democratize product development, enabling virtually anyone to conceive, build, and deploy solutions with unprecedented ease. The allure of "vibe-coding" an application or automating workflows with intelligent agents suggests a future where the technical barriers to creation are dramatically diminished, empowering a broader demographic to become "tool builders."
However, this optimism, while partially valid in terms of technical accessibility, risks overlooking a fundamental truth about human capabilities and organizational dynamics. Benedict Evans, a respected independent technology analyst known for his astute observations on industry trends and market forces, offers a crucial counter-narrative. In his article, "Most People Aren’t Tool Builders," and a subsequent podcast discussion, Evans posits that while AI profoundly alters the thresholds for building, it does not fundamentally change the problem of creating valuable and viable products. His core argument challenges the notion that widespread access to advanced building tools automatically translates into widespread successful tool creation. Evans argues that the critical skills required to identify what should be built and how it should exist remain specialized and distinct from the mere ability to manipulate creation tools.
Benedict Evans’s Framework: Three Pillars of Product Leadership in the AI Era
Evans, despite not being a "product person" in the traditional sense, articulates an implicit definition of the product role that resonates deeply with experienced practitioners. His analysis, rooted in observing the broader tech industry, highlights three distinct, yet interconnected, skill sets that differentiate effective product leaders from typical users or even proficient tool operators. These skills are foundational, and their scarcity explains why the product role remains indispensable, even as AI simplifies execution.
1. The Art of Problem Discovery: Beyond Symptoms to Systemic Issues
The first critical skill identified by Evans is the ability to transcend superficial pain points and discern the underlying, more generalized problems that merit solving. Many individuals can recognize a specific frustration or have an idea for a feature that addresses a singular annoyance. However, true product leadership lies in the capacity to abstract from these individual instances to identify a broader, systemic challenge that, when addressed, can unlock significant value for a larger user base or market segment.
For instance, a customer might complain about the tediousness of manually entering data into a spreadsheet. A less experienced approach might focus on automating that specific data entry task. A product leader, guided by Evans’s first principle, would delve deeper: Why is this data being entered? What decisions does it inform? Are there other manual processes upstream or downstream? Is the root problem a lack of data integration across systems, an absence of real-time insights, or a flawed workflow design? This process of "problem discovery" involves deep empathy, rigorous user research, market analysis, and a strategic mindset to identify opportunities that are not just urgent but also significant and scalable. It requires distinguishing between a symptom and the disease, a task that demands critical thinking, pattern recognition, and strategic foresight, capabilities that AI can augment but not yet fully replicate. Data from a 2022 Gartner survey indicated that companies with strong problem discovery processes are 2.5 times more likely to achieve product-market fit.
2. Navigating Solution Discovery: The Value Risk
Evans’s second point underscores a crucial distinction: proficiency in using a tool is fundamentally different from expertise in creating a tool. He eloquently states, "People that are really good at using the tool are not the same people as those that are really good at creating the tool." This distinction is particularly salient in an era where AI promises to make tool creation more accessible. While a sales professional may possess profound knowledge of sales processes, client interactions, and market dynamics, this expertise does not automatically equip them to design effective sales software.
The product leader’s role in "solution discovery" involves translating identified problems into tangible, valuable solutions. This encompasses understanding user needs, conceptualizing features, designing user experiences, and validating hypotheses through iterative testing and feedback loops. It’s about ensuring the solution genuinely addresses the problem in a way that provides demonstrable value to the end-user. This involves mitigating "value risk"—the risk that users won’t find the product useful or valuable. AI can generate countless solution ideas, automate prototyping, and even write code, but the human judgment to select, refine, and validate which solution truly resonates with users and solves their core problem remains firmly within the product leader’s domain. According to a report by McKinsey & Company, companies that invest heavily in robust solution discovery processes see, on average, a 15-20% higher success rate in new product launches.
3. Ensuring Business Viability: The Enterprise Context
Beyond discovering a valuable solution for the customer, the third and equally vital skill is the ability to ensure that the solution is also viable for the business. This involves navigating the intricate web of internal stakeholders, operational constraints, regulatory requirements, and strategic objectives that define an enterprise. A brilliant solution from a user’s perspective might be a non-starter if it doesn’t align with the company’s financial model, conflicts with legal compliance (e.g., GDPR, HIPAA), cannot integrate with legacy systems, or disrupts critical internal workflows across departments like sales, marketing, finance, and customer support.
The product leader acts as an internal diplomat and orchestrator, understanding the "viability risk." They must foresee how a new product or feature will impact various parts of the organization, negotiate trade-offs, and champion solutions that not only delight users but also contribute positively to the company’s strategic goals and operational efficiency. This requires a comprehensive understanding of the business ecosystem, strong communication skills, and the ability to build consensus across diverse teams. A 2023 survey by Amplitude found that aligning product strategy with overall business objectives was cited as the top challenge for 40% of product teams, emphasizing the complexity of this viability aspect. Evans’s framework implicitly underscores that AI tools, while powerful, operate within a predefined technical scope; they do not inherently grasp the multi-faceted business context required for a solution’s successful integration and sustainability.
The Enduring Relevance of Human Product Craft in the AI Era
Evans’s insights serve as a potent reminder that while AI revolutionizes the means of creation, it does not diminish the strategic imperative of skilled human leadership in defining what and why. The initial enthusiasm for "product creators" leveraging AI tools may have led some to believe that the "craft" of product management would become largely automated or simplified. However, as Evans compellingly argues, "Writing the code isn’t the hard part, and making the tool isn’t the hard part — the hard part is knowing that it should exist, and knowing how it should exist, and that’s a different person."
This perspective highlights the persistent and growing need for product professionals who possess a rare combination of strategic foresight, deep user empathy, and comprehensive business acumen. The product manager’s role, far from being made redundant by AI, is arguably elevated. It shifts from overseeing potentially manual or repetitive tasks (which AI can now handle) to focusing intensely on the higher-order cognitive functions: identifying truly impactful problems, envisioning innovative and valuable solutions, and navigating the complex organizational landscape to ensure these solutions are viable and scalable.
The implications for the future of product management are profound. Product professionals must increasingly cultivate and demonstrate these distinct skills outlined by Evans. Their value proposition in the AI era is not in their ability to operate tools, but in their capacity for critical thinking, strategic judgment, and holistic problem-solving. They remain the crucial bridge between technological potential and market reality, ensuring that innovation is not just technically feasible but also genuinely valuable and commercially viable. As companies navigate an increasingly complex and AI-driven economy, the product role, anchored by these enduring skills, is not merely essential; it is a strategic imperative for sustained success and meaningful innovation.
