Real Talk about Empowered vs. Feature Product Teams

Jones distinguishes feature teams, which receive solutions to build, from empowered teams, which receive problems to solve. Teams have latitude to find a solution, but they are accountable for whether it works, such as reducing customer onboarding time by 25%.

Jones says feature factories can ship plenty while making little difference, especially when business leaders hand teams disconnected requests. Empowerment also needs direction: leadership defines and allocates problems so teams’ work fits a coherent strategy. Leaders should know when to guide teams and when to step back.

Jones warns that teams can game narrow metrics, such as using a prominent banner to hit a target. He recommends treating key results as proxies for a broader objective and giving cross-functional teams shared outcomes. That shared responsibility can prompt engineers, designers, and product managers to question weak assumptions together.

Jones describes a product operating model through three areas: how to build, how to solve problems, and how to choose which problems matter. Product strategy gives teams focus and helps coordinate their work. He says focus also requires leadership to say no to many otherwise appealing ideas.

Jones advises product managers to become experts on their customers, product data, and business stakeholders to earn a seat at the table. When a team receives a feature to build, asking what success means can shift discussion toward outcomes. To rebuild trust, share disappointing results openly, explain what was learned, and use that insight in the next effort.