4 ms·

The professor of non-profit organizations class in law school cautioned us to avoid Robert's Rules warning us that it would lead to discord and overbearing majo

The professor of non-profit organizations class in law school cautioned us to avoid Robert's Rules warning us that it would lead to discord and overbearing majority rule, preferring Thomas Jefferson's Manual [0] for peaceable and practical reasons. Having used Robert's before attending law school and seeing how its use tore up a club I tend to agree. [0] https://en.wikipedia.org/wiki/Jefferson%27s_Manual https://en.wikipedia.org/wiki/Jefferson%27s_Manual

WorldMaker 4y ago
Relatedly, it's incredible how thick of a tome "modern" editions of Robert's Rules have become to elucidate every single edge case and complex trivia of nearly every state of the described finite state machine. As a programmer, I laud that kind of detail in the specifications of something I need to build, but meetings aren't run on computers, they run on a group of people, and if the finite state machine can't be easily visualized and shared by everyone in the meeting then it isn't doing its job properly. The editions in the public domain are so much smaller and faster to read by comparison, though still suffer most of the problems the article points out. It gets the raw gist across without getting lost in trivia. (The 1915 edition is often the most commonly recommended. [1]) There are "bugs" fixed in later editions, but the answer is more often YAGNI (you aren't going to need it) and if you do, you are a) in deep, possibly with too many "rules lawyers" trying to D&D min/max your meetings, or b) the edition is public domain so DIY hack your own bug fix. There is a certain satisfaction to only running meetings on public domain editions of Robert's Rules, including that it is free as in beer and speech to do so, and it can be worth throwing out some of the bathwater from "modern" editions (including in spite of if you think there's a baby in there in some of the "bug fixes"). I knew someone whose favorite "edition" was the Robert's Rules Simplified of 1937 that is also mentioned in the first paragraph of the article. I think it will be a big day for meeting governance once that is finally in the public domain as well. (I think procedures manuals such as Robert's Rules are a strong case against how absurdly long copyright has become. Finite state machines for controlled meeting operation should be easy to hack and share. Everyone has meetings in their lives. Good shared FSMs make meetings run smoother. Access to the "source code" of those FSMs shouldn't be limited to a cabal of people buying expensive books and/or planning to use rules trivia to bludgeon meetings into shapes they enjoy or think they control.) [1] One PDF source: https://robertsrules.org/robertsrules.pdf https://robertsrules.org/robertsrules.pdf

WorldMaker 4y ago

Relatedly, it's incredible how thick of a tome "modern" editions of Robert's Rules have become to elucidate every single edge case and complex trivia of nearly every state of the described finite state machine. As a programmer, I laud that kind of detail in the specifications of something I need to build, but meetings aren't run on computers, they run on a group of people, and if the finite state machine can't be easily visualized and shared by everyone in the meeting then it isn't doing its job properly. The editions in the public domain are so much smaller and faster to read by comparison, though still suffer most of the problems the article points out. It gets the raw gist across without getting lost in trivia. (The 1915 edition is often the most commonly recommended. [1]) There are "bugs" fixed in later editions, but the answer is more often YAGNI (you aren't going to need it) and if you do, you are a) in deep, possibly with too many "rules lawyers" trying to D&D min/max your meetings, or b) the edition is public domain so DIY hack your own bug fix. There is a certain satisfaction to only running meetings on public domain editions of Robert's Rules, including that it is free as in beer and speech to do so, and it can be worth throwing out some of the bathwater from "modern" editions (including in spite of if you think there's a baby in there in some of the "bug fixes"). I knew someone whose favorite "edition" was the Robert's Rules Simplified of 1937 that is also mentioned in the first paragraph of the article. I think it will be a big day for meeting governance once that is finally in the public domain as well. (I think procedures manuals such as Robert's Rules are a strong case against how absurdly long copyright has become. Finite state machines for controlled meeting operation should be easy to hack and share. Everyone has meetings in their lives. Good shared FSMs make meetings run smoother. Access to the "source code" of those FSMs shouldn't be limited to a cabal of people buying expensive books and/or planning to use rules trivia to bludgeon meetings into shapes they enjoy or think they control.) [1] One PDF source: https://robertsrules.org/robertsrules.pdf https://robertsrules.org/robertsrules.pdf