Stop Micromanaging and Start Developing Your PMs while Managing Product Managers

Why do brilliant engineering teams spend months building things that nobody actually buys? Managing product managers is crucial because roughly 90% of all product releases fail to meet their intended business objectives. For a director of product management, success depends entirely on building a team that can bridge the gap between technology and customer value. Marty Cagan argues that this leadership role is the most impactful position in any modern tech firm. You act as the architect of the team that ultimately builds the company.

The Role of the Head of Product

Managing product managers refers to the leadership function typically held by a VP or Director of Product. In his book Inspired, Marty Cagan defines this role through two primary duties: building a high-performing team and setting the overarching portfolio strategy. This isn't a traditional middle-management job focused on status reports. It's a high-stakes position where a single failed product can sink a business, while a success can redefine its entire trajectory.

This role is organizationally on par with the heads of engineering and marketing. A successful head of product ensures that the company's offerings stay aligned with the broader business strategy. They resolve conflicts between different product lines and ensure that resources go to the best opportunities. Without this dedicated leadership, teams often become feature factories that lose sight of actual customer needs.

Core Components of Product Leadership

Hire for Traits Instead of Resumes

Most leaders hire for domain expertise, but Cagan suggests this is a mistake. You're looking for product passion, customer empathy, and innate intelligence. Domain knowledge can be learned in three months, but you can't teach someone to love products. A PM with high empathy will naturally uncover the hidden pain points of your users. These personal traits form the foundation of a team capable of true innovation.

Why Your VP Product Role Must Foster Ownership

If you micromanage your team, they'll never take true ownership of their products. You've got to hire people smarter than yourself and then give them the latitude to make decisions. Empowered teams are productive; micromanaged teams are just order-takers who stop thinking for themselves. Trust is the currency of a successful product organization. When you empower pm teams, you allow them to surprise you with their ingenuity.

Portfolio Strategy Tactics for Managing Product Managers

Your second duty is resolving conflicts across the product line. Each individual PM will naturally try to optimize their own specific area. As the head of product, you ensure these separate efforts align with the company's broader business goals. This involves managing the portfolio roadmap and identifying cross-product issues before they derail a release. You provide the strategic context that allows individual PMs to excel in their specific domains.

Success and Failure in the Real World

HP once spent a year developing a high-tech AI workstation that reviewers loved but customers ignored. The engineering was perfect, but the product manager failed to discover a solution that was actually valuable. Marty Cagan witnessed this failure firsthand and realized that great engineering is worthless if the team isn't given something worthwhile to build. This lesson shaped his entire philosophy on the importance of discovery over mere execution.

eBay provides a more successful example of strong product management and project discipline. Under the leadership of Lynn Reedy, eBay established a project management competency that allowed the company to scale globally. They managed a massive, multi-million-line code rewrite while simultaneously delivering record amounts of new functionality. This was possible because the leadership team understood how to manage complex interdependencies without slowing down the innovation engine.

Apple demonstrates how hardware should serve software, which in turn serves the user experience. They don't just add features; they create products that speak to human emotions like pride and excitement. Their success with the iPhone wasn't just about marketing prowess. It was about a leadership team that insisted on a holistic user experience that satisfied deep, unmet consumer needs. They understood that the end goal of any product is to create a happy, loyal customer.

Three Moves to Level Up Your Team

1. Establish a Product Council. Bring together the cross-functional set of managers responsible for product development to make timely, high-level decisions. This group should focus on selecting opportunities and reviewing prototypes rather than trying to design the product. A council eliminates the need for endless, unstructured meetings and provides clear visibility for the CEO.

2. Implement a 20% Headroom Rule. Negotiate with engineering to dedicate 20% of their total capacity to infrastructure and scaling. This prevents the code base from becoming a house of cards as the user base grows. It's the best way to avoid the dreaded "we need to stop and rewrite" conversation that kills many growing startups.

3. Use Net Promoter Score (NPS) as a Core Metric. Start measuring how likely your customers are to recommend your product to others. This single metric keeps the team focused on the overall customer experience rather than just hitting feature deadlines. It's a clear indicator of whether your PMs are actually creating products that people love.

Where the Cagan Model Faces Friction

Critics often argue that the recommended ratio of one PM per five to ten engineers is too expensive for bootstrapped startups. While this investment is high, Cagan would argue that building the wrong thing is even more costly. Some also find the "Sprint Zero" concept for designers to be difficult to coordinate in fast-moving Agile environments. It requires a high level of discipline to keep design work consistently ahead of implementation cycles.

Cagan also explicitly states that his methods are designed for software and internet products. If you're working in pharmaceuticals or heavy manufacturing, the rapid prototyping and discovery cycles might be harder to implement. These industries have different regulatory and physical constraints that don't always allow for the same flexibility. However, the core principle of validating value before building remains a universal business truth.

Hire PMs based on their passion and empathy, then give them the autonomy to own their products. A head of product must balance building team capabilities with a coherent portfolio strategy. Schedule your first Product Council meeting this week to review the current roadmap and identify one area where managing product managers can improve the overall customer experience.