How do you make decisions in your teams/solo?

Question

I think decision making is one of the most important things we do as software engineers (not to mention other disciplines).How you manage decisions in your teams? Do you have heavy process, lightweight, none? What works, what _doesn't_ and in what situations?My aim here is to flush out ideas and generate some discussion. Hopefully to figure out some better ways of managing this critical piece of our work.Thanks for your time!

Isammoc · Accepted Answer

Really, for my job, it depends on the subject. Next feature: the CTO (small structure, so he has the PO cap). Small library dependency to add in our project, the dev that need it. Big refactoring: the one that had the idea validated by the whole team (to be sure it's the path we want to take). Process/documentation: a team specific meeting. Usually, small nits to change to sustain all team members. For current next big feature, it's the fourth proposal and we don't agree yet. So was have more proposals to come.