1. - Book a 1:1 with the new Product Manager for day 1
  2. - Schedule a reminder to check in on their onboarding issue, how are they doing, how can you help, etc. that is recurring for their first 6 weeks.
  3. - Suggest handbook pages they may find useful
  4. - Remind them to introduce themselves
    • In #new_team_members
    • In #product
      • You will get introduced in the next product meeting and asked where did you work before GL, why did you join, where are you located, what do you do for fun outside of work.
        • You may share with them how you introduced yourself.
  5. - Encourage them to organize a group call with the other new hires
  6. - Intro to slack
    • Channels to be aware of
      • Product related - #product, #uxresearch, #competition, #analyst-relations, #analytics, #analytics-social, etc.
      • Fun - #random, #allcaps, #loc channels and there are others, just search for things you might find fun and interesting.
    • Tips/Tricks
      • Update your profile in Slack, especially your working hours and location
      • Make use of starred channels, what’s most important to you.
      • Add keywords to get alerted on for your product area, competitors, etc.
  7. - Add a reminder for once a week to ask what they couldn’t get an answer on this week, how to get them unstuck for the first 6 weeks.
  8. - Ask them after a few days if they got their team page MR merged.
  9. - Tips / Tricks for sensing mechanisms
    • There is a good breakdown of sensing mechanism in the handbook. Some other things I have found useful are;
    • Go other places customers/user are like the Denomas forum and Discord, Reddit and HackerNews are just a few.
    • Issues - It is good practice to review new issues assigned to your group that may get missed by the weekly triage issues. There can be good conversation to be had discussing problems/desired outcomes with users within a day or two of them creating an issue.
    • Slack - Adding keywords to your Slack alerts like your category name, competitor names, etc. is a good way to stay on top of issues bubbling up, potential customers, etc. in channels you are joined.
    • Analyst Reports - You can inquire about access to reports from analysts in the #analyst-relations channel.
  10. - The flow of a milestone
    • Rough timeline of the flow
    • Planning
      • Each milestone there is a kickoff issue created and assigned to PMs. Link your planning issue in that and once recorded your kickoff call.
    • Kickoff call
      • Hold a call with your Designer talking about the issues the team will work on that milestone with preference to issues that are ~direction AND ~Deliverable.
      • Company wide call
    • During the milestone
      • Keep an eye on your TODOs if you use them for pings/questions from your development team or customers/users asking about progress on issues to keep them moving.
    • Release posts
      • Important deadlines are having them in review by Technical Writing and PMM two weeks prior to the release and merged 7 days prior to the release.
    • Moving issues that do not finish in the milestone
      • This is an [/handbook/engineering/quality/triage-operations/#milestone-reschedule] to move issues that do not finish in amilestone but it’s good to review issues that were not closed in a milestone as it does not move confidential issues.
    • Retrospectives
    • Direction updates
      • There is no wrong time to update your direction pages when something has changed. The cadence of a release is a great time to schedule it to ensure it is happening regularly though.
    • Performance Indicators / OKRs
      • After the close of a milestone it is a good time to regularly check in on your Performance Indicators and OKRs for the quarter.
Last modified November 29, 2023: big update (17188382)
View page source - Edit this page - please contribute. Creative Commons License