Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

MVP vs MVT is a false dichotomy. It is made up by the author to sound smart and be convincing. From the article, describing what it calls MVT:

“Build an initial product to bring all of your insights together and test them with your target customer.”

Yeah, that initial product is the MVP.



Maybe we read different articles, but "Build an initial product" is what he said to do _after_ the hypothesis testing.


I think this is often where people are confused by MVP. Your minimum viable product isn't (necessarily) your initial product. It's the product you build to test a hypothesis.

This is why the article read fairly false to me, not that there wasn't the odd nugget of value, but coming up with a new MVT, is just adding to the confusion.


I quoted directly from the article. MVP is built after the hypothesis testing, but it’s still a test, a test of the independent hypotheses combined into a material product.


I think the point is that the P is not necessary if the T's fail. So, you're creating a stop loss for your time/money/blood/sweat/tears


> I quoted directly from the article.

You did, but your quote comes directly after he said:

"Once you’ve finally tested enough hypotheses to have more confidence about your product viability, then go to the next steps:"

The MVP is the next step and it distinctly different from what he calls an MTP.

An MTP is not a useable product, it doesn't have a login, stack or maybe any code at all.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: