Product StrategyEmerging Pattern

Organize teams around problems to solve, not products to build, to stay open to better solutions

Q: How many founders have validated "organize teams around problems to solve, not products to build, to stay open to better solutions"?

1 founder has proven this pattern works. Examples include Fidji Simo (Facebook Live).

When teams identify with a product name ('the Q&A team'), they become invested in that specific solution even when better alternatives emerge. Organizing around the problem ('helping celebrities engage with audiences') keeps teams flexible to pivot when research reveals superior approaches.

When to use

When structuring product teams or naming projects, especially in early exploration phases where the best solution isn't yet known

Don't do this

Naming teams after their current product or feature, which creates psychological attachment to solutions rather than outcomes

1 Founder Who Did This

Facebook Liveby Fidji Simo

Team organized around 'helping celebrities engage with audiences' discovered through customer conversations that video was better than text Q&A, enabling pivot to Live

Result:Facebook Live became a major product category; would have been blocked if team identified as 'the Q&A team'

Read full story →