Product Management Theater: Marty Cagan on Building Empowered Product Teams
Many organizations appear to practice modern product management. They employ product managers, run agile ceremonies, maintain roadmaps, and invest heavily in software development. Yet Marty Cagan of Silicon Valley Product Group argues that much of this activity is “product management theater”: the organization adopts the vocabulary and rituals of product work without giving teams the responsibility or capabilities needed to produce valuable results.
In his conversation on Lenny’s Podcast, Cagan distinguishes shipping features from solving problems. He examines why product organizations became bloated, what separates feature teams from empowered teams, how artificial intelligence may expose weak roles, and why leadership remains essential even in a culture built around autonomy.
How Product Management Became Theater
Cagan’s criticism begins with a simple distinction: output is not the same as outcome. A company can complete a roadmap, release on schedule, and still fail to improve anything that matters. Customers may ignore the new functionality, revenue may remain unchanged, and the business may be no better positioned than before.
During the pandemic-era hiring surge, Cagan says, many technology companies expanded teams faster than they could maintain hiring standards or clarify responsibilities. Organizations added product owners, agile coaches, business analysts, product operations staff, and other coordinating roles. Some of these positions can create genuine leverage, but others merely add layers between the people defining problems and those building solutions.
This environment rewards visible activity. A full backlog, a polished requirements document, and a predictable delivery calendar all look like progress. Determining whether a proposed solution will be valuable, usable, feasible, and commercially viable is harder. The result is an organization that can demonstrate motion without demonstrating impact.
Cagan also challenges superficial implementations of agile methods. Scrum ceremonies and Jira workflows do not make a company innovative. When process becomes the operating goal, it can slow learning and obscure who is accountable for results.
Feature Teams and Empowered Product Teams
The central contrast in the discussion is between feature teams and empowered product teams.
A feature team receives a solution—often from an executive, stakeholder, or sales request—and is asked to deliver it. Its performance is typically measured by deadlines, scope, and release volume. The product manager may coordinate tasks, maintain the backlog, report status, and translate stakeholder requests into tickets. Cagan considers this closer to project administration than authentic product management.
An empowered product team receives a meaningful customer or business problem. Product leaders establish the strategic context and decide which problems deserve investment, while the cross-functional team determines how best to solve them. Product managers, designers, engineers, and technical leaders combine their expertise to discover a solution and test whether it works.
The difference is not cosmetic. A feature team is responsible for executing an instruction. An empowered team is accountable for producing a result.
Cagan argues that strong product companies care less about time-to-market in isolation than about “time-to-money”: how quickly an investment begins generating real value. Shipping sooner is useful only if the release improves the customer experience or advances the business.
What a Real Product Manager Contributes
In Cagan’s model, a product manager is a creator and decision-maker, not simply a facilitator. Designers bring deep expertise in usability and experience. Engineers assess feasibility and help uncover possibilities enabled by technology. The product manager concentrates especially on value and viability.
Value asks whether customers will choose or use the solution. Viability asks whether it works for the business under real-world constraints. Answering those questions requires more than collecting requirements. Product managers need knowledge across several domains:
Customers, users, and their unmet needs
Product data and evidence-based decision-making
Market dynamics and competitive alternatives
Revenue models, pricing, cost, and go-to-market considerations
Sales, marketing, legal, compliance, and ethical constraints
A product owner who primarily administers a backlog may perform useful delivery work, but Cagan does not treat backlog management as the defining responsibility of a product manager. Similarly, someone on a feature team may contribute beyond Jira while still spending most of their time coordinating a predetermined solution.
The empowered PM works directly with design and engineering to shape solutions. That does not mean directing designers or assigning developers’ daily tasks. It means representing customer value and business viability while the team discovers what to build.
Empowerment Still Requires Direction
Empowered teams are sometimes mistaken for teams that choose whatever they want to pursue. Cagan rejects that interpretation.
Product strategy belongs to product leadership. Leaders decide where the company will compete, identify important opportunities, make investment choices, and assign consequential problems to teams. Empowerment begins after that strategic work: teams receive latitude to investigate the problem, test assumptions, and determine the solution.
This creates a productive division of responsibility. Leadership supplies context, priorities, resources, and capable people. Teams supply discovery, judgment, experimentation, and execution. Autonomy without strategy produces fragmentation; strategy without team autonomy produces feature factories.
A healthy environment also depends on trust. Teams need room to take responsible risks, learn from failed experiments, and challenge weak assumptions. Leaders should celebrate meaningful progress and learning rather than rewarding feature volume alone.
The Post-ZIRP Reckoning
Cagan connects the current reassessment of product management with the end of the zero-interest-rate era. When capital was abundant, many companies emphasized growth optimization and staffed narrowly defined roles. A tighter business environment has renewed attention to product-market fit, disciplined discovery, and the economics of product investment.
In that climate, organizations are scrutinizing jobs centered on coordination and backlog administration. Cagan expects generative AI to intensify the pressure because many routine communication, documentation, and triage tasks can be partially automated.
His message to product managers is demanding but constructive: assess the work you actually perform, not the title on your profile. Strengthen customer understanding, analytical judgment, market knowledge, strategic thinking, and business fluency. Where possible, demonstrate the model by helping one or more teams work against outcomes rather than feature lists.
Career development also requires skepticism. Cagan warns that much online advice and many certification programs teach a project-management interpretation of the role. Critical thinking is therefore a foundational PM skill—not only for evaluating product ideas, but also for evaluating professional guidance. He recommends investigating a prospective manager carefully because that person will strongly influence which skills the role develops.
How AI Changes the Work
Cagan sees stable principles beneath rapidly changing techniques. Product managers will still need to determine whether a product provides value and can succeed within business, legal, ethical, and operational constraints. The tools used to answer those questions, however, are changing quickly.
Generative AI can help draft documents, explore strategy, triage defects, refine communication, and challenge an initial proposal. Cagan cautions against treating fluent output as reliable judgment. His preferred pattern is to think through the problem first, then use AI to critique, expand, or improve that thinking.
Roles dominated by documentation and workflow administration appear particularly exposed to automation. Empowered product managers remain valuable because their work depends on context, evidence, tradeoffs, and accountability. AI products may even increase the importance of viability: probabilistic systems introduce difficult questions involving compliance, safety, intellectual property, ethics, and customer trust.
The Product Operating Model
Cagan’s book Transformed presents the product operating model as a collection of principles found across successful product companies, including organizations outside Silicon Valley. The model brings together three major areas: product strategy, product discovery, and product delivery.
Its purpose is not to impose another rigid process. Cagan emphasizes principles over ceremonies, learning over blame, and innovation over artificial predictability. Teams should receive problems worth solving, develop genuine ownership, address risks during discovery, and run fast but responsible experiments. Delivery should favor small, frequent, independently releasable changes supported by strong instrumentation and monitoring.
Effective product organizations also require complementary competencies. Cagan highlights product management, design, engineering, marketing, and leadership, with the core team often centered on the product manager, product designer, and technical lead. None of these roles can compensate indefinitely for weak leadership or missing expertise.
Product Operations and the Founder’s Role
Cagan does not dismiss product operations outright. He sees legitimate value in high-leverage specialists—such as user researchers and data analysts—who support multiple teams. The warning sign is a product operations function dominated by governance, process enforcement, or work that product managers and leaders should perform themselves.
He offers similarly nuanced advice to founders. Before product-market fit, founders should usually retain responsibility for value and viability rather than hiring a product manager prematurely. At that stage, separating product judgment from founder vision can create friction and slow learning.
As the company grows—Cagan suggests roughly 20 to 25 engineers as a common transition point—the founder may no longer be able to serve effectively as the sole product person. That is when an experienced product manager can help scale product judgment without reducing the role to coordination.
Moving Beyond the Performance
The remedy for product management theater is not a new title, framework, or ceremony. It is a clearer system of accountability. Leaders choose important problems and provide strategic context. Cross-functional teams discover solutions. Product managers bring deep customer, market, data, and business knowledge. Success is judged by outcomes rather than the volume of shipped features.
For individual PMs, the implication is equally clear: become harder to replace by becoming more capable, not more administratively busy. The future belongs less to custodians of process than to people who can help a team determine what is worth building, why it should work, and whether it actually did.
