4 ms·
I don't wholly disagree but there are probably far simpler documents one could put together (and I imagine exist) with various voting/notification/debate arrang
by ghaff 4y ago
I don't wholly disagree but there are probably far simpler documents one could put together (and I imagine exist) with various voting/notification/debate arrangements most suitable for the given situation. Whenever I've been involved with creating bylaws for an organization, we've tried to be fairly specific about such things. (One thing I definitely learned was that being very informal about most things was fine--until it wasn't.) In the bylaws, we basically invoked Robert's Rules in the vein of--if we didn't think of some situation, use this.
- cf 4y agoI know there is IWW's "Rusty's rules of order" that tries to simplify these procedures and remove some of the archaic bits. https://libcom.org/article/how-hold-good-meeting-rustys-rules-order https://libcom.org/article/how-hold-good-meeting-rustys-rule...
- pfarrell 4y agoAgree. I’ll admit that, like Agile, I use portions of it as I see fit, not a strict adherence. The core thing I’m thinking of is respect for opposing viewpoints, techniques for debating with people who disagree, and coming to decisions. Debate teams do this, but I think there’s some value in everyone getting a taste of it.
- ghaff 4y agoThere's probably at least two different aspects. One is how to discuss/debate opposing viewpoints so people at least feel they've had the opportunity to express their opinion and then there's how a decision is actually made. The specifics of which are very important on a board or other structure that is some variant of majority rule.