(to be done **after** you start work 😁 )
== General orientation === Readings =
As you would expect from a part of the Wikimedia movement, we have a sprawling mass of documentation. Here are some key pieces to get familiar with.
== General Foundation stuff ==
 our [staff handbook](https://office.wikimedia.org/wiki/Staff_handbook) on Office wiki. This is the official guide to organizational policies, principles, and benefits.
 the [guide for new hires](https://office.wikimedia.org/wiki/Guide_for_new_hires) on Office wiki. Edit this if you figure out something important is missing or outdated!
 the [staff and contractors page](https://wikimediafoundation.org/wiki/Staff_and_contractors) on the Foundation website. You probably already know about this.
 our [internal contact list](https://office.wikimedia.org/wiki/Contact_list) on Office wiki.
 watch: [[ https://docs.google.com/file/d/0BxiTHaqH0xCRS2ZjMHNvV0hxRms/edit | a video on transitioning from volunteering to being on staff ]]. It's a few years old, but has some good nuggets.
 The [Wikimedia 2030 strategic direction](https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Direction).
 The [Foundation's current annual plan](https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2018-2019/Final). This includes Audiences's work, but at a very general level.
== Audiences and Product Analytics stuff ==
 The [Audiences annual plan](https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2018-2019/Audiences). This has the specifics projects the whole department (almost) will be working on for next 11 months, as well as the metrics we've picked to measure them. The main focus is on contribution tools (which means "the Readers team" is no longer an accurate name, although we haven't changed it), and the secondary focus is on better use of data, so there's //plenty// to keep us busy! 😛
 The Community Health Initiative's [separate annual plan](https://meta.wikimedia.org/wiki/Community_health_initiative/Annual_plan_FY18-19). It's a few years old,The Community Health Initiative is a cross-departmental program of Community Tech's Anti-Harassment Tools team, which you'll be working with, and Community Engagement's Trust and Safety team.
 Marshall Miller's research and recommendations around the better use of data program ("the Marshall Plan"). but has some good nuggetsThere's an email out to him asking for the best links.
=== Access ==ounts and communications =
 Get access to [Office wiki](https://office.wikimedia.org/).
 Get set up with a staff wiki account.
 Edit your CSS and JS so that it's distinct from your personal account. (Might I suggest the version from [my global JS](https://meta.wikimedia.org/wiki/User:Neil_P._Quinn-WMF/global.js)? 😁)
 Confirm your access to the [Product Analytics team drive](https://drive.google.com/drive/folders/0AOfflhB7kgNjUk9PVA).
== Communication== Mailing lists ==
Join (see [office:Mailing lists](https://office.wikimedia.org/wiki/Mailing_lists) for instructions if necessary):
You //may// also want to join firstname.lastname@example.org, which is a public list for general discussion of Wikimedia engineering. It's focused on software development, so it's not highly relevant to our work, but it can be helpful in keeping abreast of which engineering projects are underway.
Verify that you're subscribed to:
 Set up email filters so that mail from most mailing lists bypasses your inbox and goes to a folder which you can check occasionally. You don't want to skip this ;)
 Set up your Google Calendar so that meetings you create are modifiable by other attendees by default. - thisThis is found in settings
 Get familiar with [Hangouts Chat](https://chat.google.com/)
 Join IRC rooms
== Profiles ==
 Add a profile photo to your staff G Suite account.
 Set up a Meta-wiki user page for your staff account.
 Add yourself to [our team page](https://www.mediawiki.org/wiki/Product_Analytics#Who's_on_the_team?)
 Add yourself to the Office wiki contact list.
== Meetings and team integration ==
The following is a list of people you should meet with to get to know them (if you don't already) and to hear about their work and their current priorities. It's up to you how long to schedule these for—I'd generally recommend an hour so you can have a comfortable conversation, but 30 minutes could work too if they're busy. This will add up to a significant chunk of time, so you can space these out over several weeks: there's no huge rush. I've batched some of these together, but feel free to tweak that if you see a better way.
 Set up your weekly 1-on-1 with Jon Katz
=== Growth team ===
You are embedded in the [Growth team], which means you'll form part of the team on a day-to-day level.
 Get added to their standups
 Get added to their mailing lists, chat channels, and so forth
You should set up one-on-one meetings to get to know the following people:
 Marshall Miller, product manager
 Jazmin Tanner, program manager
 Ryan Kaldari, engineering manager
 Benoît Evellin, community relations specialist
 Roan Kattouw, lead engineer
=== Community Tech ===
You're also assigned to [Community Tech](https://www.mediawiki.org/wiki/Community_Tech), which means you're on call for reactive support. You should decide with the team what that means (e.g. which recurring meetings will you attend? which communication channels will you follow?).
Have introductory meetings with:
 Joe Matazzoni, product manager
 Niharika Kohli, product manager
 Trevor Bolliger, anti-harassment tools product manager
 Moriel Schottlender, lead engineer
== Others ==
The other Contributors product managers
 Dan Garry
 Pau Giner, Runa Bhattacharjee, and Amir Aharoni (the Language triumvirate)
 Danny Horn, director of product
Research and Analytics
 Nuria Ruiz, analytics manager
 Andrew Otto and Dan Andreescu
 Dario Taraborelli
 Erica Litrenta
 Sherry Snyder and Nick Wilson
= Readings =
 Annual plan
 Marshall Miller's better use of data plan