By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
Lenny's PodcastThe ultimate guide to product operations | Melissa Perri and Denise Tilles
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
At a glance
WHAT IT’S REALLY ABOUT
Why Product Operations Is Transforming How Companies Build Products At Scale
- Melissa Perri and Denise Tilles break down the fast‑emerging discipline of product operations and why it has exploded across modern product-led companies. They argue that product ops exists to free product managers and leaders from operational drag—data wrangling, process chaos, and ad-hoc research—so they can focus on strategy and outcomes. The role is organized around three pillars: business & data insights, customer & market insights, and product processes & practices, with emphasis shifting by company stage. They share how to know when you need product ops, how to hire and structure it, how it differs from product and project management, and case studies from companies like Uber, Amplitude, and Athenahealth.
IDEAS WORTH REMEMBERING
5 ideasProduct ops exists to maximize the time PMs spend on strategic work.
Instead of PMs burning 20–30% of their time chasing data, scheduling research, and reinventing processes, product ops builds shared systems and infrastructure so PMs can focus on customer problems, strategy, and outcomes.
The three pillars of product ops should be tailored to company stage.
High-growth startups usually need help first with business & data insights, while large or transforming enterprises often benefit most initially from process, governance, and operating model support; customer & market insights is a major underused opportunity across both.
Product ops informs decisions but should never make product decisions.
Product managers must keep ownership of vision, strategy, prioritization, trade-offs, and stakeholder negotiations; product ops supplies clean data, efficient research systems, and consistent processes to support those decisions—not replace them.
Start small: one sharp hire focused on the biggest pain point.
Most successful product ops functions begin with a single person focused on a clearly defined, high-impact problem (e.g., dashboards for product metrics, research participant recruiting, or roadmap governance), demonstrate quick wins, and only then expand.
Hiring for product ops depends heavily on the pillar you’re addressing.
For business & data insights, look for analyst/BI or consulting profiles strong in data storytelling and BI tools; for process & practices, look for an ex-PM with high EQ and systems thinking; for customer & market insights, seek research-ops or UX research profiles with a process-orientation.
WORDS WORTH SAVING
5 quotesDo you want to hire 10,000 product managers and let them all do these things off the side of their desk, or do you want them concentrating on strategic work the majority of the time?
— Melissa Perri
Product operations does not take away decision-making rights from the product manager. It's there to inform them.
— Melissa Perri
If you try to serve everybody, you serve no one.
— Denise Tilles
We don't usually need another agile coach telling us how to run a standup. We need people to come in and help us figure out who's invited to cross-functional roadmap reviews and how to communicate at the right level to executives.
— Melissa Perri
My current chief product officer said he will never go anywhere else that doesn’t have product ops.
— Melissa Perri (relaying a CPO’s view on Athenahealth)
High quality AI-generated summary created from speaker-labeled transcript.
