You have to prevent only catastrophic decisions.
If you are working on CRUD web platform most decisions will not be catastrophic. Maybe inconvenient, maybe eat more budget but probably company will not go under because of some technical decision.
Much worse is a series of mediocre decisions that you can live with, but compound over time to slow you down. You never really learn what's going wrong, your team doesn't improve. Give me the former, painful though it may be in the moment.
As a practical matter, "be humble and accept the input of others" quickly shades over into "be lazy and allow stupid people to dominate the meeting, because letting them dominate the meeting is easier than fighting them." I agree it is easier, but it is unethical to accept money while allowing bad decisions to be made.
In my experience this is very rarely the actual case. Usually there are multiple viewpoints, multiple solutions, and while some may be slightly better than others, the effort of having the debate is much more time and resource-intensive than just accepting one of the solutions.
Man, have you ever seen bad code?
For an example, suppose someone comes up with the idea of making dozens of mini-modules with poorly defined interfaces, each one having no clue about what's going on globally, that should somehow contribute to solving a simple problem. Each interacts with each other through some sort of worm hole where you have only a vague idea what's on the other side.
Another possibility is to look at the requirements as a whole and write a single module that solves the problem in a straightforward way. Now, should one accept the first idea and write 3 or 4 times the amount of hard to code, the code being unmaintainable because the interactions between the many moving parts are very hard to understand? Just because everybody thinks that's how it should be done?
This has nothing to do with having a debate in a meeting, indeed, often the best strategy is to avoid the meeting altogether.
Like picking tabs vs spaces, I am not going to fight about it, it is not a decision that will make any difference for product.
When it comes to getting coworkers or other teams on board with a new workflow or tool, it's really completely up to powers of persuasion, providing good examples, documenting, and letting people move at their own pace. It can be frustrating to work through, but it's probably for the best, in the sense that it probably is genuinely the best tool or workflow that will win out over time, instead of the favorite of some senior person that doesn't know all the details.