By Marty Cagan · svpg.com · LinkedIn
Marty Cagan examines how product organizations tackle large, multi-team initiatives, such as a usability redesign or a localization push into a new market, that cannot be owned by a single team. He argues that the core question is who leads discovery and delivery, since letting every team figure it out independently would be inefficient and produce conflicting answers. He compares three approaches: designating a lead team, forming a transient discovery team, or having several teams combine forces. Each carries trade-offs for clarity of ownership, team durability, and shared learning. Because initiatives serve the organization rather than any one team, he suggests the real choice is how to minimize the loss of team autonomy.
01Key takeaways
- Large initiatives spanning many teams need a deliberate decision about who leads discovery and delivery.
- A lead team gives clear ownership, but must keep other teams continuously informed to preserve their buy-in.
- Transient discovery teams concentrate expertise, yet they take accountability away when they rotate back out.
- Combining several teams shares learning but risks design by committee and slow decisions.
- Pick the approach that minimizes loss of team autonomy, since initiatives serve the wider organization.
02Key sections
- Defining initiatives
- Initiatives are product efforts that inherently span many teams, such as responsive design or market localization. Technical re-platforming is treated separately as tech debt work.
- Lead team strategy
- One team takes primary responsibility for discovery and delivery, coordinating others. This gives clear ownership, but other teams can feel excluded if the lead does not keep them informed.
- Transient team strategy
- A temporary, dedicated discovery team is formed and then returns to its original team. It focuses expertise but leaves accountability behind and borrows people from their teams.
- Combo team strategy
- Several teams jointly do discovery, sharing learning, though it often devolves into design by committee with too many decision makers.
- Choosing an approach
- No option is clearly superior for autonomy; the best choice minimizes the sense of lost autonomy, and successful initiatives are worth the effort.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.