| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
public:nnels:etext:pa-communications [2022/02/24 09:48]
rachel.osolen |
public:nnels:etext:pa-communications [2022/05/24 07:00] (current)
rachel.osolen [Modes of Communication for Production Assistants] |
| This additional support will last the first 2 months of employment, after which the employee will be expected to work more independently. | This additional support will last the first 2 months of employment, after which the employee will be expected to work more independently. |
| |
| After training is complete, the Production Assistant will continue to make regular checkins on progress. This will include direct comments in the RT ticket of a book to see how progress is coming, general emails to check in on overall performance, as well as biweekly one-on-one Zoom meetings to allow the opportunity for employees to communicate with questions or concerns directly with the Supervisor. These meetings are generally 30 minutes long, but can go shorter or longer depending on the needs of the Production Assistant at that time. | After training is complete, the Production Assistant will continue to make regular check-ins on progress. This will include direct comments in the RT ticket of a book to see how progress is coming, general emails to check in on overall performance, as well as biweekly one-on-one Zoom meetings to allow the opportunity for employees to communicate with questions or concerns directly with the Supervisor. These meetings are generally 30 minutes long, but can go shorter or longer depending on the needs of the Production Assistant at that time. |
| |
| If there are special circumstances, such as death in the family, or illness, the employee can contact the Production Coordinator directly via email to discuss how this will impact their workflow. | If there are special circumstances, such as death in the family, or illness, the employee can contact the Production Coordinator directly via email to discuss how this will impact their workflow. |
| * questions relating directly to feedback | * questions relating directly to feedback |
| * notes on language, or other special features you feel needs attention | * notes on language, or other special features you feel needs attention |
| * tweets for title | * Draft tweets for highlighting the book on the NNELS Twitter |
| |
| <note>All communication through RT is posted through the comment function. Never send it through the reply function, as that sends it to the patron. See [[public:nnels:etext:workflow|Using RT]] more information.</note> | <note>All communication through RT is posted through the comment function. Never send it through the reply function, as that sends it to the patron. See [[public:nnels:etext:uploading_finished_file_and_passing_rt_ticket_to_production_coordinator|Uploading Finished File and Passing Back RT Ticket]] more information.</note> |
| |
| ''Q&A'' is used for communications about: | ''Q&A'' is used for communications about: |
| * Special Projects | * Special Projects |
| |
| <note>The Production Coordinator will send out emails for every wiki update, as well as any changes in production workflow. Please reply to each email to let the Production Coordinator know you read and understood the updates. As this is a remote position, we need to be more direct and concise with our written communications.</note> | <note>The Production Coordinator will send out emails for every wiki update, as well as any changes in production workflow. Please reply to each email to let the Production Coordinator know you read and understood the updates. As this is a remote position, we need to be direct and concise with our written communications.</note> |
| |
| | ''Discord'' is for direct communication between staff (note the Production Coordinator is a moderator). The Production Coordinator will add you to the group. This is not a replacement for the Q&A or the wiki, but a place to talk out more nuanced issues and ideas. This can include but is not limited to: |
| | * Help with how to describe a tricky image. We all get stuck on something! Sometimes it can even be something simple, but our brains get a little stuck. This is a great time to bounce ideas and get suggestions from each other! |
| | * Tips and Tricks on using Word. Learned a new short cut? Feel like a task is taking you too long, and are curious if others have a workaround? Great way to develop skills together! |
| | * Discussing a cool book. Maybe you are working on a really cool book, and you want to share it with the group! |
| | * Work/Life balance. How to not overthink and take good breaks. |
| |
| | <note>Discord is new to the team. We have used other similar platforms in the past, and where not as successful. We are hoping you guys can use this to support one another. If you have an idea for a topic, you can add it to the above list, and to the Discord group. Make it your own!</note> |
| | |
| | <note>The Production Coordinator will be monitoring the channels to help out when needed, and taking note of anything that would be good to add to the wiki. Please still use the Q&A for your questions about production and the wiki. This is so other PA's can see those answers quickly and easily, and they don't get lost on Discord.</note> |
| | |
| | |
| | [[public:nnels:etext:start|Return to main eText Page]] |
| |
| |
