Fantastic analysis, Bandan. I particularly liked the conclusion that the common knowledge to "release as soon as possible" might not always be the right approach.
At the same time, it's worth considering Dan Olsen's advice from The Lean Product Playbook. You shouldn't build an MVP (both prototype and the first version of the product) without having a great UX for your selected feature set from the start.
When you say "At a highly scaled company, the first iteration of the product should be a minimum lovable product and not a MVP" Why should this be different for a startup? Even they are competing against existing products that have raised the bar w.r.t customer experiences. When does the MVP truly help in that case?
Fantastic analysis, Bandan. I particularly liked the conclusion that the common knowledge to "release as soon as possible" might not always be the right approach.
At the same time, it's worth considering Dan Olsen's advice from The Lean Product Playbook. You shouldn't build an MVP (both prototype and the first version of the product) without having a great UX for your selected feature set from the start.
When you say "At a highly scaled company, the first iteration of the product should be a minimum lovable product and not a MVP" Why should this be different for a startup? Even they are competing against existing products that have raised the bar w.r.t customer experiences. When does the MVP truly help in that case?
Great post! Critical to understand the distribution of MVPs in large-scale organisations.