Product vs. Project Operating Models - All Things Product Podcast with Teresa Torres & Petra Wille

This podcast episode asks whether an organization can run a product operating model and a project operating model at the same time. Teresa Torres and Petra Wille contrast the two: project models organize around fixed outputs and deadlines, while product models organize around outcomes and durable, cross-functional teams. They explain how software delivery history shaped today's tensions, and when project-style work still fits, such as one-time compliance efforts like GDPR. The hosts argue the answer is usually "yes, and," treating each model as a lens rather than a rival camp. The discussion matters for PMs who must coordinate product work with compliance, finance, and HR teams still operating in project mode.

01Key takeaways

• Treat operating models as tools rather than rules to follow dogmatically.
• Use project models for one-time, compliance-driven work with a clear end state.
• Apply product models to evergreen challenges that need durable, cross-functional teams.
• Look at both outcomes and outputs, using whichever lens fits the context and constraints.
• Watch for recurring problems over time as a signal that a work item should move to a product model.
• Use feedback loops to test whether a piece of work is actually done.

02Key sections

The core question

The episode opens by asking whether product and project operating models can coexist in one organization. The hosts frame it as a common, practical dilemma rather than a binary choice.

Defining the two models

Project models focus on delivering defined outputs on a timeline, while product models focus on outcomes and ongoing problem-solving. The distinction is grounded in why outcomes matter more than outputs.

Where project models still fit

One-off, compliance-driven initiatives such as GDPR or accessibility work often suit project framing. The hosts also examine gray areas where the right model is less obvious.

Working across models

Product teams must collaborate with departments still in project mode, and even product teams sometimes need project-style thinking. Recognizing repeating patterns helps decide when to switch models.

Feedback loops and done-ness

Feedback loops reveal whether work is truly finished or merely paused, helping teams judge completion under either model.

03From the post

“Listen to this episode on: Spotify | Apple Podcasts Can an organization operate with both a product and a project mindset—at the same time? In this episode, Petra Wille and Teresa Torres unpack one of the most common operating model questions in product organizations today. They dive deep into the”

04Frameworks mentioned

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