326
edits
Starbase 118 Ops Mentor Handbook: Difference between revisions
Jump to navigation
Jump to search
Starbase 118 Ops Mentor Handbook (view source)
Revision as of 16:05, 7 January 2023
, 7 January 2023updated with CO permission
Alora DeVeau (talk | contribs) m (corrected typo) |
Trovek Arys (talk | contribs) (updated with CO permission) |
||
| Line 15: | Line 15: | ||
<br /> | <br /> | ||
<br /> | <br /> | ||
Mentors are coordinated through, and allocated by, the Command Staff of Starbase 118 | Mentors are coordinated through, and allocated by, the Command Staff of Starbase 118. If you think that this is a job that you might like to do, review the following expectations and send a message to Commodore Sal Taybrim (Starbase 118) in order to apply. | ||
* You are asked to hold the rank of Lieutenant or above, with no disciplinary issues | |||
* | * You are required to sim consistently and at full-time | ||
* | * You have shown that you consistently adherence to Fleet formatting and setup | ||
* | * You have the capacity to check in with a mentee on a weekly basis | ||
* You are able to read every sim and are able to provide feedback in a timely manner | |||
* You are willing to collaborate with other mentors and seek to improve our mentoring program | |||
<br /> | <br /> | ||
<br /> | <br /> | ||
| Line 26: | Line 29: | ||
<br /> | <br /> | ||
<br /> | <br /> | ||
When a new Ensign arrives on the Starbase/Ship, they will receive a few specific emails. The first is a welcome from the Commanding Officer, and the second is the welcome from the First Officer. Once the welcomes are out of the way, the Commanding Officer will assign a mentor and hand off the Ensign to their specific mentor to ensure that both the mentor as well as the new member know what is going on. | When a new Ensign arrives on the Starbase/Ship, they will receive a few specific emails. The first is a welcome from the Commanding Officer, and the second is the welcome from the First Officer. Once the welcomes are out of the way, the Commanding Officer will usually assign a mentor and hand off the Ensign to their specific mentor to ensure that both the mentor as well as the new member know what is going on. Best practise is to check with CO and FO if such an email has been sent / will be sent. It will look like this: | ||
''Greetings Ensign, and Lieutenant, | |||
Ensign __________, I would like to introduce Lieutenant Commander Alora DeVeau (Amanda). She currently writes for our First Officer, and is a member of the Starbase command staff. She will be here to serve as a guide as you incorporate your character into the Starbase crew. She is a wealth of knowledge and assistance. She will be in touch with you on a regular basis with some pointers and a tips as you integrate further with our group. | Ensign __________, I would like to introduce Lieutenant Commander Alora DeVeau (Amanda). She currently writes for our First Officer, and is a member of the Starbase command staff. She will be here to serve as a guide as you incorporate your character into the Starbase crew. She is a wealth of knowledge and assistance. She will be in touch with you on a regular basis with some pointers and a tips as you integrate further with our group. | ||
| Line 36: | Line 40: | ||
If either of you need anything, let me know. | If either of you need anything, let me know. | ||
-Jamie | -Jamie'' | ||
</span></div> | </span></div> | ||
<br /> | <br /> | ||
| Line 47: | Line 52: | ||
Chances are they are very excited about getting started, but may not know just where to actually begin. By reiterating what has already been stated by the Commanding Officer and First Officer, and then offering to help get their characters involved by leaving them some tags, you can show them where to go to get information (the Wiki), and that we want them to be integrated and involved in the current plot. Below is an example introduction email that you can adapt to use as your own mentor introduction email. | Chances are they are very excited about getting started, but may not know just where to actually begin. By reiterating what has already been stated by the Commanding Officer and First Officer, and then offering to help get their characters involved by leaving them some tags, you can show them where to go to get information (the Wiki), and that we want them to be integrated and involved in the current plot. Below is an example introduction email that you can adapt to use as your own mentor introduction email. | ||
''Greetings Ensign ___________, | |||
As Jamie said, I sim for Lieutenant Commander DeVeau, the ship's Chief of Science, but feel free to call call me Amanda; we are all very informal out of character, and you never have to refer to anyone by their rank. | As Jamie said, I sim for Lieutenant Commander DeVeau, the ship's Chief of Science, but feel free to call call me Amanda; we are all very informal out of character, and you never have to refer to anyone by their rank. | ||
| Line 60: | Line 65: | ||
Amanda | Amanda | ||
(Alora DeVeau) | (Alora DeVeau'') | ||
<br /> | <br /> | ||
<br /> | <br /> | ||
| Line 77: | Line 82: | ||
<br /> | <br /> | ||
<br /> | <br /> | ||
Feedback is | Feedback is a vital part of the mentoring process. Mentors will provide feedback to new members about both the things that they are doing right as well as the things that they might need to improve on. Use examples or bits from other people's sims to show how things should be done correctly, but be sure not to overload the new member with lots of things that need to be fixed. Concentrate on one or two big things, then work your way to the smaller issues that might be occurring. | ||
Mentors are required to provide | Mentors are required to provide feedback emails on a weekly basis during a new members first mission. While some new members will not require intensive feedback, it is important to send an email anyway if only to reiterate that questions and comments are always welcome. | ||
Ensigns that have larger issues that need worked out will require more feedback emails. | Ensigns that have larger issues that need worked out will require more feedback emails. If there is a specific problem, mentors are asked to send feedback emails after each sim until the problems are resolved. Remember, provide examples so that the new member can really see what is going on and how they need to adapt to fit into the Starbase 118 style. | ||
<br /> | <br /> | ||
<br /> | <br /> | ||
{{LCARS-bar-heading|Staying Connected|200|COLOR=linear-gradient(to right, #e6be35, #c17207)}} | {{LCARS-bar-heading|Staying Connected and Providing Ops-Specific Information|200|COLOR=linear-gradient(to right, #e6be35, #c17207)}} | ||
<br /> | <br /> | ||
<br /> | <br /> | ||
Beyond the | Beyond the feedback emails, all mentors are required to send go through the mentoring templates. While it is less about sending out a template, we want to make sure that important information is provided to our new members, and that we offer a timely explanation and guidance regarding things like the Ops Voice Chat, Appreciation Forums etc. | ||
The end goal, for all new members, is to give them a 'friend' and point of contact on their home ship where they can feel comfortable asking questions and taking their first steps towards becoming a future leader within the fleet. | |||
<br /> | <br /> | ||
<br /> | <br /> | ||