Open rickr opened 7 years ago
Proposal: Move Mentorship Management to Discourse (shelved, 10/5/2017)
Proposal: Improve Slack tooling, utilize OC web app, keep Airtable for data storage Suggestions from @kylemh from phone discussion on 10/5/2017:
Assigning new mentees to a mentor in a timely fashion:
Assign the mentee to the mentor:
Use previous Mentor Request Form (temporarily not in use, see front-end issue 341 and back-end issue 155).
Mentors API (with small schema) and an interface on the front-end lists selectable mentors. When form submitted, pre-populates Airtables form.
Notifying mentors: If mentee chose no mentor preference, all mentors with the desired skills are DMed. First claim gets it. If mentee chose a specific mentor, DM that mentor with the request record and the easy option to confirm deny. Maybe even to create an event on their device? (expanded on this in https://github.com/OperationCode/operationcode_bot/issues/89 in Slackbot repo)
Monitoring the state/progress of the mentor/mentee experience: Bot that pings mentor based upon Mentorship event date. "It's been a week since your scheduled mentorship event with Billy Bob. How'd it go? FEEDBACK LINK HERE"
Track active mentors: Multiple options 1) Dont track. Have Slack bot hit every mentor, but they can opt-out at any moment. Bi-annually remind mentors that they've opted-out to try to bring them back in. 2) Use Slack data to identify active mentors
We will also need to make the mentorship request form accessible only to eligible mentees.
Key stakeholder: @jjhampton
Pain points from our discussion on 10/5/2017 around mentor management: