We almost shipped a feature nobody actually needed.

by

This week we were ready to build a feature that seemed like an obvious win.

Before starting, we reached out to a few users and asked a simple question:

"What slows you down the most?"

Not one person mentioned the feature we were about to build.

That conversation probably saved us a week of work.

It was a good reminder that what feels important inside the team isn't always what matters to users.

How do you decide what to build next? User interviews, analytics, intuition, or something else?

16 views

Add a comment

Replies

Be the first to comment