Marty Cagan on Product Teams and Product Management

Marty Cagan on Product Teams and Product Management

transcriptproductproduct-managementproduct-teamsdiscoveryempowered-teamsfeature-teamssvpg

Marty Cagan on Product Teams and Product Management

Marty Cagan in conversation with Lenny Rachitsky. Cagan draws the line between feature teams and empowered product teams, explains Jobs’s disease theory, and lays out the three sacred PM access rights.

Key ideas

  • Feature teams vs. empowered product teams. Feature teams are handed a prioritised roadmap of solutions; real product teams are given problems to solve. The PM role is so different in each context that Cagan argues the same title should not apply to both.
  • Steve Jobs’s disease theory. Companies lose their product mojo because, as they scale, marketing, sales, and finance people rise to leadership whilst good product people leave. The cycle accelerates: new leadership is even further from product quality, and the company ossifies.
  • Product discovery = solution focus, not problem focus. The team usually knows the problem already; the scarce resource is time on solution discovery (valuable, usable, feasible, viable). Spending weeks re-validating a known problem wastes the clock.
  • Three sacred PM access rights. Direct access to users/customers, direct access to engineers, and direct access to stakeholders. Any structure that mediates these three connections breaks the PM role.
  • Scaling with leaders, not process. The only path to good outcomes at scale is developing coaches and empowered leaders. Process-first scaling (SAFe, repackaged waterfall) destroys product quality.

Feature teams vs. empowered product teams

A feature team receives a prioritised roadmap — a list of features requested by stakeholders — and is asked to design, build, and ship them. The PM role is essentially project coordination. Output, not outcome, is the measure of success.

An empowered product team receives problems to solve. The PM must bring four categories of knowledge the team cannot generate itself:

  1. Deep customer and user knowledge — Cagan was required to visit 30 customers before making any product decisions as a new PM.
  2. Data fluency — how the product is used, trend lines, sales and user analytics.
  3. Business context — how the product is marketed, sold, monetised, and what regulatory or compliance constraints apply.
  4. Competitive and industry knowledge — trends, competitors, landscape shifts.

Steve Jobs’s disease theory

Jobs described this in the 1995 documentary The Lost Interview. As companies grow, product historically becomes less central to promotion. Sales, marketing, and finance leaders ascend. Good product people leave. The cycle accelerates.

Jobs identified two related diseases:

  • The disease of executives who think ideas are 90% of the work. They don’t understand that the craftsmanship of going from idea to product — discovery — is where success or failure is determined.
  • The disease of process people. Scaling via process rather than leaders. Attractive, easy to implement, and ultimately destructive of product quality.

Discovery: problem vs. solution

Two types of discovery:

  • Problem discovery — understanding whether the problem is real, widespread, and worth solving.
  • Solution discovery — prototyping and testing solutions against four risks: valuable, usable, feasible, viable.

The error Cagan coaches against: spending weeks in problem discovery when the problem is already known. The competitive advantage lies in the solution. User research in solution discovery should be evaluative, not validating: find all the reasons users will not use the product.

The three sacred PM access rights

  1. Direct access to users and customers — no mediating layer.
  2. Direct access to engineers — working daily with a set of engineers on shared problems.
  3. Direct access to stakeholders — understanding how to build things that work for the business in real time.

Everything else can be delegated without harm. These three cannot.

Transforming a feature team

Propose a one-quarter experiment to the manager. Ask for a problem to solve rather than a feature to build. Ensure the PM is equipped across the four knowledge areas and has access to discovery techniques. The longest part of the transition is the PM learning discovery skills — typically two to three months.

See also