One of Cagan's five core Product Model (vs. Roadmap Model) concepts. A product team is defined by five traits:
Contrast with feature teams, which are handed a roadmap of features to build and are accountable for output, not outcomes — see Valuable / Usable / Feasible / Viable for how the accountability split plays out for the PM specifically, and Three Conditions for Empowerment for what "empowered" requires in practice.
Feature teams implement solutions and Roadmap (Feature/Project List)s defined by others — stakeholders, sales, customers. Product teams are handed problems and empowered to find and validate their own solutions via Discovery (Product Discovery Process). Diagnose an organization's actual model by checking whether teams receive problems-to-solve or pre-defined features-to-build, regardless of what job titles or team names are in use.
Cagan distinguishes feature teams from product teams by which of the Valuable / Usable / Feasible / Viable risks they own: feature teams are responsible only for usability and feasibility — someone else has already decided what's valuable and viable — while product teams own all four, including value and business viability. This isn't a legitimacy judgment (feature teams aren't lesser), it's a structural explanation for why the product-team PM job is harder: they're accountable for risks a feature-team PM never has to weigh in on.
Feature teams are handed pre-decided solutions by stakeholders and simply implement them, in contrast to the discovery-driven empowered team above. Cagan cites a rough industry rate that only about 20% of shipped features from feature-team organizations actually solve the underlying problem — "a pretty bad efficiency rate." The gap is his core argument for empowered teams: they use Discovery (Product Discovery Process) plus business/customer knowledge to find the solution rather than being handed one. See Gravitational Force Model (Pull Between Project and Product Model), Three Conditions for Empowerment.
Из тем: The Product Operating Model