Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Sinergise Handbook
  • Project information
    • Project information
    • Activity
    • Members
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Wiki
    • Wiki
  • Activity
Collapse sidebar
  • operations
  • Sinergise Handbook
  • Wiki
  • People operations
  • Mentoring

Mentoring · Changes

Page history
Create people operations/Mentoring authored May 21, 2021 by Miha Kadunc's avatar Miha Kadunc
Hide whitespace changes
Inline Side-by-side
people-operations/Mentoring.md 0 → 100644
View page @ 4e8077a1
A mentor focuses on both short and long-term professional development goals. They understand organisational culture and values well.
A mentor should:
- set clear goals for the mentee,
- the mentor should be responsible to set and communicate expectations and goals. The team should be included and pitch in
on expectations and help find the initial tasks. But, the mentor is the one that should ensure that the mentee gets enough
opportunities to work with all team members and get some feedback on the work from the team.
- have a weekly meeting with the mentee;
- regularly evaluate progress and provide honest feedback,
- clearly communicate expectations and priorities,
- identify and help with any blockers or issues;
- instead of solving the issue for the mentee, rather help them solve it on her own,
- try to pair (program).
- be available for help/support for the mentee, but should not actively seek involvement outside the set meeting unless requested by the mentee;
- recommended approach is the "15 minute rule" (if stuck for 15 minutes, mentee requests help).
When selecting the first tasks for the mentee, try to find smaller tasks that don't require a lot of context and knowledge of existing systems, but are still not isolated from what the team is doing. Initial tasks should be well defined and have a clear scope to avoid confusion and frustration.
Starting with such tasks will enable the mentee to complete them successfully, which will build confidence and momentum, and will allow the mentee to get comfortable with the codebase and team workflow early on.
The size and complexity of the tasks should increase gradually.
First week good practice example: the team prepares a string of shorter presentations/workshops about the tools, infrastructure, work organization, projects, apps etc.. The presentations should be practical if possible (mentees should get to know these by using/trying them out during these presentations).
A mentor works on two levels, both supporting the protégée in meeting essential job duties and helping them envision and take steps toward the career they desire.
A mentor combines instruction in professional behaviour and tasks with affective support.
A mentor may fulfil all or a combination of roles. The mentor:
- Advocates – Offers sponsorship, provides exposure and visibility within the organization.
- Acquires resources – Brings critical readings, opportunities, or experiences to the attention of the protégée.
- Acts as a role model – Offers insight on how they “made it” in the organization.
- Advises – Shares institutional and professional wisdom, critiques performance, makes suggestions.
- Coaches – Helps a protégée learn new skills and practice new behaviours.
- Protects – Helps a protégée find new and challenging opportunities within the organization while protecting them from adverse forces and “dead-end” job assignments.
- Supports – Listens with a sympathetic ear, explains unwritten rules, and acknowledges disappointments and triumphs.
A mentor should be someone from the team which the new colleague will join. If there is no one suitable for the role in the team, the mentee should join a team with an available mentor, until they become independent.
A mentee should also be aware of their responsibility in the relationship; they should:
- understand the value of the mentor's time (prep for the meetings, come with questions and comments),
- not try to show 'their best face' to the mentor, instead be real about expectations and objectives,
- be ready to receive and give feedback (input, advice or criticism),
- be open and ready to learn whatever they can.
The team coordinator should address any mentoring relationships in the team on regular 1:1s and schedule more 1:1s with any new team members. The team coordinator should try to solve or find help (e.g. through Pia, Miha or Teo) solving any issues in the mentoring relationship.
References:
- [1] https://www2.mmu.ac.uk/media/mmuacuk/content/documents/human-resources/a-z/guidance-procedures-and-handbooks/Mentoring_Guidlines.pdf
- [2] https://www.bc.edu/content/dam/files/centers/cwf/individuals/pdf/MentorGuide.pdf
- [3] https://www.xkyle.com/Being-a-Great-Engineering-Mentor/
- [4] https://ideas.ted.com/are-you-mentorable/
\ No newline at end of file
Clone repository
  • Benefits and Perks
  • Communication Channels
  • Employee Ownership of Sinergise Shares
  • Office Rules
  • Our Mission and Vision
  • Remote Work
  • Sinergise Core Values
  • Working Hours and Absence
  • _sidebar
  • Home
  • organization
    • Organization of Products
    • Organization of Teams
    • Organization
    • Team Coordinator Role
    • Upper Management
View All Pages