How do you know when a feature is failing because it's trying to do too much ?

by•

We built an all-in-one search feature that checked docs, users, and settings all at once. It was super powerful on paper but because it took over two seconds to run, users were quietly avoiding it.



We decided to cut it down so it only searches documents in milliseconds, while moving the full search behind a second click. Search usage shot up by three times because people prefer speed and clear results over a complex tool.



Have you noticed any features in your own app that users avoid simply because they got too slow or complicated?

4 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.