From John at Stripe, Doshi learned that product teams often want to promote the features that demanded the most work or feel most innovative. Customers may care more about a simpler capability, so marketing emphasis should follow what customers understand and value rather than mirror the engineering effort behind each feature.

Build effort and customer resonance are different variables
Product teams are naturally attached to difficult or innovative work
A seemingly minor feature may deserve greater marketing emphasis
Product language should match terms customers actually understand

“talking about product in terms that customers really understand.”
Shreyas Doshi

“separate the effort involved in kind of building something with the effort you want to put behind talking about said thing.”
Shreyas Doshi

#product-marketing#customer-value#positioning#stripe

Hot Take· 1

Hot Take

Google's $100 Million Filter Made Teams Think Bigger, but Miss Trends

Google Ads had an unwritten bar that opportunities below roughly $100 million in revenue were not worth pursuing because billion-dollar opportunities were available. Doshi says the standard trained him to expand the scale of an opportunity, but the same high bar could cause Google to miss emerging trends whose eventual size was not yet obvious.

Google Ads regularly declined opportunities that were large by ordinary standards
The environment trained teams to ask how a $1 million idea could become a $10 million idea
Pursuing large opportunities sometimes required creating a market rather than finding an obvious one
A high size threshold can filter out trends before their potential is legible

“if it's not going to generate more than 100 million dollars in revenue, it's not worth talking about it”
Shreyas Doshi

“Google missed out on some trends simply because of this filter or this high bar”
Shreyas Doshi

#google#strategy#market-sizing#innovation

Explainer· 1

Explainer

Why Network Effects Alone Don't Explain Twitter's Durability

Doshi attributes Twitter's staying power to the combination of network effects and a core product that remains meaningfully differentiated. Even amid infrastructure, leadership, and cultural problems, that combination made the service harder to displace than a network-effect explanation alone would suggest.

Network effects make an established social graph difficult to reproduce
Twitter also retained a core experience unlike other products
Differentiation and network effects reinforced each other
The combined moat helped the product survive serious organizational challenges

“that core product differentiation combined with network effects has what enabled Twitter to kind of have the staying power it's had.”
Shreyas Doshi

#twitter#network-effects#differentiation#product-strategy

Story· 1

Story

The One Question That Exposed a Weak Acquisition Case

During a Twitter discussion about a possible acquisition for Doshi's team, the room covered strategic, financial, integration, and metrics arguments. Jack listened and then asked how the deal would make users love Twitter more, exposing an important dimension the analysis had only addressed through proxies and for which Doshi had no strong answer.

The team had built a detailed intellectual case for and against the acquisition
Dorsey listened before intervening with one essential question
Metrics and integration plans had become proxies for user love
The unanswered question pushed Doshi toward more rigorous product thinking

“how does this make our users love Twitter more?”
Shreyas Doshi

“at the time I did not have a good answer to that question.”
Shreyas Doshi

#jack-dorsey#acquisitions#user-love#decision-making

Q&A· 1

Q&A

Why Aspiring PMs Should Consider Starting in Engineering

Doshi entered product management by doing customer and product work while still employed as an engineer, then building the solutions himself. He recommends that technically trained people consider engineering as a first job because empowered engineering teams expose them to far more than coding and let them choose a path from direct experience.

Doshi spent about a year doing product work before holding the PM title
Customer meetings revealed that he enjoyed understanding and solving user needs
Engineering on an empowered team can provide broad product exposure
Technical experience remains an advantage after moving into product management

“I was kind of doing the product job without having the title. And I was also the engineer, so I was in this great state…”
Shreyas Doshi

“I often respond with try out engineering”
Shreyas Doshi

#product-management#engineering#career-transition

Takeaway· 3

Takeaway

Why Painful Account Migrations Can Still Be Right

At Yahoo, Doshi learned the power of bundling multiple services under one account. He points to the backlash around moving YouTube users to Google accounts as an example of a painful migration whose long-term integrated experience eventually became normal, while acknowledging that acquired-product fans often resist the change.

A shared account can make a portfolio of services substantially more powerful
Account consolidation can trigger intense resistance from an acquired product's fans
Short-term backlash does not automatically make a platform migration strategically wrong
Users may eventually treat the integrated identity as ordinary

“The interesting part though is nobody remembers that now, right? Like people happily use YouTube.”
Shreyas Doshi

“sometimes it's painful in the short term, even though it might actually be the right answer over the long term.”
Shreyas Doshi

#platform-strategy#identity#acquisitions#migration

Takeaway

The Four Ingredients Behind Stripe's Small-Team Magic

The most distinctive team environment Doshi observed at Stripe combined high energy, sound judgment, low ego, and small teams. He does not present Stripe as flawless; his point is that this particular mix produced unusually effective collaboration and shaped his own thinking as a leader.

Energy increases the pace and ambition of the team
Sound judgment directs that energy toward sensible decisions
Low ego makes strong collaboration easier
Small teams preserve clarity and ownership

“when you combine high energy sound judgment, low ego, and small teams, you just get magic.”
Shreyas Doshi

#stripe#team-design#leadership#culture

Takeaway

Founders Set Culture by Living It, Not Posting It

Watching Patrick and John at Stripe, Doshi concluded that leaders establish culture by repeatedly modeling the behavior they want copied. Consistent user focus and humility communicated the values more strongly than formal statements, especially while Stripe was scaling.

Daily leadership behavior is a stronger cultural signal than stated values
Consistency matters because employees infer what the company truly rewards
User-centricity and humility can be modeled directly
Founders remain visible examples as the organization scales

“setting the culture you want simply by consistently being an example of the behaviors you want to replicate in the organization.”
Shreyas Doshi

“that consistency spoke louder than anything that you might write on a poster on the office walls.”
Shreyas Doshi

#culture#founders#leadership#stripe

Frameworks in this episode

Band-Aid Test for Execution Problems

High Agency Model

Opportunity-Cost Prioritization

Pre-Mortem with Tigers, Paper Tigers, and Elephants

Three Levels of Product Work

Insights & moments

⚡Myth Buster· 1

The Hardest Feature to Build Isn't Always the One to Market

◆Hot Take· 1

Google's $100 Million Filter Made Teams Think Bigger, but Miss Trends

✶Explainer· 1

Why Network Effects Alone Don't Explain Twitter's Durability

❝Story· 1

The One Question That Exposed a Weak Acquisition Case

?Q&A· 1

Why Aspiring PMs Should Consider Starting in Engineering

▲Takeaway· 3

Why Painful Account Migrations Can Still Be Right

The Four Ingredients Behind Stripe's Small-Team Magic

Founders Set Culture by Living It, Not Posting It

Myth Buster· 1

Hot Take· 1

Explainer· 1

Story· 1

Q&A· 1

Takeaway· 3