The role of the product manager is expanding due to the growing importance of data in decision making, an increased customer and design focus, and the evolution of software-development methodologies.
Product managers are the glue that bind the many functions that touch a product—engineering, design, customer success, sales, marketing, operations, finance, legal, and more. They not only own the decisions about what gets built but also influence every aspect of how it gets built and launched.
Unlike product managers of the past, who were primarily focused on execution and were measured by the on-time delivery of engineering projects, the product manager of today is increasingly the mini-CEO of the product. They wear many hats, using a broad knowledge base to make trade-off decisions, and bring together cross-functional teams, ensuring alignment between diverse functions. What’s more, product management is emerging as the new training ground for future tech CEOs.
As more companies outside of the technology sector set out to build software capabilities for success in the digital era, it’s critical that they get the product-management role right.1
Why you need a product manager who thinks and acts like a CEO
The emergence of the mini-CEO product manager is driven by a number of changes in technology, development methodologies, and the ways in which consumers make purchases. Together, they make a strong case for a well-rounded product manager who is more externally oriented and spends less time overseeing day-to-day engineering execution, while still commanding the respect of engineering.
Data dominates everything
Companies today have treasure troves of internal and external data and use these to make every product decision. It is natural for product managers—who are closest to the data—to take on a broader role. Product success can also be clearly measured across a broader set of metrics (engagement, retention, conversion, and so on) at a more granular level, and product managers can be given widespread influence to affect those metrics.
Products are built differently
Product managers now function on two speeds: they plan the daily or weekly feature releases, as well as the product road map for the next six to 24 months. Product managers spend much less time writing long requirements up front; instead, they must work closely with different teams to gather feedback and iterate frequently.
Products and their ecosystems are becoming more complex
While software-as-a-service products are becoming simpler for customers, with modular features rather than a single monolithic release, they are increasingly complex for product managers. Managers must now oversee multiple bundles, pricing tiers, dynamic pricing, up-sell paths, and pricing strategy. Life cycles are also becoming more complex, with expectations of new features, frequent improvements, and upgrades after purchase. At the same time, the value of the surrounding ecosystem is growing: modern products are increasingly just one element in an ecosystem of related services and businesses. This has led to a shift in responsibilities from business development and marketing to product managers. New responsibilities for product managers include overseeing the application programming interface (API) as a product, identifying and owning key partnerships, managing the developer ecosystem, and more.
Changes in the ‘execution pod’
In addition to developers and testers, product-development teams include operations, analytics, design, and product marketers that work closely together in “execution pods” to increase the speed and quality of software development. In many software organizations, the DevOps model is removing organizational silos and enabling product managers to gain broader cross-functional insights and arrive at robust product solutions more effectively.
Consumerization of IT and the elevated role of design
As seamless, user-friendly consumer software permeates our lives, business users increasingly expect a better experience for enterprise software. The modern product manager needs to know the customer intimately. This means being obsessed with usage metrics and building customer empathy through online channels, one-on-one interviews, and shadowing exercises to observe, listen, and learn how people actually use and experience products.
Three archetypes of the mini-CEO product manager
There are three common profiles of the mini-CEO archetype: technologists, generalists, and business-oriented. These three profiles represent the primary, but not the only, focus of the mini-CEO product manager; like any CEO, they work across multiple areas (for instance, a technologist product manager will be expected to be on top of key business metrics). Most technology companies today have a mix of technologists and generalists (Exhibit 1).
As these three archetypes emerge, the project manager is a fading archetype and seen mainly at legacy product companies. The day-to-day engineering execution role is now typically owned by an engineering manager, program manager, or scrum master. This enables greater leverage, with one product manager to eight to 12 engineers, versus the ratio of one product manager to four or five engineers that has been common in the past.
Common themes across the three archetypes
An intense focus on the customer is prominent among all product managers. For example, product managers at Amazon are tasked with writing press releases from the customer’s perspective to crystalize what they believe customers will think about a product, even before the product is developed.2 This press release then serves as the approval mechanism for the product itself.