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.
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.