[majormajor]

It also created a cargo cult though.

"What can we get rid of for MVP" as a design strategy vs a way to iterate fast, for instance. Cutting things isn't a way to product cohesion, especially if you never go back to do the full-featured version.

Sometimes I wonder how many features or products flopped because the MVP dropped the things that would've actually taken off, and the business "smartly" pivoted away.

There's still a limit to how many new features you could shove in front of your users per month. But what if they were all much more baked out of the gate?

(See also: "data driven" product management as an excuse to not have your own vision for the product. If three competitors build a lot more in the span of six months, but have to depend more on their own skills and instincts vs A/Bing every little detail, maybe more of them will ship more bold and interesting new things.)

[byzantinegene]

the opposite can also be true, feature bloat can destroy products by making it unclear for users what they should expect.