I recently threw out the "do the MVP" mindset. To me, MVP means "Do part A to a good enough level of perfection where customers will buy it, then release and g

I recently threw out the "do the MVP" mindset. To me, MVP means "Do part A to a good enough level of perfection where customers will buy it, then release and get customers, support them while then working on part B as a value-add.." - often, in my mind, all parts, ABC add up to the whole package value. I don't want to break it apart. I'm actually trying to do more planning and outlining first, and it has worked reasonably well for me. Start with an outline of the different systems and how they connect, then outline one of those systems, the inputs and outputs to it. Then break down further into how does it get the input, where does it put the output, etc. It has been remarkable in that I can actually feel joy for what I'm making again. I have also tried to start a blog with doing this type of "open design" - but blog writing requires its own planning and refining, which is an extra workload that I didn't intend to put on myself..