We stopped asking users what they wanted. Our product got better.

For the first year of Murror, we ran surveys, interviews, feature request boards -- the whole playbook. We collected thousands of data points about what people said they wanted.

Then we started watching what they actually did.

The gap was enormous. Users asked for more customization options. What they actually needed was fewer choices at the right moments. They asked for social features. What they actually did was journal alone at 2am.

We built what they asked for. Usage was flat. We built what their behavior told us. Retention jumped.

Here's the uncomfortable truth about product building: users are experts on their problems but unreliable narrators of their solutions. They describe what they think they want using the vocabulary of products they've already used. But the breakthrough comes from noticing the thing they do that they'd never think to mention.

At Murror, the feature that drove the most retention was one no user ever requested. We noticed people would re-read their own entries days later -- not to edit, just to reflect. So we built a gentle resurfacing system that brings back past entries at moments that feel right, not on a rigid schedule.

Nobody asked for it. It became the thing people said they couldn't live without.

The lesson we keep re-learning: run your surveys, do your interviews. But treat them as conversation starters, not product roadmaps. The real roadmap is hiding in your behavior data, in the things users do when nobody's watching and no one's asking.

What's a feature in your product that nobody asked for but everyone ended up using?

22 views

Add a comment

Replies

Be the first to comment