Read my other comment, as your story is a far-too-often-used extreme used by the other extreme party to justify bizarre situations. For every one of those anecdotes is another anecdote of a team of seniors/architects pissing away half the development time only to come with an inadequate solution at the end of it. Guess what, it leads to the same 3-6 months of 'unfucking' with said feature now having to be juggled in prod, where it could have taken half a day of user-testing in a safe environment. When both extremes lead to the same problem, the anecdotes of 'how going fast destroyed my mental sanity' are not an excuse to endlessly bash the other extreme.

The key problem is always the same. The business wants to move as fast as possible, and developers are extremely concentrated in either the overly defensive "let us discuss ad nauseam" camp or the willing/passive "let's develop something and deliver it" camp. I don't agree with either, but frankly, I've had far more trouble convincing the former of their problem (analysis paralysis and wasting time) than the latter of theirs, and the former group is extremely convinced they have the high ground over the latter.

>I’ve dealt with this half a dozen times (maybe more) in my career.

And I've dealt with 'seniors' willingly sitting in meetings not achieving anything and pushing silly refactors more than half a dozen times only to run into performance issues, bugs and terrible deployments. User complaints don't lie, the grass ain't greener on the other side.