What If You’re Wrong About Why People Are Sticking Around?
Every product team has a story about why their product works.
It usually sounds like this: "We solve [functional problem] for [type of user] better than anyone else." The roadmap serves that story. The marketing tells that story. The dashboards measure that story.
And sometimes that story is wrong.
Not wrong about whether the product works. Wrong about why people stay.
The Job Has Layers. The Team Usually Sees One.
In , every job has . is the practical outcome — track the run, send the report, manage the project. is how someone wants to feel — confident, in control, not stupid. is how they want to be perceived — competent, organized, serious, part of something.
These aren't three different jobs. They're three dimensions of the same job. But here's the thing: teams almost always assume is the one producing retention, because it's the one they can see and build features for.
The emotional and social layers operate in the background. Nobody puts "I feel in control" on a feature request. Nobody writes a support ticket that says "my colleagues perceive me as organized because of your product."
But those layers can be the entire reason people stay.
Strava Thinks It's a Tracking App. It's a Social Network.
Mark Gainey and Michael Horvath founded Strava in 2009. The name is Swedish for "strive." The original idea was to recreate the team mentality Horvath had experienced with his college rowing crew — give runners and cyclists a way to train together, even alone.
On paper, the is obvious: track my workout. Distance, pace, elevation, heart rate, route. Strava does this well. So does Garmin Connect. So does Nike Run Club. So does the Apple Watch. If tracking quality were the whole story, Strava would be one option among many.
It's not one option among many. It has over 135 million athletes and a reported $500 million in annual revenue.
The reason is .
When someone finishes a run on Strava, they don't just get . They get an audience. The activity goes to a feed. Friends give kudos. Comments arrive. Segments turn ordinary roads into leaderboards. Clubs create communities around shared goals.
Strava's own community has a phrase that tells you everything you need to know: "If it's not on Strava, it didn't happen." That's a statement about being seen. The run doesn't feel complete until it's witnessed by people whose opinion matters.
A study of runners in Dutch Strava clubs found that receiving kudos directly increased how much and how often people trained. The social reinforcement wasn't a nice bonus on top of the tracking. It was the mechanism producing the behavior. If a product team looked at Strava's retention and attributed it to tracking quality, they'd be pointing the roadmap at the wrong layer.
This Mistake Is Expensive
When you misread which layer is producing fit, every decision inherits the error.
If Strava believed the was doing the work, they'd invest in better analytics, fancier route planning, deeper heart rate monitor integration. All fine. None of it is why a casual runner opens the app after a Tuesday evening jog.
That runner opens Strava because their friends will see the effort. Because the kudos will come. Because skipping the upload means the run is invisible — and invisible effort feels like it didn't count.
The same misread happens in B2B constantly. A project management tool's team believes "track tasks and deadlines" is producing retention. But maybe the actual fit is coming from : "I feel in control of a chaotic situation." Or : "My team can see I'm on top of things."
If the is "feel in control" and you ship features that add complexity — more views, more options, more configuration — you're undermining the layer that's doing the work. More capable. Less calm. More powerful. Less safe.
The roadmap improves while degrading the emotional one. And nobody notices until retention softens and nobody can explain why.
The Other Mistake: Averaging Across Different Jobs
There's a second version of this problem. It's not about layers. It's about segments.
Different groups of users can be hiring your product for genuinely different jobs. Your aggregate metrics blend them into one signal, and you build for an averaged user who doesn't exist.
Strava has this too. A competitive cyclist chasing KOM titles on weekend segments is doing a fundamentally different job than a person who walks three times a week and posts it so their friends know they're staying active. The cyclist wants competitive validation. The walker wants social accountability.
Both show up as "active users." Both contribute to retention. But they need completely different things from the product.
If you don't see the split, your roadmap tries to serve both and fully serves neither. Your marketing speaks to one segment. Your product optimizes for another. Retention looks healthy in aggregate while one group is slowly drifting.
How to See What's Actually Producing Fit
The diagnostic isn't complicated. It just requires talking to people instead of staring at dashboards.
Ask about the last time they almost stopped. Not why they stay — that produces rationalized answers about features. What almost made them leave? If someone almost quit Strava because their friends stopped using it — not because the GPS was inaccurate — is doing the work.
Ask what they'd miss most if the product disappeared. Not which features. What would get harder in their life? "I'd miss the route tracking" is functional. "I'd miss knowing my friends saw that I ran this morning" is social. "I'd miss feeling like I have my act together" is emotional. Whichever answer produces the strongest reaction is where fit lives.
Segment retention by job, not persona. Stop grouping users by role or company size. Group them by what they're hiring the product to do. Then look at retention by group. One job almost always has significantly stronger retention. It may not be the one you're building for.
Watch what people do right after the core action. After a Strava user finishes a run, do they study the or go straight to the feed? After someone finishes a report in your product, do they download it or share it?
The behavior immediately after the is complete reveals which other layer matters. If people go straight to the social surface, the is doing the retention work.
The assumption that you know which job is producing fit is one of the most expensive assumptions in product work. It shapes the roadmap, the marketing, the onboarding, the pricing.
And it's often wrong because is visible and measurable, while the emotional and social layers work in the background — producing retention that the team attributes to the wrong cause. If you want to know where your fit actually lives, stop asking what features people use.
Ask what would get worse in their life if the product disappeared.