The 'Empowerment Model' for Product Managers
A recent analysis on the Product Thinking podcast highlights the "empowerment model" for product management, used by companies like Amazon and TikTok. In this model, PMs are given business outcomes to achieve, such as improving retention, rather than a list of features to ship. They are then responsible for proposing solutions, negotiating for resources, and taking full accountability for the results.
The "empowerment model" was heavily popularized by Marty Cagan, a Silicon Valley product veteran and founding partner of the Silicon Valley Product Group. His book "Inspired" is considered a foundational text, contrasting the practices of successful tech companies with those of "feature teams." This approach stands in direct opposition to the "feature factory" model, where teams are given a roadmap of features to build and are measured on output rather than on achieving measurable business outcomes. In a feature factory, teams often lack direct contact with customers and have little say in what gets built, leading to a focus on shipping features over solving actual user problems. An empowered team is typically a cross-functional trio of product, design, and engineering that is given a specific customer or business problem to solve. This structure, often called a "product squad," is designed to have the necessary skills and autonomy to discover the best solution to a given problem, a model famously adopted by companies like Spotify. The core belief is that the team closest to the customer is best positioned to find the right solution. This requires product managers to have a deep knowledge of their users, the data, the market, and the business itself to make informed decisions. However, true empowerment isn't chaos; it requires a foundation of trust and clear strategic context from leadership. Leaders are responsible for setting the product vision and company objectives, ensuring that while teams have autonomy on the "how," their work aligns with the overall company strategy to prevent disjointed efforts. To validate their ideas, empowered teams engage in continuous product discovery, using techniques like rapid prototyping and frequent customer interviews. This allows them to test assumptions about value, usability, feasibility, and business viability before committing significant engineering resources. While the model fosters innovation and motivation, it can present challenges like the risk of teams working on the wrong things or duplicating efforts without strong directional guidance. Striking the right balance between autonomy and alignment is crucial for an organization to successfully scale this approach.
