Why Product Management Is a Team Sport: Building Autonomous Cross‑Functional Teams

Product management is described as a team sport, but friction arises when multiple teams must interact, leading to the proliferation of project‑management methods, inboxes, and dependency handling.

Removing inter‑team dependencies and creating autonomous product teams eliminates this friction.

1. Cross‑Functional Teams

Each team should possess all skills and expertise needed to achieve its goals, including functions such as customer success, marketing, and compliance, while ensuring diversity of background, experience, and perspective.

A spider‑chart model can help visualize skill overlap and gaps when forming teams.

Diverse teams, like Transferwise’s product team that includes designers, engineers, bankers, and lawyers, can handle end‑to‑end tasks (e.g., adding a new currency conversion) without relying on other departments.

Conversely, siloed departments create bureaucratic nightmares with extensive approval processes.

2. Autonomy

Traditional command‑and‑control management works only when knowledge resides in a few senior leaders; modern product work requires empowering teams.

Most agile and lean practices stem from the Toyota Production System, which is unsuitable for design teams that need flexibility.

Teams are smarter than any single leader, possessing more information and closer proximity to customers, so they should be trusted to decide how to achieve outcomes.

2.1 Motivation

Daniel H. Pink’s research, presented in Drive , shows that financial rewards are not the primary motivator; autonomy, mastery, and purpose are.

2.2 Autonomy Means Maintaining Agility

True autonomy removes dependencies on shared resources or central teams, allowing each team to own everything needed to deliver product goals, including marketing execution without waiting on product.

2.3 Autonomy Means Everyone Can Contribute

Every team member should participate, leveraging their skills to solve challenges; collaboration across engineering, design, product, and research yields unexpected insights and better products.

3. Alignment and Autonomy

Successful autonomous teams must also take responsibility for outcomes; leadership still sets vision, goals, and boundaries, ensuring teams stay aligned with company objectives.

The Spotify squad‑tribe model illustrates high alignment and high autonomy as the ideal quadrant for innovative organizations.

4. Summary

The author recounts personal experience building a semi‑autonomous team at a London SaaS startup, emphasizing the importance of gathering all stakeholders, focusing on customer problems, and allowing junior developers to propose solutions that solved the majority of issues.

Ultimately, product leaders should empower autonomous teams, giving them space to reach their best performance.