2
3 Comments

I accidentally stopped asking users what features they wanted

When I started building Dayleaf, I thought user research meant asking:

"What features are missing?"

But the most useful feedback I've received wasn't feature requests at all.

It was emotional language.

People said things like:

"My to-do list became a record of failure."
"The app feels emotionally heavy."
"I avoid opening it when I'm already behind."
"It's basically a guilt dashboard."

None of those comments told me what to build.

But they completely changed how I think about the problem.

Instead of asking:
"How do I help people manage more tasks?"

I started asking:
"How do I help people feel comfortable returning after a messy week?"

That shift has influenced Dayleaf far more than any feature request.

Curious if other founders have had a similar experience where customer language taught you more than customer feature requests.

on June 17, 2026
  1. 1

    This is a strong shift.

    Feature requests usually describe the surface. Emotional language tends to describe the actual constraint.

    What I find interesting is whether you optimize directly for the emotion people express, or treat it as a signal and still validate it against actual behavior.

    1. 1

      That's something I've been thinking about a lot.

      I don't think the emotional language alone is enough to build from, but it's often what points me toward the behavior worth investigating.

      For example, when people say things like "I avoid opening the app" or "it feels emotionally heavy," the interesting part isn't the phrase itself—it's the behavior behind it. Why are they avoiding it? What changed between the first week and the tenth week?

      The emotional language helps identify the problem. The behavior helps validate whether it's real and worth designing around.

      1. 1

        I think that's where it gets interesting.

        Sometimes the behavior confirms the emotion.

        Sometimes it points somewhere completely different.

        The tricky part is knowing which lesson deserves to drive the product.

        Hard to do justice to that in a comment, but happy to send over the fuller thought if you're interested.

  2. 1

    This comment was deleted 2 months ago