The Foundation of Product

Marty Cagan argues that the foundation of a strong empowered product team is unencumbered, direct access to four constituencies: customers and users, product data, business stakeholders, and engineers. He explains that an empowered product team exists to solve important problems in ways users love, are technically possible, and work for the business. Each form of access serves a different purpose, from discovering needs and validating solutions to understanding business constraints and what technology makes newly possible. Cagan suggests this access is the true source of innovation and good decisions, and that protecting it is worth fighting for, even at the cost of leaving a company where it is denied.

01Key takeaways

• Protect the product team's direct access to customers and users from any gatekeeper, including sales, marketing, and customer success.
• Give product managers direct access to product data, using governance and anonymization systems rather than restricting access.
• Build real trust with business stakeholders so they believe constraints will be addressed, and check gray-area viability with them before building.
• Keep product managers and designers in daily contact with engineers, since engineers see what technology makes newly possible.
• Engineers should observe users struggling with the product when possible, since this often sparks better solutions.
• If a company blocks access to these four constituencies despite repeated explanation, consider whether it is the right place to practice strong product work.

02Key sections

Purpose of an empowered product team

Cagan distinguishes empowered product teams from feature or delivery teams, defining their job as solving important customer or company problems with feasible technology and sound business outcomes.

Direct access to customers and users

Product teams need unfiltered access to users and their behavior data, and engineers benefit from seeing users struggle firsthand. Gatekeepers across the organization should not block this access.

Direct access to product data

The product manager owns decisions based on data and must access it directly, with governance and privacy handled through systems rather than by restricting access.

Direct access to business stakeholders and engineers

Product managers should build trust with stakeholders for viability constraints, and engineers should interact daily with product staff since they know what technology makes newly possible.

Protecting access as the basis for innovation

Cagan argues that protecting these four channels is the most important battle a product team can fight, and that teams unable to win it may need to find a better company.

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.