Reps/SOPs/Mentoring Training: Difference between revisions

From MozillaWiki
< Reps‎ | SOPs
Jump to navigation Jump to search
No edit summary
(Redirect to Coaching)
Line 1: Line 1:
{{outdated}}
#REDIRECT [[ReMo/Coaching]]
Mentoring is core to the success of the Mozilla Reps Program.  You can find the Mentor SOP [https://wiki.mozilla.org/ReMo/SOPs/Mentoring here].  This page outlines steps identified for Mentor training.
 
Mozilla Reps are community builders, community managers and the core of the program - please suggest updates to this training.
 
=Mentor Orientation Steps=
 
#'''Attend On-boarding''' Call: New Mentors are invited to a meeting with some members of Reps Council, as an opportunity to ask questions. A this time council will reinforce the invitation to mentors as partners in community health and success.
#'''Attend Training Call''' / Or Review of Training Video(TBA), which is based on this Wiki.
#'''Subscribe''' to reps-mentors@lists.mozilla.org
 
=Resources=
==Community Resources (please add more!)==
Working with community, even with people you know very well can come with unexpected challenges, victories and questions the need for more information.  Here are some suggested resources, but PLEASE, please add yours:
 
* [http://www.artofcommunityonline.org/about/ The Art of Community]
* [http://www.dealingwithdisrespect.com/ Dealing with Disrespect]
* [https://github.com/christi3k/policies/blob/master/citizen_code_of_conduct.md Code of Conduct]
* [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla Community Guidelines]
 
==Rep Resources==
*Currently reviewing what should go here, as we have quite a few outdated wikis.
 
=Mentoring Overview=
==Task Types==
The Mentor SOP outlines the Mentor role as consisting of both Administrative and Mentoring duties. ''Administrative Duties'' speak to the role's obligations reviewing applications, sending 'Welcome Packs' and reviewing Bugs, while Mentoring Duties are those skills that best relate to the success of Reps mentees on a human level.
 
[https://wiki.mozilla.org/ReMo/SOPs/Mentoring You can read more in the Mentor SOP.]
==Budgets==
One of THE most helpful, meaningful, awesome, impact-ful, productive, '''WONDERFUL''' things you can do for the program is to properly review budgets.  Here are some high-level suggestions for making council's work easier, and budgets more likely to pass through without challange:
* Ask questions about metrics if you don't understand them, or if seem overly optimistic for an event. Suggest metrics your mentee may not have considered.
* If Reps have hosted similar events, ask them to evaluate (with you) ways to improve with new events based on their experiences (blog posts and metrics) of the past.
* Encourage Reps to seek donation of space, partnership for catering and any other inventive methods of saving money they can come up with. 
* Discourage travel where unnecessary
* Ensure Events have detailed agendas
* Watch over-bloating of catering or printing, and make suggestions for cutting back.
* [Please add other questions you think are valuable in this process!]
 
[https://wiki.mozilla.org/ReMo/SOPs/Budget More on Budget SOP process Here.]
 
=Communication=
 
You'll notice this section is quite long, but it only speaks to the importance of communication for Mozilla Rep Mentors!
 
==Communicating with other Mentors==
 
It's important to understand that as a new mentor, you have a community of mentors to lean on, and to ask for advice.  There is a LOT to mentoring, and so don't be shy about posting questions on the dist list, or requesting feedback.  Or if you find yourself to have great success in one area, sharing that will help others too.
 
==Communicating with Council==
 
You are your mentees first line of communication, BUT please know that council is exists to support you on matters that may feel out of your comfort-zone or expertise to deal with.  Please reach out any time for assistance.
 
Although not specifically communication-related, one of the most important things you can share is the news (and names!) of new and emerging leaders.  Mozilla leaderhip is often asked seeking community opinions, and while we are good at celebrating existing, and longer-term leadership it's a goal to be more deliberate about including emerging leaders in discussions: Diversity of new visions, new ideas, new energy helps us grow in health.  '''Please help us identify emerging leaders!'''
 
==Communicating with Rep Mentees==
===Design and implement feedback loops===
Based on the Orientation call, be deliberate about scheduling communication with your mentee.  Time can go by very quickly without realizing it's been one month, or two - or three.  Adding it to the calender as a reminder ensures consistency which really makes a difference for your mentee.  And for you!  Now is a good time to think about how communication with our own mentor is working, and whether that needs revisited as well.
 
Ensure your communication times have specific goals, even if it's just to ask for feedback, on how a recent event went, how they feel about something recent in the program (like change to reports). 
Always keep in mind opportunity to improve the project by elevating feedback to other parts of the project.
 
*If feedback indicates an issue that council should be aware of, please email council with details.  Examples  could be:
* Discussions where your mentee reports having faced abusive behavior in the community.
* Discussions where your mentee expresses concerns about misused funds or swag in their community.
* Discussions where your mentee shares successes, ideas and/or initiatives that could benefit the Reps program as a whole.
* General concerns you may have about your mentee, that may be too personal to discuss with the mentor community.
 
# If  feedback is important to a functional area, or leadership in general encourage your mentee to reach out to those groups or offer to do it if they are not comfortable.
 
'''The general point being - that there is opportunity for the entire project in feedback from the 'front line' of the project.'''
 
==Reviewing an applicant==
One of the most important jobs you'll have as a mentor is to interview a mentee. 
 
* [[ReMo/SOPs/Mentoring/Screening|Please review the SOP on this topic.]]
 
=Mentorship as a gateway to new opportunities=
==Leadership in Mozilla and beyond==
Mentorship is an opportunity to grow your leadership skills, which lend well to your future career goals, wherever that may lend.  Some 'real-world' skills you build as a Mozilla-Rep Mentor include (please add yours)
 
* Problem Solving
* Conflict Resolution Strategy
* Communication & Feedback Design
* Volunteer Management
* Counseling
*
Mentorship is opportunity to grow and develop professionally as well as personally.
 
=Reps Portal =
* Review of Mentor Dashboard on Reps Portal
Rep's Portal is constantly being improved, currently you'll find the following features available to help make your work easier.
 
==Dashboard==
Also available to Mentors, the Dashboard has new features available to you including the 'my mentees' tab for activities and actual 'Mentorship' section where assigned mentee bugs will lives, until closed. 
 
From the Dashboard you'll also find links to Mentee Reports , and an an option to 'Email Mentees' which can be used for quick correspondence.
 
==Best practices - email filter==
 
It's a recommended task, to setup filters for bugzilla and mentee communication.  We all get a lot of email these days and flagging those directed to Reps Mentor list, and from your mentees will ensure you don't miss anything important :)
 
* Best practices scheduling mentee communication
See Orientation Call
 
=Resolving Conflict=
First and foremost the most important first step you can take when dealing with a conflict is to reach out to your own mentor AND council for advice.  Also be aware of the [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla Community Participation Guidelines] when recommending steps for your mentee and for yourself.
 
== Regional Communities ==
 
More to come soon...
 
=Invitation to SOP=
All SOP are yours to help improve, please make suggestions, edit mistakes, outdated content and help us keep s keep quality resources.
 
=Transitions=
==Stepping down as Mentor==
Please inform your mentees of your decision and reach out to council for next steps. 
 
===Absence===
From time to time, you may be unavailable, and it's important to communicate these absences to those who depend on you. 
 
* If you are unavailable, please add an auto-responder to your email letting mentees know of our absence, and who to contact in your absence.  Alternately you can reach out to them individually using the Reps portal for messaging mentees or through personal email.
* If your absence is extended greater than 3 months, please reach out to council with a request for reassignment of mentees, or a plan for this time period.
 
 
===Wrap Up===
====Importance of the role====
In mentorship lies the potential to unlock the possibilities of all Reps can achieve together if we value the opportunity of empowering each other. This role is core to the program.  As much as this training is meant to guide you on the process, we invite YOU to continually share you unique insight into how to make things better.
 
====Value of this role to Reps Leadership, and Mozilla Leadership====
Mozilla leadership includes Reps leadership in their plans for the future of the project. 
 
====We Love you====
You should be proud of all you have accomplished, this role is recognition of your past contributions, but also your potential to be a great leader.  We look forward to sharing this journey with you.

Revision as of 14:13, 21 July 2018

Redirect to:

Retrieved from "https://wiki.mozilla.org/index.php?title=Reps/SOPs/Mentoring_Training&oldid=1197683"