I have started to encounter the same two problems again and again when building products, and both are related to the MVP mindset:
A product/feature is built as the smallest possible thing that might add value to a user, with no plan, resource or expectation to follow-on that work going forward, regardless of whether the feature is working or not; there is always something else to do.
Because the smallest possible thing is being built, there is very little consideration of how it will interact with the rest of the org, what the cost of ongoing support will be, or for what use cases it will fall down and force us to work on it even if we don’t want to.
The MVP mindset is leading to a proliferation of zombie features that won’t be improved yet won’t be killed, which to at least some degree shows a level of disrespect for the people that have to use them. It means that product teams can’t focus because they support more products than they have member of the team. The evolution of SaaS has addressed this at least somewhat - we can pay someone else to work on the things we don’t want to - but for core, user-facing products and features we have a long way to go.
Btw, this makes me think of this from Reforge:
We spend so much time looking at all the channels and all the tactics and all the hooks without understanding that it’s usually just one big thing that tips it, so maybe we should go deeper instead of just going MVP.