By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
Teresa Torres explains the product operating model, a set of first principles popularized by Marty Cagan, which focuses on achieving customer and business outcomes rather than shipping outputs. She contrasts it with the project-based model, argues for starting with pilot teams rather than transforming everyone at once, and connects it to continuous discovery and empowered cross-functional trios. The piece also covers readiness (CEO belief and pain), how the model adapts to startups, large enterprises, regulated industries, and remote teams, and how leaders must change their behavior and manage resistance. It matters because transformation is slow and people-driven, and the guidance is practical for anyone trying to move an organization toward outcome-based product work.
01Key takeaways
- Start the transformation with a few well-chosen pilot teams to prove the model and learn where your organization resists.
- Ensure the CEO both believes current ways of working will fail and feels real pain before committing to transformation.
- Manage by outcomes: evaluate teams on whether their work moves a measurable result, not whether they shipped what was requested.
- Build small cross-functional trios so product, design, and engineering make informed decisions together from the start.
- Expect transformation to take years, and give stakeholders a shared view of thinking rather than every iteration of work.
02Key sections
- Defining the product operating model
- The model is a conceptual set of principles about creating technology-powered solutions that deliver customer value and business results. It applies to how products are built, how problems are solved, and which problems get chosen.
- Readiness and motivation for change
- Companies adopt the model when leaders face competitive threats, see proof from peers, or are frustrated with poor returns on technology investment. The CEO must both doubt the current approach and feel its pain.
- Pilot teams as the path to transformation
- Rather than changing every team at once, a small set of carefully chosen pilot teams proves the model, surfaces obstacles early, and informs how to scale. Selection considers team relationships, willingness to learn, skill mix, customer access, and product stage.
- Roles, rituals, and resistance
- Product trios, leaders who coach rather than dictate, and regular demos that show progress help teams adapt. Common resistance includes lack of time, discomfort with beginner status, and leaders clinging to favored solutions or control.
- Adapting to context
- Startups can begin with a directional outcome and interviews, while large enterprises must manage more stakeholders, resist date-based roadmaps, and show work selectively. Regulated industries and remote teams can also adopt the model with adjustments.
03From the post
“The product operating model is everywhere these days. Since Marty Cagan and the Silicon Valley Product Group released TRANSFORMED: Moving to the Product Operating Model in 2024, it’s become nearly impossible to attend a product conference, scroll through LinkedIn, or walk to the office water cooler without someone mentioning”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.