# How do you decide which features are actually worth building? — retained record

> Retained reddit record from reddit:EntrepreneurRideAlong.

Canonical: https://highsignal.app/data/records/43a2217ece006e08

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:EntrepreneurRideAlong)  published 2026-10-30 12:41 ingested 2026-10-31 02:37

[original source ↗](https://www.reddit.com/r/EntrepreneurRideAlong/comments/1xjeb3t/how_do_you_decide_which_features_are_actually/)

## retained text



```
*Something* I've been thinking about lately is how easy it is to keep adding features to a product.

You get feedback, look at competitors, come up with new ideas, and suddenly your roadmap is packed.

But more features don't necessarily mean a better product. Sometimes you're adding complexity without actually solving a problem customers care about.

Curious how other founders approach this. Do you prioritize what users ask for, what could help attract more customers, or what fits your long-term vision?

Have you ever built a feature that turned out to be completely unnecessary?
```



document fetched 2026-10-31 00:25 · canonical https://reddit.com/r/EntrepreneurRideAlong/comments/1xjeb3t/how_do_you_decide_which_features_are_actually
