@rainhaDec 04, 2014Dec 04, 2014 at 03:21 PM
#1
So, regarding what was discussed in the last officer meeting. I wonder why we never did anything like this as it strikes me as important and constructive.
Here are my guidelines for it, feel free to disagree, but we do need to settle this so we can start doing it.
(I took this from guidelines that I found on google and added some of my own and adapted some to a gaming situation)
- This meetings are to occur bi-weekly on a fixed schedule.
- This meetings must be documented in the most precise way. Possibly recorded. The Senior Officer doesn't necessarily need to share the recording with anyone but the Guild Master unless requested by the other person. This should be done only for security purposes. Heck you don't even need to show the guild master, but you have to have a recording of the meeting. Honest. I read about this.
- This meeting should be done with the entire department, in the way the Senior Officer in charge best deems it, however, both Senior Officer and Officer should provide feedback, both on themselves and on the other. Keep the feedback to the point and constructive. Feedback meetings have the purpose of growth and development.
- After the Senior Officer has spoken to their department, they are to warn the Guild Master, who then will schedule a feedback meeting with said Senior Officer. Where feedback on their officers and on the Guild Master will be given, as well as on the Senior Officer in question.
- The meetings with the Guild Master will be recorded by him/her and saved for security purposes.
- The meeting is developmental – not punitive. Everyone has strengths and
weaknesses.
Those are like a draft for guidelines, please let's discuss this as I was hoping we could start doing these meetings by the start of next week :D
Resources: Website 1 | Website 2 | Website 3
Here are my guidelines for it, feel free to disagree, but we do need to settle this so we can start doing it.
(I took this from guidelines that I found on google and added some of my own and adapted some to a gaming situation)
- This meetings are to occur bi-weekly on a fixed schedule.
- This meetings must be documented in the most precise way. Possibly recorded. The Senior Officer doesn't necessarily need to share the recording with anyone but the Guild Master unless requested by the other person. This should be done only for security purposes. Heck you don't even need to show the guild master, but you have to have a recording of the meeting. Honest. I read about this.
- This meeting should be done with the entire department, in the way the Senior Officer in charge best deems it, however, both Senior Officer and Officer should provide feedback, both on themselves and on the other. Keep the feedback to the point and constructive. Feedback meetings have the purpose of growth and development.
- After the Senior Officer has spoken to their department, they are to warn the Guild Master, who then will schedule a feedback meeting with said Senior Officer. Where feedback on their officers and on the Guild Master will be given, as well as on the Senior Officer in question.
- The meetings with the Guild Master will be recorded by him/her and saved for security purposes.
- The meeting is developmental – not punitive. Everyone has strengths and
weaknesses.
Those are like a draft for guidelines, please let's discuss this as I was hoping we could start doing these meetings by the start of next week :D
Resources: Website 1 | Website 2 | Website 3
Edited Apr 23, 2015 at 09:14 PM by 0

ElridgeDec 04, 2014
Mo'jahi Ice-EyeDec 05, 2014