The following items were mentioned in the ACM 2.14 Retro regarding UI Changes:

1. Increase the UI dev team to solve UI issues before code freeze/GA

2. We have to find a way to communicate about UI code changes before they are merged (or while reviewing MRs that changes it) to avoid CI failures and adjusting  Automation code in time

3. Wide impacting changes like underlying UI codes changes (and others) should be tested better and earlier. Maybe one team take the lead and perform initial test instead of everyone tries to ask the same questions