Is it better to fix a feature or change how you explain it?

by•

We spent three weeks building an advanced export feature because users kept asking for it in support tickets. Once we shipped it, adoption was almost zero. When we reached out we realizes people didn't actually want a new feature they just didn't understand how to use existing tools to get the same output.

How do you figure out whether a product issue is a missing feature or just a clarity problem?

2 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.