For the past 3 months, the primary activity on my team has been to debate and discuss the architecture design of the large system our team will be developing in Q3. It feels like we’re in gridlock and I don’t see a clear path to a decision. How can we move forward productively?
Timebox it! Engineers, especially at a strong company like Google, love to theory craft on their quest for the absolute optimal, scalable approach. The problem is that this discussion can easily go infinite if left unbounded.
Q3 is very soon, so there's only so much more time left before execution needs to start. Set a deadline for the architecture discussion, say 2 weeks from now, whatever you need to hit the final ship deadline in a healthy way. The contract is that wherever the discussion is after 2 weeks, the team will move forward with what it currently thinks is the best option, regardless of its FOMO for some potential other option that's better. If there's still no consensus with this pressure, you can call a vote or delegate the decision to the EM/TL.
The main thing is to make sure that people can't just keep debating without fully accepting the repercussions. If you're an engineer who's going to strike down the current consensus and push the discussion even longer, you need to own the fact that you are pushing back the deadline for the entire team.