If you equate "slow" with "wasting time" you have very clearly missed the point.

"Move fast and break things" works only when the value of, and audience for, your work is highly uncertain. If you have any confidence whatsoever in the value or audience of what you're building, slow is usually better.

Going fast in the wrong direction is only a good use of time and resources when you quickly recognize the mistake and turn around. In my experience, most people who prioritize speed above all else are hellbent on a specific destination and won't change course until it's too late.