How to flub (and not flub) group decision-making on technical teams

I like the framing here. I’ve been trying to get participants to declare their stakes more clearly up-front, upside and downside, and keeping that more or less updated as discussions and decision-making proceeds.

Interestingly, this hasn’t just been good for decision-making but has brought some hidden agendas out of the woodwork, where they do less damage and sometimes have led to really better understanding of problems that we’ve got.

Anybody else trying similar things?