The Product Model and Org Design

Marty Cagan argues that moving to the product model rarely requires a reorganization, because org design is largely orthogonal to whether a company adopts product principles. He describes the two dominant org models, the General Manager (GM) model and the Functional model, plus a common hybrid, noting each makes some things easier and others harder. The right choice depends mainly on business strategy, product vision, and product strategy: a portfolio of loosely related products fits the GM model, while a tightly integrated experience fits the functional model. He warns that reorgs often just rearrange the deck chairs, since product leadership quality, team skills, and culture matter more. Strong, empowered teams can succeed under any structure.

01Key takeaways

• Don't assume a product transformation requires a reorganization; first check whether structure is actually the bottleneck.
• Choose the org model based on business strategy and product vision, not on a desire to look like a product company.
• Use the GM model for portfolios of loosely related products and the functional model for tightly integrated experiences.
• Recognize that every org design trades some things easier for others, such as coaching being harder under a GM without functional managers.
• Invest first in product leadership quality, team skills, and culture, since these drive outcomes more than structure.
• Separate reporting structure from team topology so you can change one without disrupting the other.

02Key sections

Reorg is usually unnecessary

Cagan says the common question of whether a product transformation requires reorganizing is usually answered no, and that the question often reveals confusion about the purpose of org design.

GM and functional models

He contrasts the GM (business unit / single-threaded leader) model with the functional model, noting that both can produce excellent products, as Amazon and Apple illustrate.

Strategy drives org design

The best org model follows from business strategy, product vision, and product strategy: loosely related portfolios favor GM, tightly integrated experiences favor functional, and a hybrid suits shared platforms.

People and culture matter most

Reorganizing is tempting but often misses the real issues, which are the quality of product leaders, team skills, and product culture; strong teams overcome structural obstacles.

Org structure vs. team topology

A footnote distinguishes org structure (reporting lines) from team topology (what teams own and how they collaborate), which can change independently.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.