Skip to content
This repository was archived by the owner on Sep 4, 2018. It is now read-only.
This repository was archived by the owner on Sep 4, 2018. It is now read-only.

Mentorship Management Improvements (Epic) #758

Description

@rickr

Key stakeholder: @jjhampton

Pain points from our discussion on 10/5/2017 around mentor management:

  • Assigning new mentees to a mentor in a timely fashion:
    • Goal is for a mentee to have a response from a mentor within 24-48 hours, once a mentor service request is made.
    • To notify mentors of a request, we currently rely on:
      • Slackbot that posts one-time to the #mentors-internal channel when a request is made. This requires mentors to actively monitor the #mentors-internal channel.
      • Volunteers who manually scan the Airtable sheet on a semi-regular basis to see if there are outstanding requests.
    • The above options are not ideal. They open the possibility for requests to slip through the cracks and go unfulfilled. (this has happened before)
  • Monitoring the state/progress of the mentor/mentee experience:
    • How can we easily track when a mentor service request is fulfilled? Currently we rely on mentors manually entering this data on Airtables, which rarely happens.
    • How can we track the progress of mentees in a quantifiable way? We should aim to automate the gathering of data on:
      • How many mentees we've helped?
      • Which mentees have progressed to a new level of expertise?
  • Track active mentors:
    • Our Airtable sheet currently lists 82 people who have signed up as mentors. In order for our volunteers to easily match incoming mentees -> mentors, we need to be able to filter this list to identify which of these are active mentors that have capacity / willingness to help mentees.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions