|
I'd like to try this as an experiment to see if we can do some "knowledge management" here on the forums. Some background: I consider it the "fault" of past officers for not having continued to update our Event Chair guide with all of the things we learn about how to make events great. Once in a while an event has some glitches and we re-learn some things all over again.
Since this is MY thread, here are the rules:
POSTING RULES
- Make suggestions for additions to the event chair guide or suggestions for MINOR changes/new things.
- Do not suggest wholesale changes to the way things are run. Start a new post.
- Be specific about how to implement
- Point out good practices that are inconsistently performed.
- If your suggestion would require EXTRA work from the officers or event chairs, make REALLY good case for it
- Think through your recommendations.
- DON'T post your personal pet peeve unless it follows the above
- Feel free to offer modifications to prior posts. I plan to copy the wording from these posts verbatim into the EC guide. - Write your suggestions as you would like to see it in final form.
CATEGORIZATION - Try to preface your suggestions with one of the following implementation types (or make up a new one). Documentation can mean a label, sign, placard, whatever. - Event Chair Guide - GM Responsibility / Checklist - VP Responsibility - At-Event/Bus Documentation - Registration Documentation - T&S Documentation - Website Documentation - Novice Coordinator Responsibility - Worker Coordinator Responsibility - Tech Process - Recommendation for the VPs
MODERATION PROCESS
- I'll be using a "Two out of three" rule. If anyone has an objection to any recommendation, post a well-thought out retort.
- If there is an objection, I will be the 3rd vote. If I agree with the suggestion, it stays and the objection is deleted. If I also disagree, I will delete both.
- If there are several responses about a topic I will split it into a separate thread. Bring the final recommendation back here when there is consensus or a VP decision please!
- I will remove ANY recommendations if the officers tell me to
- I may edit any posts in this thread for clarity and tone.
- I will NOT stand complaining, fighting, bad attitudes, contentious topics, or discussions about things.
- If something isn't a fairly obvious lesson learned or insightful suggestion, I will delete it.
- If you have a gripe about what I'm doing, PM me privately.
Something to keep in mind that if you'd like to see someone do something at a specific time (like turing the volume up or down), there needs to be something implemented. Where should this recommendation be written down? Should it go into an event chair guide? Should there be a sign or label? Can YOU implement the solution?
No one in this club is good at "just remembering to do it". There is too much to remember and too much turnover for a lesson to just stick without documentation.
I'm all for opportunities for improvement. But I'm fishing here for the fairly simple, almost-slam-dunk, "Oh Yeah, Why Didn't I Think Of That", we-should-do-that-every-event, kind of suggestions.
If this works, I'll take the results and see about how to best capture them for future reference. Please don't be afraid to post -- if it turns out to be a dumb idea, just let me know and I'll delete it.[/b]
_________________ Mike Whitney whit32@gmail.com, 919-454-5445 V10, V8, V8t, I6, I6, V6, F4t, I4, I4, I4, I4, I2, 1, 1
Last edited by MikeWhitney on Tue Jun 14, 2005 11:55 pm, edited 13 times in total.
|