This kind of criticism happens to any popular term. And usually terms become popular because they <i>work</i>. Thinking "minimum viable product" worked -- it turned on the light bulb for many people (like myself) who polish instead of test, or seek perfection instead of iteration.<p>I feel like Reinhardt is complaining about the term "minimum VIABLE product" when most people emphasize it "MINIMUM viable product".<p>In that emphasis, the two mean almost the same thing. However, I see another difference:<p>- "viable" makes you think about what users want. Sure, you can get carried away, but that's why "<i>minimum</i> is there to reign you in.<p>- "testable" could mean anything -- you can <i>test</i> anything, in any direction -- it doesn't make you think about what users want.<p>This is problematic.<p>Viable is a good word. It points you in the right direction. "Testable" helps to limit you, but "Minimum" is already there to do it.<p>I say stick with MVP, but if you, or team, start getting carried away, just remember - Minimum, minimum, minimum!