Skip to content

Instantly share code, notes, and snippets.

@bkatiemills
Last active December 18, 2015 19:49
Show Gist options
  • Save bkatiemills/8b9d43addfb98d63d50c to your computer and use it in GitHub Desktop.
Save bkatiemills/8b9d43addfb98d63d50c to your computer and use it in GitHub Desktop.

mentorship-workflow

Some explanations:

  • Mentorship Meetups are intended to be generic help sessions, where groups of newly badged instructors meet with a mentor once or twice a month to discuss progress towards teaching in a workshop. The mentor will create a space where new instructors are comfortable asking questions, facilitate conversation between instructors so they can support their peers in this process, and offer guidance where necessary. These meetups are soft-mandatory for new instructors until they teach their first workshop; Instructor Training should funnel all new trainees there as the clear next step.
  • Pre-workshop Checkin - to be discussed, likely a troubleshooting session to make sure everything is on track in the final leadup to the workshop.
  • Topic-specific help sessions have been floated previously, like intro to git and how to teach python; these focused topic sessions will serve to take the pressure off the more general Mentorship Meetups by answering common questions, and also be open to the Instructor community at large.
  • Community Management Pings are simple, 1:1 emails asking Instructors how they're doing and if they're thinking about teaching another workshop, best delivered a few months after their last debriefing to encourage them to come on back and teach another workshop.
  • Phase I / Phase II Offerings distinguish between must-haves (phase I) and nice-to-haves (phase II). The Phase II offerings are conjecture only at this point and should not be implemented until more evidence for their necessity is observed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment