Live data from Hacker News

Meeting everyone on a new team

annashipman.co.uk

11–20 of 87 posts

Re: Meeting everyone on a new team

#11
Perfect timing. I just joined a company this past week as a software engineer. Day one, I knew 5 people, only topically. By the end of week 1, I have introductions/1:1s scheduled for 30+ top-notch people at the organization. Here's the method I used to do this:

I created a really comprehensive intro email about myself (work stuff, personal stuff, passions, etc). I wrote this in Google Docs, so it would be easy to paste into Gmail, and preserve the nice formatting. In this email, I included several questions (see below), which I wanted to ask the person. I got these questions from a few sources, including "The first 90 Days" book, along with some other questions I found through Google. At the end of the email, I marked in bold: Suggest 3 other amazing people for me to connect to, and why you recommend them.

I sent the emails out, and got replies within 1-2 days - 75% provided me with 3 names! If some did not provide me with names, I politely followed up with warm, thankful email, but also a reminder to please send me name, which each of them did.

I then sent out "cold" emails to THOSE people, starting with "X person said to reach out you" (helping bring a familiar name immediately at the beginning of the email). I used the exact same email template for that, along with asking for more names.

I used a Google spreadsheet to keep track of all the people I reached out with, along with columns for questions, the people they referred, and who referred them.

At current, I have 15 1:1s scheduled for next week, and tentatively 5-10 scheduled for the week after. I'm using labels in Gmail to flag "@ Waiting" for the people who have not responded, so that I can follow up after a few days.

In the meeting invites I sent to folks, I included the agenda items in the description, so it was top-of-mind for them, as they checked their calendar.

I'm using a note taking tool called Obsidian (https://obsidian.md/) to take notes on all the conversations I'm having with people. This tool lets you write in markdown, and quickly crosslink topics (like a personal wiki). The goal is to create a knowledge base of information, based on all the "here's what you need to know" topics that people share with me.

Finally (and important). I made sure to set expectations with my manager before doing this. I basically told him: (1) I am going to setup conversations with many people this first 2 weeks of work. (2) I will use this output of these conversations to build a learning plan of topics which these people suggest focusing on, (3) I will then synthesize these notes, and will share them with you (manager). (4) You and I will review the learning plan, and prioritize it together. (5) We will use this plan, along with our weekly 1:1s to build out a 30/60/90 day plan.

This was important, because it allowed me to "buy time" before being thrown into a million meetings, assignments, etc. Each person I have spoken to so far has had different suggestions on what the first several things to focus on, learn, etc are. However, they have all been incredibly valuable - and in many cases, they are things I would not have immediately known to even list down.

The great part about this approach (in my opinion), is that all of the people I'm meeting are essentially pre-selected for awesomeness by someone awesome. All of the conversations have been enormously valuable.

The feedback I've gotten from the people has been really great, and validating!

Bonus: I have been using an app called UpHabit (https://uphabit.com/), which is a "Personal Relationship Manager". It lets you tag people (e.g. by skill, passion, etc), and then assign regular reminders to reach out to them (e.g. "connect with this person every 3 months"), and lets you take notes on the conversations you had. I have found this tool enormously valuable, as its allowed me to "scale" my personal network, and trust that important people don't get forgotten. I find myself a very LIFO person (the people I most recently connected with, I'll remember to connect with. The folks from long time ago, I often forget). This tool has been helping me re-invigorate my personal/professional relationships.

Note: I have no affiliation with either of the tool recommendations in this post, aside from finding them very useful!

Below are the questions I included in my intro email. If anyone would like to see the "full" email, I could probably generify it, and share directly.

--- Tell me about yourself! If you feel comfortable sharing, I’d love to hear what you are personally passionate about, and what topics, processes, areas etc you are passionate for at X.

What is your role & your responsibilities at X?

What’s a “day in the life” like for you? This helps build empathy and understanding for your world, and how I could best help.

What are your top 3 priorities in the next two months? What specifically are you hoping to achieve?

What do you feel are the top 3 challenges/blockers (1) facing X, (2) facing your team, (3) you professionally at X?

What is your understanding and expectations of me and my role?

How do you envision us working/partnering with one another?

If you were in my shoes, what would be the top 3 things you would prioritize, learn, or focus on in the next month or two?

For each of the above, what would be an actionable next step to make progress? (it could be as simple as, “reach out to X person”, or “read this blog post”)

What do you think would be some realistic, achievable and impactful “quick wins” or contributions I could make, for me to consider taking on as I get started at the company?

Very Important: Suggest 3 amazing people at X for me to reach out to, who you think connecting with and learning from would help make me successful in my journey at X. Be sure and tell me what about these people is so amazing & awesome!

Re: Meeting everyone on a new team

#12
> With a team of ~50, that’s a lot of hours, and I was also working four days a week so each meeting takes up a greater proportion of time.

At thirty minutes a pop these meetings come out to 25 hours. That does not strike me as “a lot of hours” given that this is talking to everyone who works in your department. Put another way is like a sanity check on the biggest and most important category of your department’s budget, at roughly 1% of your annual time.

Re: Meeting everyone on a new team

#14
post #13

Would a similar strategy be valuable for an IC (individual contributor) joining a new team? For example, setting up 1-on-1 meetings with direct teammates soon after joining.

Yes! This is what we do. We even explicitly typically put it in your 30 day plan.

Re: Meeting everyone on a new team

#15
post #9

I did something very similar when I joined my last team. I like Anna's questions. One of the questions I asked was 'who do you go to for advice and bouncing ideas off'. This gave me a great view of the key knowledge nexus points and how people are connected to each other in the team. After I'd spoken to everyone, I created a report for the executive committee summarizing all topics that had come up multiple times, an…

Oh man, I love that “who do you go to for X?” question. I’m starting as an SWE on Monday, so that’s big on my mind.

what is SWE?

Re: Meeting everyone on a new team

#16

> With a team of ~50, that’s a lot of hours, and I was also working four days a week so each meeting takes up a greater proportion of time. At thirty minutes a pop these meetings come out to 25 hours. That does not strike me as “a lot of hours” given that this is talking to everyone who works in your department. Put another way is like a sanity check on the biggest and most important category of your department’s bud…

At the exec level, a good 70-80% of your time is probably unable to budge, so 25 hours of discretionary time _is_ a big investment - probably most of your discretionary time for a calendar month. It sounds like it was well worth it though.

Re: Meeting everyone on a new team

#19
With remote working becoming so prevalent the thought has crossed my mind about what it might be like to start a new job without having much contact with most people who work there.

Seems like it would be harder to become friends with coworkers, or easy feel isolated in your work (particularly outside of software development).

Re: Meeting everyone on a new team

#20
post #11

Perfect timing. I just joined a company this past week as a software engineer. Day one, I knew 5 people, only topically. By the end of week 1, I have introductions/1:1s scheduled for 30+ top-notch people at the organization. Here's the method I used to do this: I created a really comprehensive intro email about myself (work stuff, personal stuff, passions, etc). I wrote this in Google Docs, so it would be easy to pas…

Thank you for posting this! I'm going to be starting a new job sometime soon, and this is giving me all sorts of ideas! Especially thank you for being so comprehensive in your comment. Some questions:

What size is your company, and what level of SWE are you? Did your referrals tend to move up the org chart, or stay at the same level? Is your role very broad? I ask this last one because a question like "How do you envision us working/partnering with one another?" seems like something I would ask an immediate coworker, not necessarily someone two connections away. Are you a tech lead, or someone with reports (or some other position of authority?).

Finally, one of your questions contains what appears to be your company name, I don't know if it was intentional to leave that there, just letting you know.

Post reply on HN