Evidence receipt / preference
Published · transcript-backedJackson Shuttleworth: preference
15 Dec 2024 Lenny's Podcast Behind the product: Duolingo streaks | Jackson Shuttleworth (Group PM, Retention Team)
“Leaderboards is the best vector for doing it, so that team does a lot of leaderboards work, but every now and then I have an idea that I think will be highly retentive, and I will go in, and I'll pitch to them, and then we'll do some change to the leaderboard to make it more retentive.”
Source trail
Everything needed to verify it.
- Speaker
- Jackson Shuttleworth
- Attribution
- Verified speaker
- Claim type
- preference
- Recorded
- 15 Dec 2024
- Publisher
- Lenny's Podcast
Transcript context
…Versus feature-oriented. So, basically your teams are structured around a metric/a goal/outcome versus we own this feature, or this product. So, retention owns streak, I guess, but that's only because we've seen streak drive CURR better than any feature. But we are not, we have this IAP hook with our streak freeze purchases, there are other teams that work on, that can and have worked on the streak, because it's not ours to say, no, no, no, we do all the iterations here, we just know that it drives our metric better. In the same way that leaderboards, we have a team that focuses on how much time you spent, we want users to spend more time on Duolingo so they're learning more. Leaderboards is the best vector for doing it, so that team does a lot of leaderboards work, but every now and then I have an idea that I think will be highly retentive, and I will go in, and I'll pitch to them, and then we'll do some change to the leaderboard to make it more retentive. But I do think having that clear metric of we're trying to drive CURR not we're trying to just make this feature better, helps at least make sure, give the team clear marching orders, and that focus I think is really good for prioritizing backlog. Cool. This is a really important point, this is the same way Airbnb worked, when I worked there for a long time, is it's, here's a goal that we want your team to be responsible for, you can work on any product you need to hit this goal, as you said, often various products are most connected to what you're doing, but what you're describing is, even though a team's kind of... I imagine you own it from a [inaudible 01:07:29] perspective, and you're like are the shepherd of this part of the feature because it hits your goal, helps your goal most. But any other team can come in and be like, hey Jackson, we need to work on some streak stuff to help with learning, you're like, go for it. Just a tangent there. Do they work really closely with your team if they want to do some work in the code? How does that work logistically?…
Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.