This can't be an "all or nothing" proposition in either case. There are technical decisions that are absolutely worth fighting for, that would be pretty devast

This can't be an "all or nothing" proposition in either case. There are technical decisions that are absolutely worth fighting for, that would be pretty devastating for the product or the company, and you're right, in those cases, you might feel like you have to fight against the preconceived mood -- but even then, keeping account for feelings, because these are the people who are going to need to build your "vision". Compassion without compromise is a real thing. In other cases, you need to keep in mind personal biases, and also keep in mind the pyrrhic victories are a very real thing and a very real danger, even potentially catastrophic in certain environments. Hiring an engineer, when you figure in staff costs in interviewing and possible recruiter fees, can cost 5 figures easily. Lost opportunity costs in training and losing corporate knowledge can push those figures even higher. Always have a good understanding of what you're doing, what the consequences might be, and whether your issues are worth those consequences.