Skip to content
Nerdy beta

Small, Cross-functional Teams

Activity Product Management Team Topologies

When the whole team weighs in on every product decision, nothing moves fast. A product trio concentrates decision rights in three complementary perspectives.

Overview

A product trio is the PM, Designer, and Tech Lead working as a tight decision-making unit. The trio brings a balanced perspective: viability (PM), desirability (Designer), and feasibility (Tech Lead). The whole team has input, but the trio has decision rights.

This practice matters for stream-aligned teams because it concentrates product decisions in a small group with complementary viewpoints, reducing the coordination overhead of involving the entire team in every discovery decision while keeping all three lenses represented. Without a trio, teams tend to default to whoever is loudest or most senior, which usually means feasibility dominates and desirability gets discovered too late.

Trio? Quartet? Quintet?

Marty Cagan’s original trio idea assumed three disciplines covered the decision space: viability, desirability, feasibility. That was a reasonable bet in 2008, but the space has evolved.

A team building a personalization engine might need a data scientist at the table, not downstream. A team navigating healthcare compliance needs a domain expert with deep industry knowledge, not a consultant they ping on Slack. A team instrumenting growth loops needs analytics embedded in discovery, not dashboards they occasionally review after the fact.

The principle isn’t “three people.” The principle is: the smallest group that holds every perspective required to make good product decisions without waiting on anyone outside the room. If that’s four people, call it a quartet. If it’s five, call it a quintet. The moment you add someone who doesn’t change the quality of decisions, you’ve crossed the line from cross-functional to committee.

Resources