I've read your post and love your writing and your take on it.

As far as I see MVP, it is a fine methodical tool that is useful, but using it wrong or misinterpreting it is what gives it a bad name.

Two things I'd love to give back:

1. Things can be as old as Jerusalem. As long as they work, age doesn't matter. The tendency to "find something new, since it's been around 10 years" is not a motivator. Periodic reviewing, if your method and/or tool is still the best for the job, IS. It's about having a process, not an expiration date.

2. The word "build" isn't inherently connected to MVP. Many people think it is.

You can configure a facade website, and do the processes that your product automates manually in order to run your MVP. It's about providing enough value to others, so you're getting paid (thus becoming viable) as the best evidence that your product/service will prevail.

No-code/Lo-code is a blessing for the MVP part. But having a landing page, getting people to enter their credit card info to hook up with your product/service, and doing all the stuff manually behind the scenes can be considered an MVP. It's often not scalable, but viable and proof for the entrepreneur to keep investing on improving/growing it.

Anyway, my mantra: Create. Value. First.