Interesting to see the other POV. I experienced this from the opposite side. A teammate once told me he is frustrated with being asked to work on an MVP, that

Interesting to see the other POV. I experienced this from the opposite side. A teammate once told me he is frustrated with being asked to work on an MVP, that is minimum cost, minimum polish, minimally functioning. He said he wanted to work on MLP, so I said he can call it MLP if he wants, but what we must build does not change: prove the concept minimally such that we can verify whether the problem we seek to solve is a real problem in the first place, then we can add as much polish as needed once we know it's a good problem to solve. If we think customers are experiencing some problem that, in order to solve minimally, we need to give them polish, then the polish is a part of the MVP/MLP. Otherwise, it is not. It doesn't matter what we call it. What matters is what we must do. He thought that my attitude taking the distinction between MLP and MVP lightly was a sign that I do not care about the best interest of our customers, and left the company.