I wholeheartedly agree with this principle since my days at Amazon.
I also found that if you need to follow the principle too many times it's a good indicator the team/company goals/vision/ and yours don't align and - if circumstance permits doing so - leaving is better than keep up the fighting forever (which is extremely exhausting, from personal experience).
Don't know how it works at Amazon, but we have a similar rule to avoid teams getting paralyzed on design decisions. I've also worked at companies that didn't do this, and spent more time in design meetings than it would have taken to code a simple prototype.
Following this principle too many times isn't necessarily an indication that the team doesn't align with you, it can also be a sign your communication skills are lacking, and you need to get better in how you convey your ideas (unfortunately talking from my own experience).
A good tie-breaker is usually picking the simpler idea, to avoid perfectionism or over-engineering that engineers sometimes fall into. It seems especially common with people straight out of uni, and lessens with experience.
I also found that if you need to follow the principle too many times it's a good indicator the team/company goals/vision/ and yours don't align and - if circumstance permits doing so - leaving is better than keep up the fighting forever (which is extremely exhausting, from personal experience).