Quote:
Originally Posted by Jimmy Nichols
Great Handbook! Lots of information.
My only advise, coming from someone who has been responsible for maintaining and forming committees for annual review and revision of our team handbook, is to break it apart. There seems to be more information in it than what you would need in a handbook. I could see you breaking it apart into seperate handbooks for parents, Enginneering, etc. I think it would make it more managable for maintaining, as well as distributing and actually getting folks to read what you want them to read.
|
Thanks, I think that is a useful idea. We've just started on another reference document containing the roles and responsibilities of our team "admins" (president and vice presidents) and NEM's, and since that will contain a lot of detail that not everyone needs to see, we're doing it as a separate handbook.
One thing I've realized, being a former president of our team, and seeing my brother be president now, is that so much of the operations, deadlines, and responsibilities are in our collective "brain trust." Therefore the importance of clearly documenting each and every thing to empower future leaders to be even more successful cannot be overstated.