Actually, it is a little more complicated than this.
First, startups do need to find out what is that "one thing". So many startup end up building more features (use cases) since they are searching for "the thing".
That is ok - but the problem is that many startups are not removing features (use cases) even after their metrics show that this new feature is not "the thing".
I heard arguments like this:
It is wrong to release a user feature and then simply remove it when your testing shows it isn't improving any metrics. Users will feel they are being cheated, even though they aren't spending a single penny for that feature.
My answer to that is: "How much money did you say they paid for this?"
First, startups do need to find out what is that "one thing". So many startup end up building more features (use cases) since they are searching for "the thing". That is ok - but the problem is that many startups are not removing features (use cases) even after their metrics show that this new feature is not "the thing".
I heard arguments like this:
It is wrong to release a user feature and then simply remove it when your testing shows it isn't improving any metrics. Users will feel they are being cheated, even though they aren't spending a single penny for that feature.
My answer to that is: "How much money did you say they paid for this?"