Onboarding Checklist

This doc is for: People onboarding new members after orientation
How to contact people about this doc: Post in #clean-slate Slack channel
What and why: We rotate the onboarding role because it's a taxing one. This should help those with previous experience use the latest agreed upon information/methodology and help those with no experience run it with minimum pain.

We will try to answer what we’ve found that works, what dead ends we hit, and why we made the decisions we made. We will try to put answers to the most frequently asked questions at the top.

1. Settle down in a space outside of the project meeting room.
2. "Do you have any questions before we get into this?" Pause for 8 (?) seconds to let someone speak up.
3. Answer reasonable questions.
4. "A few details first - We have a data team and an app team. The data team is working on finding and analyzing data about how changes in regulations could affect people. The app team is working on online tools to help people who are trying to expunge their criminal records. You can look into both teams, but we work separately, so you'll have to pick one at a time to sit with."
5. "Also, this is project has been going on for a while so you may have a bit of reading to do to get up and running. We're still working on our documentation, but I'll connect you with what we've put together at the end of this."
6. "If this project isn't a good fit, there are other projects here that need help and new ones come up every few months. There will be no hard feelings!"
7. Go in a circle. For each person:
   1. Ask what work they'd find meaningful at Code for Boston.
   2. Appreciate what they say.
   3. Discuss where that fits in with our project
      1. If you know where they might fit into the project, mention it.
      2. If not, say you'll talk with the group to see if there's a good fit.
      3. If you know it's not a good fit and know where else they can be directed, let them know about it. They can then decide whether to stay or go.
   4. "You don't have to answer now, but we'd like to know what kind of bandwidth you have for this. Is it just Tuesday nights or also times during the week?"
8. Connect them to our tools:
   1. Slack (they can click the link at codeforboston.org)
   2. #clean-slate channel
   3. #clean-slate-app and/or #clean-slate-data channels
   4. Github - make sure they have an account and get added as collaborators to our repo
9. Have them open links
   1. For everyone:
      1. Question asking doc
      2. Repo home page
      3. Fist-to-five participation (not "voting") documentation
   2. For app people:
      1. App intro page
10. Practice fist-to-5:
    1. Have them read the fist-to-5 right then and there
    2. "I propose we wrap up here and go back into the room. Fist-to-5."
    3. All votes should be 4's or 5's.
    4. "All you 4's agree that you will help implement this and all you 5's agree that you will help lead this, right?"
11. "If you have any questions, write them in the new member questions doc and we'll see if we can address them at the next meeting."
12. When you bring them into the room, see if folks are at a good point to pause and go around saying names.
13. Show them where to sit for their team of interest.

Note: We may want to check if we can have regular access to the surveys prospective new members fill out.