Everyone says good PMs have product sense, but how many people can truly define what good product sense is?
In this episode, we’re joined by Kevin Sung, VP of Product at Life360, where he runs ecosystem strategy, the foundational infra and developer experience group, and works alongside the AI platforms team. Before Life360, Kevin spent several years at Dropbox, leading the Usability team that owned performance, reliability, and CX.
Kevin’s worked in both the goal-seeking world and the customer-obsessed one, and he’s clear about which one AI is about to make obsolete.
In this episode, Kevin shares:
Why product sense is customer centricity
The difference between lazy product management and rigorous product craft (hint: it’s how strong your opinion is before you start)
How his team at Dropbox found $24M in ARR hiding in a cohort nobody was looking at
And how to get leadership to fund the unglamorous quality work that never wins a roadmap fight
1. If your job is running every permutation, AI already does it better
Kevin isn’t in the doomer camp on AI and PM roles. But his reasoning for why the job survives is sharper than the usual reassurance.
AI removed engineering headcount as the bottleneck on learning — you can prototype and validate in days instead of quarters. That doesn’t reduce the need for judgment.
“In a world where you can now ship lots and lots of ideas quickly, it becomes even more important now to have really strong product sense and customer centricity in order to decide that you are shipping the right things.”
He’s skeptical of the 10x-your-experiments crowd for a specific reason: someone is on the other end of all those experiments, and a product that changes on you every day makes them a test case. Then comes the line that should make a few PMs uncomfortable:
“If all you’re doing is facilitating maximalist tests, an AI will always outperform you, because they will be able to come up with every permutation and actually ship it. So then you are actually obsoleting your own job.”
Product takeaway: Audit what part of your team’s week goes to generating and coordinating options versus deciding between them. The first half is getting automated. If your PMs can’t articulate a customer-grounded hypothesis before an experiment runs, you don’t have a product function — you have a permutation engine.
2. Lazy product management vs. Product craft
Kevin has a refreshingly straightforward definition of product sense:
“What is product sense? It is customer centricity. It is understanding a customer’s painful needs and being able to translate that into business value [...] One of the big differences between the two is the strength of your opinion, and that opinion is based on your understanding of what a customer’s needs are.”
The rigorous version sounds like this: based on what I understand about this customer’s life, here is a painful problem, here is my hypothesis for solving it, here’s how their behavior should change, here’s the business impact. Then you find out whether you were right — and either way you get smarter.
The lazy version outsources all of that to volume. Kevin points out this predates AI entirely; it’s the same instinct that had teams running a hundred A/B tests a day and Google testing shades of blue. AI just made it cheaper.
There’s a second-order risk too. If everyone lets the same handful of models generate their ideas, everyone’s product converges.
Product takeaway: Make the hypothesis a required artifact, not an optional one. Before anything ships, someone should have written down what they believe about the customer and what behavior change would prove them right. That document is the difference between learning something and generating noise — and it’s the part a model can’t write for you.
3. Don’t let data quietly become a spreadsheet maximization game
At Smule, Kevin led growth in an environment he describes candidly as goal-driven: here’s a number, find twenty ways to move it. When a key metric dropped, they’d spin up a tiger team and build a list of hypotheses.
And then:
“Seven times out of 10 the culprit would be found by ultimately one of us running through the app itself, going through a flow, and being like, ‘Oh, this is clearly the thing that was broken.’”
His conclusion isn’t anti-data. It’s about what happens when data is the only input.
“If all you do is look at data and you use data to then double-check other data and form hypotheses on that, and you’re not talking to the customer, you’re not experiencing the product yourself, you can very easily just turn this into a spreadsheet maximization game.”
Dropbox showed him the other model — real-world Wednesdays, a large user research team, an expectation that you talked to two to six customers a week. He also makes a sharp distinction about growth work itself: growth is gasoline on a fire. If the product genuinely solves a painful problem, growth accelerates it. If it doesn’t, you get a pop and a drop.
Product takeaway: Put a standing constraint on your team that every metric investigation includes someone actually using the product through the affected flow. It’s the cheapest debugging step available, and it’s the one most often skipped — and if your instrumentation can’t tell you where users are struggling without a manual walkthrough, that’s the real finding.
4. Resentment compounds over time
At Dropbox, Kevin led a group called Usability, spanning key user journeys, service performance and reliability, and the entire out-of-product experience — because your relationship with a product includes every moment you’re outside of it trying to get help. The team spent a year making lots of small things better and produced roughly $24 million in ARR from churn reduction alone.
The hypothesis they pitched it on was wrong.
They’d argued that first impressions matter most, so the gains would show up in month-one and month-two retention. Those numbers didn’t move at all. What moved was month 13+ — fifteen years of accumulated customers, improving by roughly half a percentage point. At that population size, half a point was eight figures.
Kevin’s explanation for why is the part worth stealing. Their time-to-visual-complete metric averaged around 15 seconds globally, and every one of those slow loads was a small deposit:
“These things create moments of what I call moments of resentment. Like, man, all my files are stuck in here. I can’t remove them, but I’m frustrated, but I can’t leave you. And then it just builds up and builds up and builds up.”
Frustrated-but-locked-in users don’t churn on the day they get frustrated. They churn on the inciting incident — an outage, a trust-breaking event, a price increase. The price increase doesn’t cause the churn. It collects on years of resentment.
Product takeaway: Your loyal users absorb the most accumulated friction, and their churn stays invisible until something triggers it all at once. Before your next price change or migration, ask what the resentment balance looks like on your longest-tenured cohorts — a small lift on a very large denominator usually beats a large lift on a small one.
Chapters
00:00 Introduction
04:06 Defining "product sense"
07:45 How the PM role is evolving
10:20 Kevin's growth lessons from Smule
14:22 The $24M retention bet
18:29 Resentment builds until users snap
22:38 Selling a bet you can't model
24:36 Enshittification and paper cuts
27:51 Life360, where trust is the product
32:23 Conclusion
Links
What does LogRocket do?
LogRocket’s Galileo AI watches user sessions for you and surfaces the technical and usability issues holding back your web and mobile apps. Understand where your users are struggling by trying it for free at LogRocket.com.