"Systems fail where coordination is assumed rather than designed.
Read the quote as instruction, not as comfort. In a dependency upgrade with unknown blast radius, the word coordination is where the cost hides. If you miss it, you will pay it later.
In a dependency upgrade with unknown blast radius, people argue about preferences when the real issue is structure. You see it in a boundary shift that moves work onto a team that did not agree, where the system teaches everyone the wrong behavior. If you do not name the cost now, it will return later as rework, pager load, or a standard nobody can enforce.
Herbert A. Simon is a reminder to keep it concrete. Name the cost you are accepting so you can defend it later. Make the decision legible to the next person who inherits it.