The foundational definition of the product role, encompassing positions like Product Manager and Product Owner, has long been a subject of extensive debate and diverse interpretation across the technology industry. With literally hundreds of distinct definitions surfacing over the years, this fluidity stems from a confluence of factors, including varying organizational operating models, the inherent complexity of the role, and a pervasive desire for concise, often oversimplified, descriptions. This ongoing discourse has taken on renewed urgency and depth with the accelerating integration of Artificial Intelligence (AI) into business operations and product development. A recent analysis, drawing from the insights of prominent technology industry analyst Benedict Evans, suggests that while AI tools promise to democratize creation, they inadvertently underscore the indispensable and strategic importance of the product professional, especially those possessing a specific set of critical skills.
The ambiguity surrounding the product role is not merely an academic exercise; it has tangible implications for talent acquisition, team structure, and strategic direction within companies. For decades, the simple query, "How do you define your product role?" has served as a revealing Rorschach test in interviews, offering profound insights into a candidate’s professional background, their understanding of the role’s purpose, and their perceived contribution to a product team. The responses illuminate the diverse product models they have encountered, ranging from highly prescriptive, feature-delivery-focused roles to expansive, strategic positions guiding market entry and long-term vision. This inherent variability makes a universal, pithy definition elusive, as any attempt to capture its essence often omits critical nuances.
The Evolving Landscape of Product Management
Product management as a distinct discipline traces its roots back to the 1930s with Procter & Gamble’s "brand men" who managed specific brands. However, its modern iteration, particularly within technology, gained prominence in Silicon Valley, evolving significantly with the advent of personal computing in the 1980s and the internet boom of the 1990s. The early 2000s saw a paradigm shift with the widespread adoption of agile methodologies, pushing product managers to work more closely with engineering teams and focus on iterative development and customer feedback. By the 2010s, "product-led growth" became a dominant philosophy, emphasizing the product itself as the primary driver of customer acquisition, retention, and expansion.
This historical trajectory reveals a constant expansion of the product manager’s mandate, transitioning from mere project coordination to strategic leadership. Today, a product manager is often expected to be a polymath, bridging the gap between business strategy, technical feasibility, and user desirability. This includes market analysis, competitive intelligence, customer research, roadmap development, stakeholder communication, and often, a deep understanding of data analytics. The sheer breadth of these responsibilities contributes significantly to the definitional challenges, as different organizations prioritize different facets of the role based on their industry, maturity, and specific business objectives. For instance, a product manager in a B2C SaaS company might focus heavily on user experience and growth metrics, while one in an enterprise B2B firm might prioritize integration capabilities, compliance, and complex stakeholder management.
AI’s Double-Edged Sword: Promise and Reality
The advent of advanced AI capabilities, particularly generative AI and sophisticated automation tools, has introduced a new layer of complexity and potential disruption to this already intricate landscape. Initial enthusiasm suggested that AI would democratize software creation, empowering "citizen developers" to build their own applications, automate workflows, and even design complex systems with minimal coding knowledge. Low-code and no-code platforms, augmented by AI, were touted as the ultimate enablers for anyone with an idea to become a "product creator," bypassing traditional development bottlenecks.
However, the practical implementation of these promises has revealed a significant gap between aspiration and reality. While AI tools undeniably lower the technical barrier to entry for building, the success rate of such endeavors, especially within complex organizational contexts, remains a challenge. Data from various industry reports indicates that while adoption of AI tools for specific tasks is growing rapidly – with a 2023 McKinsey report showing 70% of organizations reporting some AI adoption, up from 50% in 2022 – the broader success in transforming these tools into effective, scalable, and viable business solutions is far from universal. Many organizations struggle to move beyond pilot projects or isolated use cases, encountering difficulties in integration, maintenance, and aligning AI-generated solutions with overarching strategic goals. This disparity highlights a crucial insight: possessing the tools does not automatically confer the ability to build effective solutions.
Benedict Evans’ Provocative Thesis: "Most People Aren’t Tool Builders"
This crucial distinction between tool access and solution creation forms the core of Benedict Evans’ recent thesis, articulated in his article "Most People Aren’t Tool Builders" and further elaborated in a widely circulated podcast. Evans, a respected technology industry analyst known for his sharp insights into market trends and strategic shifts, approaches the subject not from the perspective of a product practitioner, but as an astute observer of the broader tech ecosystem. His argument, while not explicitly defining the product role, provides one of the most compelling implicit descriptions of the skills required for effective product management in the AI era.
Evans posits that despite the increasing accessibility of powerful tools and technologies, including advanced AI, the vast majority of individuals and organizations are fundamentally not "tool builders." He argues that while customers may now have the technical means to "vibe-code" applications or automate workflows with intelligent agents, they are remarkably unlikely to attempt it, and even less likely to succeed in creating robust, impactful solutions if they do. This observation challenges the optimistic narrative of widespread "democratized creation" and redirects attention to the unique cognitive and strategic abilities that underpin successful product development.
Unpacking the Essential Product Skills in the AI Era
Evans’ analysis, when mapped to the established lexicon of product management, illuminates three distinct and essential skills that differentiate true product creators from mere tool users:
-
The Art of Problem Discovery: Many individuals can identify a pain point or conceptualize an idea for improvement. However, the critical skill, according to Evans, lies in transcending the specific instance of pain to discern the underlying, more general problem that needs solving. This requires a profound ability to abstract, synthesize, and contextualize. For a product manager, this translates directly to the practice of problem discovery – a deep dive into user needs, market gaps, and strategic opportunities that often extends beyond superficial symptoms. This involves rigorous qualitative and quantitative research, active listening, pattern recognition, and the capacity to envision a broader solution space. Without this foundational skill, even the most advanced AI tools will merely automate suboptimal processes or solve non-existent problems, leading to wasted resources and failed initiatives.
-
Navigating Solution Value Risk: Once a significant problem has been identified, the next hurdle is discovering an effective solution. Evans emphasizes a crucial distinction: "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 a potent 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 speaks directly to the concept of managing "value risk" in solution discovery – ensuring that a proposed solution genuinely delivers value to the customer and solves their core problem effectively. It requires a unique blend of empathy, creativity, and systematic validation. A product manager must not only understand the target user deeply but also possess the design thinking acumen and iterative testing methodologies to craft a solution that is both intuitive and impactful. This involves continuous experimentation, prototyping, and gathering feedback to refine the solution until it demonstrably meets user needs and provides tangible benefits.
-
Mitigating Solution Viability Risk: Beyond delivering customer value, a strong product professional must also ensure that the discovered solution is viable for the business. Evans points out that solutions rarely exist in a vacuum; they interact with numerous internal stakeholders and organizational constraints. A new product or feature might impact sales processes, marketing strategies, financial models, regulatory compliance, legal considerations, and existing technological infrastructure. It may depend on sensitive data, require integration with legacy systems, or necessitate adjustments to various workflows across the enterprise. This third skill directly addresses "viability risk" – the ability to design and implement a solution that works not only for the customer but also for the company as a whole. This demands a broad and deep understanding of the organization’s capabilities, limitations, and strategic objectives. A product manager must act as an internal diplomat, navigating complex stakeholder landscapes, securing buy-in, and ensuring that the solution aligns with broader business goals and operational realities. This includes assessing the cost-effectiveness, scalability, and long-term sustainability of the solution.
The Strategic Imperative for Product Leadership
These three skills – problem discovery, managing value risk, and mitigating viability risk – are rarely found in combination among most individuals. They represent a sophisticated synthesis of analytical rigor, creative problem-solving, strategic thinking, and organizational acumen. While elements of these skills might exist within other functions, it is the product professional who is uniquely positioned and empowered to orchestrate their convergence, transforming nascent ideas into successful, sustainable products.
Evans’ perspective serves as a powerful reminder that the true value of product management transcends mere feature delivery or technical proficiency. It lies in the strategic foresight to identify what should exist, the ingenuity to determine how it should exist, and the leadership to navigate the complexities of bringing it to fruition within a business context. This perspective is particularly salient in the AI era, where the ease of building tools can paradoxically obscure the much harder challenge of building the right tools for the right problems.
Industry Reactions and Broader Implications
Evans’ thesis resonates deeply with the experiences and observations of many product management thought leaders. Experts like Marty Cagan, known for his emphasis on product discovery and empowered product teams, and Teresa Torres, a proponent of continuous discovery, have consistently argued that understanding the problem space and validating solutions are paramount, far outweighing the act of coding or merely managing a backlog. Their collective wisdom underscores that technology is an enabler, but strategic thinking, customer empathy, and business acumen remain the driving forces behind successful product outcomes.
From an organizational standpoint, Evans’ insights suggest that companies investing heavily in AI and low-code/no-code platforms should temper expectations about widespread "citizen development." Instead, they should redouble their efforts to cultivate and empower highly skilled product professionals who can effectively leverage these tools to address strategic business challenges. This might entail:
- Elevating the Product Role: Recognizing product management as a core strategic function, not merely an operational one.
- Investing in Product Talent Development: Focusing on training and mentorship that hones problem discovery, solution validation, and business viability skills.
- Structuring for Discovery: Creating organizational structures and processes that explicitly support continuous product discovery rather than just delivery.
- Strategic AI Integration: Ensuring that AI initiatives are led by product teams who can connect AI’s capabilities to genuine market needs and business opportunities.
The "tool builder" paradox highlighted by Evans underscores a fundamental truth: while AI lowers the bar for making tools, it simultaneously raises the bar for knowing what tools to make and how to make them impactful. This distinction solidifies the enduring and indeed elevated importance of the product role. The product manager of the AI era must evolve into a strategic architect, capable of harnessing advanced technologies to solve complex problems, creating genuine value for customers, and ensuring sustainable growth for the business. This critical function serves as the indispensable bridge between technological potential and real-world impact, ensuring that innovation translates into meaningful progress rather than mere technological indulgence.
