|
|
|
|
|
by shoo
1552 days ago
|
|
I guess part of it is really hashing out how decision making in your team works, and getting everyone on board and used to that. For the category of decisions it is acceptable for the team to have authority over: one way this could work is to have people present candidate ideas, put issues to vote, then if the team cannot elect a winner, someone in a leadership position (you?) gets to cast the deciding vote. there are obviously some categories of decisions that the engineering team should not have the authority to decide, e.g. ones where they might have conflicts of interest. e.g. maybe all the developers in the team want to rewrite the product in $HYPED_TECHNOLOGY to be able to put the experience on their resume and then trade it for better jobs, but risk ruining the product and the business (where people might be making the decision with their personal-career hat on, rather than their whats-my-best-professional-recommendation-for-the-company hat on). |
|