In my experience what trade-off is the correct one depends on your ability to iterate and where your risk comes from. Can you ship infrequently, but you know wi

In my experience what trade-off is the correct one depends on your ability to iterate and where your risk comes from. Can you ship infrequently, but you know with high confidence what product/market-fit looks like (extreme example Mars mission)? In that case you want all the planning and verification you can get. Can you ship often, but have little confidence in what your users/customers want and what will grow your business (extreme example social media app)? In this case you probably want to prioritize speed of iteration and rework technical aspects once you know it's what's needed. I've had a very angry product manager because a feature took almost a second to load. I told him that we could make it load much faster but it would be almost a week of work and he should validate the feature with customers before we invest in that. "Of course we need this feature! It's core to the product!". So we spent a week. It worked realty nicely and scaled pretty well. In the next 12 months the feature changed completely twice because customers didn't find it useful. Then it was removed entirely and then we had to bring it back because the sales team liked it for demos. All that iteration was required to find what the market needed, not fit technical reasons, except for the performance work which was entirely wasted because it all got redone after the first user feedback.