The dynamic landscape of technology has consistently reshaped organizational structures and professional roles, yet few positions have weathered as much definitional flux as that of the product manager or product owner. Over recent decades, the core responsibilities and requisite skill sets for this critical function have been subject to myriad interpretations, often tailored to specific operating models, industry verticals, or even individual company philosophies. This ongoing ambiguity underscores a fundamental challenge in the tech sector: clearly articulating the strategic imperative and unique contributions of product leadership.
The Elusive Definition of Product Management
Historically, the product role has evolved significantly. Its genesis can be traced back to the 1930s with Procter & Gamble’s brand management, focusing on market analysis and competitive strategy for consumer goods. In the software industry, the role gained prominence in the 1980s and 90s, often blending aspects of project management, technical understanding, and market analysis. With the advent of agile methodologies in the early 2000s, the "Product Owner" emerged, emphasizing backlog management and stakeholder communication within development sprints. Today, the role spans a vast spectrum, from highly technical product managers in AI/ML domains to growth-focused product managers specializing in user acquisition and retention, and strategic product leaders shaping entire portfolios.
The sheer volume of definitions, estimated by some industry veterans to exceed a hundred, highlights the complexity. This lack of a universal standard is not merely an academic exercise; it has tangible implications for hiring, career progression, and the effective execution of product strategies within organizations. A common observation among seasoned recruiters and product leaders is that asking a candidate to define their product role often functions as a "Rorschach test." Their response reveals not only the specific product models they’ve experienced but also their underlying philosophy regarding the role’s purpose, its value proposition, and its contribution to the broader product team and business objectives.
This definitional fluidity stems from several factors. Different operating models, whether B2B, B2C, enterprise, or startup, inherently demand distinct skill sets and focus areas from product professionals. Moreover, the human inclination to distill complex roles into concise, memorable phrases often sacrifices the nuanced understanding necessary for effective performance. While such pithy descriptions can be useful for initial communication, they frequently fail to capture the depth and breadth of responsibilities, ranging from deep customer empathy and market analysis to technical acumen and cross-functional leadership.
According to a recent report by Product School, the demand for product managers continues to outpace the supply of truly qualified candidates, with a projected growth rate of 15-20% annually. However, a significant challenge for companies lies in distinguishing between individuals who can merely manage a backlog and those who possess the strategic foresight and comprehensive skill set to drive innovative product outcomes. This disparity amplifies the need for a clearer, more robust understanding of what constitutes excellence in product management, particularly as new technological paradigms emerge.
AI’s Impact and the "Product Creator" Hypothesis
The advent of Artificial Intelligence, especially generative AI, has introduced a new layer of complexity and speculation into the discussion of product roles. Initially, there was a wave of optimism, a "product creator" hypothesis suggesting that AI tools would democratize product development. The idea was that with powerful AI-driven platforms, individuals and small teams could bypass traditional development hurdles, rapidly "vibe-code" applications, automate workflows with intelligent agents, and generally accelerate the creation of solutions without extensive technical expertise. This vision fueled expectations that many more people would become adept product creators, bridging the gap between an idea and a functional prototype with unprecedented ease.
However, a year into this "AI era," the reality has proven more nuanced. While AI has undoubtedly lowered the barrier to entry for certain technical tasks, the anticipated explosion of widespread, high-quality product creation by non-specialists has not fully materialized. This discrepancy points to a deeper truth about product development: the tools themselves, no matter how sophisticated, are only one part of the equation. The more critical elements—strategic insight, problem identification, and holistic solution design—remain firmly in the human domain, requiring a specialized cognitive framework that AI, at least for now, cannot replicate.
Benedict Evans’ Seminal Insight: "Most People Aren’t Tool Builders"
In this context, the insights of technology industry analyst Benedict Evans have proven particularly illuminating. Evans, renowned for his astute observations on the broader tech ecosystem, recently articulated a perspective that, while not directly aimed at defining the product role, offers one of the most compelling descriptions of the responsibilities and skills essential for product managers in the AI age. Evans, a former partner at Andreessen Horowitz and a prolific writer, is widely respected for his macro-level analysis of technology trends and their economic and societal implications. His work often cuts through hype to reveal underlying structural truths, making his observations invaluable for understanding the trajectory of the industry.
Evans’ recent article, "Most People Aren’t Tool Builders" (and an accompanying podcast discussion), explores why, despite increased access to powerful tools and technologies—including advanced AI—customers are unlikely to successfully create their own complex solutions. His core argument distinguishes between the mindset and capabilities of typical users and those of individuals adept at creating new tools or systems. This distinction inadvertently casts a bright light on the unique value proposition of the product manager.
The essence of Evans’ argument is that even if AI makes it significantly easier to write code or automate tasks, the fundamental challenges of knowing what should be built and how it should function to address a real problem effectively persist. He posits that the cognitive leap required to move from identifying a personal pain point to conceptualizing, designing, and implementing a generalized, robust solution is one that most individuals and companies are simply not equipped to make. This perspective serves as a powerful reminder of why specialized product roles remain indispensable.
Deconstructing the Product Role: Evans’ Three Pillars of Product Expertise
Evans implicitly outlines three distinct, yet interconnected, skills that characterize effective product professionals. These skills, while not exclusive to product management, are rarely found collectively and deeply embedded in most individuals, highlighting the specialization of the role:
-
Identifying the General Problem (Problem Discovery): Many people can articulate a pain point or suggest an idea to alleviate it. However, a truly skilled product person possesses the ability to look beyond the superficial symptom or individual anecdote to identify the broader, underlying problem that needs solving. This involves a deep empathy for user needs, rigorous analytical thinking, and the capacity to synthesize disparate observations into a coherent understanding of a widespread opportunity. For decades, product leaders have emphasized this distinction between "problem space" and "solution space." Evans’ point reinforces that while everyone experiences problems, only a few can effectively abstract those experiences into generalizable challenges that a product can address for a wider audience. This skill is foundational to what is known in product management as "problem discovery"—understanding the market, the user, and the unmet needs before jumping to solutions.
-
Crafting Effective Solutions (Value Risk Mitigation): Once a significant problem has been identified, the next hurdle is discovering an effective solution. Evans 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 critical distinction highlights that deep domain expertise, while valuable, does not automatically translate into the ability to design software or systems that serve that domain effectively. His 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," perfectly encapsulates this. Product managers must possess the unique skill of translating user needs and business requirements into tangible product features and experiences, navigating the complexities of user interface, user experience, functionality, and underlying technology. This involves mitigating "value risk"—ensuring that the solution genuinely delivers demonstrable value to the customer. It’s about designing a tool that is not just functional, but also intuitive, efficient, and desirable for its intended users.
-
Ensuring Business Viability (Viability Risk Mitigation): Beyond designing a solution that satisfies customer needs, a strong product professional must also ensure that the solution is viable for the business. This requires a comprehensive understanding of the company’s internal ecosystem and external constraints. Most significant product initiatives will touch various departments: sales, marketing, finance, legal, compliance, operations, and customer support. The solution might need to integrate with complex legacy systems, adhere to stringent regulatory frameworks (e.g., GDPR, HIPAA), or be incorporated into diverse internal workflows. A product manager must navigate these organizational complexities, anticipate potential roadblocks, and design solutions that align with the company’s strategic objectives, resource capabilities, and risk tolerance. This skill addresses "viability risk"—the challenge of ensuring that a product is not only valuable and usable but also feasible for the business to build, launch, and sustain profitably and ethically.
Mapping Evans’ Framework to Product Management Principles
The insights provided by Evans, though from an external analyst’s perspective, directly map to well-established principles within the product management discipline. His first point on identifying the general problem aligns perfectly with the initial stages of problem discovery, a critical phase where product teams immerse themselves in understanding user needs, market dynamics, and competitive landscapes. The second point, concerning the creation of effective tools versus merely using them, addresses the core of value risk mitigation in solution discovery—the iterative process of validating whether a proposed solution truly delivers the desired outcome for the user. Finally, his third point, emphasizing the need for solutions that work within the broader business context, directly tackles viability risk, ensuring the product’s alignment with organizational capabilities, legal requirements, and financial objectives.
These three skills, taken together, form a holistic view of what makes a product manager truly effective. They highlight that the role is not merely about managing a project or translating requirements, but about deep strategic thinking, creative problem-solving, and cross-functional leadership. It is rare to find individuals who naturally possess all three of these capabilities to a high degree, which underscores the specialized nature and enduring importance of dedicated product roles.
Implications for the AI Era and Beyond
Evans’ analysis serves as a crucial reality check for the product world, especially as AI continues to proliferate. It corrects the overestimation of how many people inherently possess the "product creator" mindset. Many product leaders, including the author of the original article, admit to having made this mistake, assuming that their own problem-solving orientation was more widespread among customers.
-
For Product Professionals: The message is clear: the fundamental skills of product management are not diminished but amplified by AI. While AI can automate tasks and provide insights, the strategic thinking required for problem discovery, value creation, and business viability remains a deeply human endeavor. Product managers must evolve to leverage AI as a powerful assistant for research, analysis, and even prototyping, but their core responsibility for strategic foresight and holistic solution design is more critical than ever. Continuous learning in AI capabilities and ethical considerations will be paramount.
-
For Organizations: Companies must recognize that simply providing AI tools to their customers or internal teams will not automatically lead to innovative solutions. Investing in strong product leadership and fostering a culture that values strategic product thinking is essential. The "build vs. buy" decision now extends to "build with AI" vs. "use AI-powered products," and organizations need skilled product managers to navigate this complexity, designing AI-powered offerings that truly solve problems rather than just showcasing technology.
-
For Hiring and Talent Development: The criteria for identifying and nurturing product talent need to focus less on mere technical proficiency or superficial "product owner" certifications, and more on demonstrated abilities in Evans’ three pillars. Recruiters should seek candidates who exhibit strong analytical skills, a track record of identifying and validating problems, a capacity for creative solution design, and a deep understanding of business operations. Internal training programs should emphasize these strategic competencies over tactical execution alone.
-
The Future of Product Management: AI is not a threat to the product role itself, but rather a catalyst for its evolution. It will free product managers from more mundane tasks, allowing them to focus on higher-level strategic challenges: understanding complex user behavior, identifying latent needs, navigating ethical considerations in AI deployment, and orchestrating cross-functional efforts to deliver truly impactful products. The role will shift even further towards empathy, vision, and the art of connecting technology to human and business value.
In conclusion, Benedict Evans’ seemingly tangential observations about "tool builders" provide a profoundly relevant and timely affirmation of the product role’s enduring and increasingly critical nature. In an age where technological capabilities rapidly outpace the human capacity to leverage them effectively without skilled guidance, the product manager stands as the essential bridge—the individual who can discern that a solution should exist, understand how it should exist, and ensure it thrives within the complex interplay of user needs and business realities. This perspective serves as a powerful reminder that the craft of product management, far from being rendered obsolete by AI, is more vital than ever in shaping the future of innovation.
