I've seen that exact argument made and put into practice, though. i.e. the unironically promoted approach of "add a button for a feature you think users will want, and then show an error message when they click it after collecting metrics"
Some people have a really delusional definition of "viable"
Comments
It's pretty obvious that if you don't consider what the customer wants your product will miss the mark.
The argument an MVP excludes actually meeting customer's requirements is pretty misguided.
I've seen that exact argument made and put into practice, though. i.e. the unironically promoted approach of "add a button for a feature you think users will want, and then show an error message when they click it after collecting metrics"
Some people have a really delusional definition of "viable"