Transformed FAQ

This FAQ, published by Marty Cagan after his book TRANSFORMED, answers recurring reader objections about moving from feature teams to empowered product teams. It argues that the product manager role changes rather than expands, shifting from project management toward product discovery. It clarifies that transformation is earned progressively with executive trust rather than requiring a fully supportive CEO, and that individual contributors can meaningfully improve their environment. The piece also addresses Product Ops ambiguity, criteria for 'best' companies, and when feature teams are still appropriate.

01Key takeaways

• Expect the product manager role to shift toward discovery, with delivery coordination handled by dedicated project or delivery managers.
• Build executive trust incrementally by demonstrating outcomes at each level rather than waiting for full CEO buy-in.
• Individual contributors can raise their own skill level, which often leads to recognition and broader influence.
• Evaluate Product Ops definitions individually, keeping helpful research and analytics support while avoiding anti-patterns.
• Focus on underlying product principles rather than copying a company's specific culture or processes.
• Leave feature teams in place only where discovery is unnecessary, such as bug fixes or large technical debt work.

02Key sections

Role change, not role expansion

The product manager job shifts from project management and meetings to product discovery, so responsibilities are changed rather than added. Delivery coordination is offloaded to project or delivery managers.

Earning executive trust progressively

Transformation is not binary on CEO support; leaders advance through levels as they demonstrate outcomes, and individual contributors can drive change by up-leveling their own skills.

Ambiguity around Product Ops

Product Ops has many definitions, some helpful (quick qualitative and quantitative answers for product teams) and others anti-patterns, so a single verdict is difficult.

Choosing role models and practices

The author uses sustained innovation as the criterion for 'best' companies, focuses on underlying principles rather than cultures, and argues that practices transfer across differing companies.

When feature teams are acceptable

Feature teams suffice for bug-fix work or major technical debt efforts where discovery is rarely needed, though morale differences should be considered.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.