Wow - that was painful to read because I can relate so much. Thanks for sharing. Another aspect of such dysfunction is the diffusion of responsibility that comes with it. The stubborn people who pushed for a particular solution rarely suffer ill consequence because the decision was technically made as a group.
I think a functional engineering decision process is more akin to a veto process. Someone, say Olivia in your example, would be tasked with selecting the language for the job and submitting the technical rationale for it and the relevant authorities (e.g. CTO or product owner) would sign off on the decision. They will normally have the power to approve or reject but not to impose certain solution. In a traditional hardware engineering, this is how it's done, where an engineer submits a design and it needs to be approved by relevant subject matter experts in various domains, such as material, thermal, structure, safety etc.
I think a functional engineering decision process is more akin to a veto process. Someone, say Olivia in your example, would be tasked with selecting the language for the job and submitting the technical rationale for it and the relevant authorities (e.g. CTO or product owner) would sign off on the decision. They will normally have the power to approve or reject but not to impose certain solution. In a traditional hardware engineering, this is how it's done, where an engineer submits a design and it needs to be approved by relevant subject matter experts in various domains, such as material, thermal, structure, safety etc.