I wonder how you would see the MVP fitting into this? I have been in situations where you “have to make something work before you can make it great” (spoken by some engineer in the room). This is very often a convincing argument for others (especially senior leadership) in the room. You build the simplest thing possible to validate whether or not the product is resonating with users (and worth taking ‘all the way’). In practice, what I’ve seen happen is that we never come back to making the feature great, because it would require starting over. The Sunk Cost Fallacy kind of applies (I suppose), but it is a different thing when you’re talking about this in the context of a feature you’ve already launched (as opposed to one you are about to launch). Thoughts anyone?