> I don't think consensus-building is necessarily bad on it's own.
Making decisions based on consensus is just often not the right choice in this context. If used for the wrong type of decision, it will lead to a "design by committee" type of process and result, driving a lot of people mad along the way.
A better way to make decisions in a software project is to consult with stakeholders (if necessary), identify the appropriate decision maker based on competence and then let that person make a decision.
> A better way to make decisions in a software project is to consult with stakeholders (if necessary), identify the appropriate decision maker based on
competence and then let that person make a decision.
Holy shit. This is one of the most profound things I've read about management in a long, long time.
Making decisions based on consensus is just often not the right choice in this context. If used for the wrong type of decision, it will lead to a "design by committee" type of process and result, driving a lot of people mad along the way.
A better way to make decisions in a software project is to consult with stakeholders (if necessary), identify the appropriate decision maker based on competence and then let that person make a decision.