Product Team

A product team is the cross-functional group responsible for discovering, building, shipping, and improving a product or feature area, organized around a persistent customer outcome. It typically includes a product manager, one or more designers, and engineers, sometimes plus a data analyst, researcher, or domain expert. It is increasingly described as the unit of work in modern product organizations. The dominant model in 2025 is small (5 to 9 people), durable (stays together across multiple cycles), and empowered (owns outcomes, not just outputs).

The classical structure is the "product triad" of product manager, design lead, and engineering lead, sometimes called the "three-in-a-box" or "trio." Marty Cagan's Empowered (2020) draws a hard line between two team archetypes: empowered product teams (given an outcome to achieve and the autonomy to figure out how) and feature teams (given a list of features to build and a deadline). Cagan argues that the difference correlates with whether the team produces real innovation versus expensive output. Other widely-used team models: Spotify's tribes / squads / chapters / guilds (popularized 2012, since publicly walked back as not the ideal it appeared to be), Team Topologies (Matthew Skelton and Manuel Pais, 2019: stream-aligned, platform, enabling, and complicated-subsystem teams), and Amazon's two-pizza teams (small enough that two pizzas can feed them, around 6 to 10 people, with clear ownership). The 2024 to 2026 shift: AI-augmented product teams are becoming smaller still, with the boundaries between PM, design, and engineering blurring as AI tools handle more of the routine production work, and the highest-leverage skill becoming judgment about what to build rather than execution of building it.

What founders get wrong: Building product teams without empowering them. Founders hire a PM, designer, and engineers, call it a product team, and then make every meaningful decision themselves. The team executes orders rather than owning the outcome, which produces shipped features but not learning or innovation. If the founder is the only one who can say "no" to a feature, you don't have a product team; you have a delivery team.

Related: Product Management · Product Discovery · Agile · Chief Product Officer

FAQ

What is a product team?
The cross-functional group (typically a product manager, designer, and engineers, sometimes plus a data analyst or researcher) responsible for discovering, building, shipping, and improving a product or feature area. Often organized around a persistent customer outcome rather than a project.

What is the product triad?
The classical product team leadership structure of product manager, design lead, and engineering lead, sometimes called the three-in-a-box or trio. The three jointly own the team's outcomes, with the PM coordinating across disciplines but not directing the others. Popularized by Marty Cagan.

What is the difference between an empowered product team and a feature team?
An empowered product team is given an outcome to achieve and the autonomy to figure out how. A feature team is given a list of features to build and a deadline. Marty Cagan's Empowered argues this distinction correlates with whether the team produces real innovation versus expensive output.