The Evolving Mandate: A Historical Perspective
The concept of product management traces its roots back to the 1930s at Procter & Gamble, where Neil McElroy, then an advertising manager, advocated for "brand men" to champion specific products, understanding both customer needs and business objectives. This early iteration focused heavily on marketing and sales. Over subsequent decades, particularly with the advent of software and digital technologies, the role evolved dramatically. The rise of Agile methodologies in the early 2000s further reshaped product management, giving birth to the Product Owner role, often distinct from or overlapping with the Product Manager, depending on the organizational structure and chosen framework.
Today, the product role is widely recognized as a critical nexus, requiring a blend of strategic vision, technical understanding, user empathy, and business acumen. Data from LinkedIn’s "Jobs on the Rise" report consistently places product management among the fastest-growing professions, underscoring its increasing strategic importance in technology companies and beyond. The global market for product management software alone is projected to reach billions, reflecting the institutionalization and scaling of these practices. Yet, despite this growth and formalization, a universal, unambiguous definition remains elusive, creating both challenges and opportunities for practitioners and organizations alike.
The Nuance of Definition: Why It’s So Hard
The primary challenge in establishing a singular definition lies in the inherent variability of organizational contexts. A product manager in a large enterprise developing B2B SaaS solutions will operate with different responsibilities and require distinct skill sets compared to their counterpart in a nascent startup building a consumer mobile application. These disparities extend to:
- Operating Models: Agile, Waterfall, Lean, Hybrid — each methodology assigns different levels of autonomy, decision-making power, and responsibility to product roles.
- Company Maturity: A product leader in a scaling startup might be heavily involved in market validation and fundraising, while in a mature corporation, the focus might shift to optimization, governance, and cross-functional alignment.
- Product Type: Hardware, software, services, platforms, data products — each category presents unique development cycles, user engagement patterns, and business models.
- Team Structure: The size and composition of engineering, design, and research teams directly influence the scope of a product manager’s involvement in technical specifications, UX flows, and user research.
This vast array of permutations means that while core principles remain, the practical application and daily responsibilities of a product professional can diverge significantly. Industry surveys often highlight a skills gap, with organizations struggling to find individuals who possess the full spectrum of required competencies, from strategic thinking and market analysis to technical fluency and stakeholder management. For instance, a 2023 report by ProductPlan indicated that "strategic thinking" and "communication" were among the most critical, yet often lacking, skills in product teams.
The Rorschach Test of Product Leadership
For seasoned hiring managers and industry observers, asking a product professional to define their role serves as a revealing "Rorschach test." The answer, far from being a simple right or wrong, acts as a diagnostic tool, providing deep insights into:
- Past Product Models: The candidate’s definition often reflects the specific operational frameworks and cultural norms of their previous organizations. Did they prioritize delivery, discovery, or strategic alignment?
- Perceived Purpose: It reveals their fundamental understanding of why the product role exists within an organization. Is it primarily to gather requirements, to maximize revenue, to solve user problems, or to drive innovation?
- Contribution to the Team: The emphasis placed on certain aspects highlights what they believe their core value proposition is to a product team and the broader company. Are they a visionary, an executor, a facilitator, or an analyst?
This diagnostic approach underscores the importance of a shared understanding within an organization regarding the product role’s mandate. Without clarity, product teams can become misaligned, leading to inefficiencies, scope creep, and ultimately, products that fail to meet market needs or business objectives. A 2022 Gartner study noted that a lack of clear product strategy and role definition contributed significantly to product failures.
AI’s Transformative Shadow: A New Imperative
The rapid ascent of Artificial Intelligence, particularly generative AI, has introduced a new layer of complexity and urgency to this ongoing discussion. The prevailing narrative often suggests that AI tools, by democratizing coding and automation, will empower a broader segment of users to "build their own solutions," potentially reducing the perceived need for traditional product roles. This perspective, however, risks oversimplifying the intricate process of product creation and underestimating the specialized skills that define effective product leadership.
The promise of "citizen developers" or "vibe-coding" (creating applications through natural language prompts) has indeed lowered technical barriers to entry. Tools like ChatGPT, GitHub Copilot, and various low-code/no-code platforms enable individuals with minimal programming knowledge to generate code, automate workflows, and even prototype applications at unprecedented speeds. This technological leap has sparked debates about the future of various tech roles, including product management. Will everyone become a product creator? Will the need for specialized product strategists diminish?
Benedict Evans’s Unconventional Clarity
Amidst this evolving discourse, technology industry analyst Benedict Evans, renowned for his insightful analysis of the broader tech landscape, has offered a particularly salient perspective. In his article, "Most People Aren’t Tool Builders," and a subsequent podcast discussion, Evans tackles the premise that widespread access to AI tools will naturally translate into widespread "tool-building" by customers. Though not directly attempting to define the product role, his analysis implicitly provides one of the most compelling descriptions of the essential responsibilities and skills of a product manager in the AI era.
Evans’s central argument posits that despite the increasing accessibility of powerful creation tools, most individuals and organizations will remain unlikely to successfully build their own solutions. He contends that the bottleneck isn’t the technical ability to create a tool, but rather the strategic mindset and specialized skills required to identify what should be built and how it should exist to solve a genuine problem effectively and viably.
Deconstructing the Product Mindset in the AI Era
Evans delineates three critical skills that distinguish effective product creators from mere tool-users, skills that are intrinsically linked to the core competencies of a strong product manager:
-
Problem Discovery: Seeing Beyond the Symptom: Many individuals can articulate a pain point or suggest an idea to alleviate it. However, the truly effective product person possesses the unique ability to transcend these superficial observations and identify the deeper, more generalized problem that underlies the specific pain or idea. This requires a profound capacity for abstraction, pattern recognition, and critical inquiry. For example, a customer might complain about slow report generation. A product professional, however, would probe further to uncover the underlying problem: is it a lack of real-time data for decision-making? Is it inefficient data aggregation? Is it a mismatch between available data and required insights? This critical distinction between a symptom and its root cause is fundamental to building impactful solutions. This aligns directly with the product management concept of problem discovery, emphasizing the "why" before the "what."
-
Solution Discovery: The Craft of Creation, Not Just Usage: Once a genuine problem worth solving has been identified, the next challenge lies in discovering an effective and elegant solution. Evans articulates this by stating, "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 compelling 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 highlights that deep domain expertise, while valuable, does not automatically confer the distinct skills required for product design, architecture, and development. The ability to translate user needs and business requirements into a functional, intuitive, and desirable product demands a different cognitive toolkit—one that encompasses systems thinking, user experience design principles, technical feasibility assessment, and iterative problem-solving. This skill set is crucial for mitigating the value risk in solution discovery, ensuring that the developed product genuinely delivers benefits to the user.
-
Business Viability: Navigating the Organizational Ecosystem: Beyond discovering a strong solution that meets customer needs, a truly effective product person must also possess a comprehensive understanding of their company’s internal landscape to ensure the solution is viable for the business. Products do not exist in a vacuum; they interact with and impact various internal stakeholders—sales, marketing, finance, legal, compliance, operations, and more. A proposed solution might depend on regulated data, necessitate integration with complex legacy systems, or require significant shifts in existing workflows across multiple departments. The ability to anticipate these interdependencies, secure internal alignment, and navigate organizational constraints is paramount to a product’s success. This third skill directly addresses the viability risk of solution discovery, ensuring that the product is not only valuable and usable but also sustainable and profitable for the business.
These three skills, while not exclusively confined to product professionals, are rarely found collectively in the general population. They represent a specialized blend of analytical rigor, creative problem-solving, and strategic foresight that underpins successful product development.
Beyond Tools: The Enduring Craft of Product
The advent of AI has, for some, created an illusion that the process of product creation has been fundamentally simplified to the point where anyone can do it. The original author of the article, for instance, previously celebrated "The Era of the Product Creator," envisioning a widespread proliferation of individuals capable of strong product creation due to new tools. However, as Evans effectively argues, the issue is not the availability or sophistication of the tools; it is the underlying mindset and the mastery of the craft of product management.
AI tools accelerate execution and reduce the friction of creation, but they do not automatically imbue users with the strategic discernment to identify critical problems, the design intuition to craft effective solutions, or the business acumen to ensure organizational viability. These remain distinctly human, high-level cognitive functions that define the essence of product leadership. A study by IBM on the future of work highlighted that while AI will automate many routine tasks, skills like complex problem-solving, critical thinking, and creativity will become even more valuable.
The "Tool Builder" Fallacy: Dispelling Common Misconceptions
A common pitfall, especially for product professionals deeply immersed in technology, is to project their own "tool-builder" mentality onto their customers. This leads to the erroneous assumption that customers will readily leverage AI technologies to construct bespoke solutions for their own needs. Benedict Evans firmly dispels this notion: "Most people and companies aren’t tool builders."
He elaborates on this crucial point: "AI makes it easy for anyone to build tools to automate their work… except most people and most companies aren’t tool-builders, don’t think like that, and can’t and won’t do that. This is why software companies and consultants exist — AI changes the thresholds but not the problem."
Evans’s powerful conclusion underscores that the core challenge in product development has never been solely about the mechanics of building. "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 "different person" is, in essence, the skilled product professional.
Implications for Product Strategy and Talent Development
Evans’s insights carry significant implications for organizations and individuals in the product space:
- Hiring and Development: Companies must prioritize hiring individuals who demonstrate these three core product skills—problem discovery, value assessment, and viability analysis—rather than solely focusing on technical aptitude or domain expertise. Continuous learning programs should emphasize these strategic competencies, especially as AI tools automate more tactical aspects of development.
- Strategic Differentiation: In an increasingly competitive landscape where AI can quickly replicate basic functionalities, the true differentiator will be the ability to identify truly impactful problems and craft unique, viable solutions. Product organizations that excel in these areas will maintain a significant competitive advantage.
- Role Clarity: The discussion reinforces the need for internal clarity regarding the product role’s strategic mandate. Product teams should be empowered to focus on the "why" and "what" with a deep understanding of market needs and business constraints, rather than being relegated to merely managing the "how."
- Customer Education: Product teams must also be mindful of the "tool builder" fallacy when designing products. User interfaces and features should cater to the reality that most users are not tool builders; they seek intuitive, ready-to-use solutions that seamlessly integrate into their existing workflows, rather than platforms requiring significant configuration or bespoke development.
Conclusion: The Indispensable Product Architect
In an era characterized by unprecedented technological acceleration and the widespread availability of powerful AI tools, the debate surrounding the product role’s definition and future relevance intensifies. Benedict Evans’s analysis, though not explicitly a treatise on product management, provides a profound and timely reminder of the enduring, indispensable value of the product professional.
The ability to discern genuine problems from symptoms, to architect valuable solutions that truly meet user needs, and to ensure these solutions are viable within the broader business ecosystem, remains a rare and critical skill set. AI may transform the how of product creation, but it amplifies, rather than diminishes, the importance of the human element in understanding what should exist and why. The product role, far from being rendered obsolete, is solidified as the strategic architect of innovation, navigating complexity and translating potential into tangible value in an increasingly AI-driven world. The foundational skills of problem discovery, value validation, and business viability will continue to be the bedrock upon which successful products are built, securing the product role’s essential place in the technological vanguard.
