News for hackers. Stuff that matters.
Re:Things I was unprepared for as a lead developer by Scarblac on Wednesday September 16, 2015 @02:47AM (#10225033)
The people who aren't convinced can feel that the debate is still open, even while the majority is convinced that a decision was made two months ago.

I'm in the Netherlands, where hierarchy is a bit of a dirty word, and educated employees are all expected to be critical, independent, outspoken thinkers all working towards a common goal. That has many advantages, but the technical discussions about pretty small details can go on forever...

Re:Things I was unprepared for as a lead developer by bkor on Wednesday September 16, 2015 @04:43AM (#10225392)
To me it indicates that you don't have a good facilitator in discussions. IMO one of the nicest things I've ever learned is the "silent thinking" bit. Basically: don't say anything, people write post-its, then people present that. This avoids usual influential people from speaking up early and everyone just focussing on one or two ideas. I've often been surprised what some people come up with.

If above is not enough to get an agreement, let the two people work it out on their own with a limit on how much time they can spend on it (and really limit this time). No need to have an entire team listen in or extend an existing meeting for ages (meetings should be brief).

Aside from that, sometimes you just need to do. So something like "it's not a perfect decision, but what you're saying is known and now it is time to do".

I'm from the Netherlands btw, though 50% of my colleagues are foreign.

Re:Things I was unprepared for as a lead developer by Pyxl101 on Wednesday September 16, 2015 @07:08AM (#10225780)
People not knowing what decisions have been made, and which have yet to be made, is poor communication. The first thing you do after making a decision is communicate it unambiguously.