On Wed, 14 May 2014, Derek Balling wrote:
On May 14, 2014, at 7:08 PM, Evan Pettrey <[email protected]> wrote:
There's one other that I forgot to add that needs to be mentioned:
Be Flexible - I can't tell you how many great ideas I've seen killed by our
rigorous adherence to bylaws that none of us created and procedure written by
somebody none of us has ever met. Bylaws and procedure can be great and exist
for a reason but we need to realize that often times we're sucking the soul out
of projects that have a promising future simply because the idea wasn't
presented correctly, the bylaws don't explicitly state something is allowable,
etc.
We need to go back to operating like a startup. We're simply not a large enough
organization to be held back by things like this.
As a 501(c)(3), you don't have the luxury of acting like a startup. You have to have
"religious adherence to bylaws". If you don't like them, I direct you to
article 11 of the bylaws for how to amend them.
Actions that are in violation of the bylaws can be legally actionable and
nobody wants that.
Fine, if the bylaws say something can't be done, we don't do that. If the bylaws
define what a "Chapter" is and what the requirements are to be one, we need to
follow them.
But assume that if the bylaws are silent on a subject, that it's allowed, don't
go looking for "what in the bylaws allow this", the bylaws allow education of
both the members and the public, that covers a LOT of ground and can be used to
justify just about anything that's not explicitly prohibited.
David Lang
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
