How to build your product team from scratch, attract top product talent, go multi-product, and more
Executive Summary
Lenny's Podcast episode, sponsored by Cloudinary and OneSchema, in which Lenny Rachitsky talks with Rohini Pandhi, product leader for Mercury's product expansion team and formerly seven years at Square, about building a product team from scratch and going multi-product. Mercury famously had zero product managers until roughly 400 employees - Pandhi explains that bottlenecks forced the change, because somebody does the PM duties even when nobody holds the title. She describes Mercury's three PM archetypes - pioneers for zero-to-one, town settlers for growth-stage products, and city planners for mature ones - and what actually attracts top product talent. Her multi-product lesson from incubating half a dozen new lines in a year: seedlings planted too close to the core banking org get crushed, so new products need real organizational distance. She also argues for investing in quality and user experience over pure metric-moving as a differentiator. PARTIAL COVERAGE: this summary highlights the team-building and multi-product lessons; hiring tactics are not covered in detail. These are Pandhi's own views and experiences, not independently verified.
Key Takeaways
PMs at 400 employees
Mercury ran without product managers until about 400 staff, when bottlenecks forced the hire.
The duties exist anyway
Her point: PM work gets done by design and engineering even with no PM in the building.
Three PM flavors
Pioneers for zero-to-one, town settlers for growth products, city planners for mature ones.
Thirty PMs later
Mercury's team grew to around 30 PMs, more than half senior, within two years.
Seedlings need distance
New product lines planted inside the core banking org struggled to grow; separation fixed it.
Six launches a year
Her expansion team incubated and scaled half a dozen new product lines in one year.
Quality as wedge
She argues investing in UX and quality differentiates more than chasing metric bumps.
The Conversation Breakdown
PMs at 400 employees
⏱ Untimed topicMercury ran without product managers until about 400 staff, when bottlenecks forced the hire.
The duties exist anyway
⏱ Untimed topicHer point: PM work gets done by design and engineering even with no PM in the building.
Three PM flavors
⏱ Untimed topicPioneers for zero-to-one, town settlers for growth products, city planners for mature ones.
Thirty PMs later
⏱ Untimed topicMercury's team grew to around 30 PMs, more than half senior, within two years.
Seedlings need distance
⏱ Untimed topicNew product lines planted inside the core banking org struggled to grow; separation fixed it.
Six launches a year
⏱ Untimed topicHer expansion team incubated and scaled half a dozen new product lines in one year.
Quality as wedge
⏱ Untimed topicShe argues investing in UX and quality differentiates more than chasing metric bumps.
Core Frameworks & Ideas
Pioneer-settler-planner - Pandhi's PM taxonomy
Match the PM's strength to the product's maturity stage.
Seedling distance - her incubation rule
New product lines fail when organizationally smothered by the mature core.
Bottleneck trigger - the PM hiring signal
Hire PMs when cross-functional load on design and engineering becomes the constraint.
Actionable Next Steps
- ✓Map who actually does PM duties on your team today.
- ✓Classify your PMs or yourself as pioneer, settler or planner.
- ✓Check whether your newest initiative sits too close to the core org.
- ✓Pick one quality investment you have deferred for metric work.
Notable Quotes
“somebody's doing the PM duties even if you don't have a PM”
“We use this idea of like a pioneer, a town settler, and a city planner”
“made it hard for that new product to even grow”
The One Thing to Remember
Rohini Pandhi on scaling product at Mercury: somebody always does the PM duties, match pioneers-settlers-planners to the product's stage, and give seedlings distance from the core.