Spotify, Airbnb, and Zappos all use small, cross-functional teams, but they make very different tradeoffs around autonomy and ownership.
Spotify organizes 6–12 person “squads” around specific feature areas, with a Product Owner in each. Squads are highly autonomous and choose how they operate, while tribes coordinate related squads through product, design, and tribe leads. This is clever for agility: teams can move quickly without waiting for centralized processes. But there is a risk in optimizing around a particular feature area—the structure could encourage teams to perfect their piece without always seeing the whole product experience.
Airbnb also uses modular, cross-functional teams, but its philosophy is more vision- and outcome-driven. Rather than continuing to push a feature simply because it is planned, teams can adapt as the product vision evolves. I especially like its three PM archetypes: Pioneers push new ideas, Settlers focus on growth and impact, and Town Planners handle scale. That gives PMs different kinds of ownership as a product matures. The potential flaw is that dividing PM responsibilities could still fragment the product perspective—each team may optimize its own stage or objective rather than the experience as a whole, potentially producing highly polished but overengineered features.
Zappos takes decentralization furthest through Holacracy: autonomous “circles” self-organize under a constitution, eliminating traditional managers and titles. The idea is compelling, but Zappos’ experience suggests that removing hierarchy can create more coordination problems: too many circles, unclear ownership, and slower decisions.
I’d choose Airbnb. Its vision-first approach seems like the best balance: enough structure to coordinate people, but enough adaptability to change direction when the original plan stops serving the user. The traditional hierarchical structure facilitating coordination between the cross-functional teams significantly simplifies organizational complexity compared to how convoluted a matrix- and circle-structured team can become.
