Hacker News new | past | comments | ask | show | jobs | submit login

If I am joining a new team or company and therefore getting a new manager, my 1:1 meetings generally support my onboarding. I would ask about the team's current processes, how they got there, who to ask about learning the system architecture, etc. I also try to get a feel about what the new manager's style is. How does the manager want to stay apprised on my work, what is his/her approach to career development, etc. And very importantly, I ask how often we should have 1:1s.

If the new manager is joining my existing team as my manager, 1:1 meetings now support my manager's onboarding. The topics are very similar, but I have to be a little more tactful to avoid appearing arrogant or patronizing. I will ask what he/she thinks of the product we work on, or about the system architecture. Once again, I will try to get a feel for the manager's management style, and I will ask about the approach to career development and future 1:1s.

In either case, my number one goal early on in 1:1s is to build rapport. I don't intend this as a "winning favor" type of thing, but rather I need to do my best to build the relationship from my side so that I feel comfortable raising concerns and I can understand where my manager is coming from when inevitably he/she starts making new requests.

I don't like to share a 1:1 agenda until it's clear that the manager respects 1:1s. Otherwise there's a risk that the manager preemptively invites other people to help answer the topics in the agenda.

I try not to rant or complain in 1:1s anymore. I found that my managers' reactions were rarely predictable. Some managers try to solve the problem immediately, and some managers do nothing. Some managers would move me onto another project. Now that I have more experience, if I have a complaint, then I also try to propose a solution.

Finally, I try to avoid using 1:1s for status updates or escalating blockers to my manager. In my mind, these are best done as needed or as soon as possible.




This is really good advice ^

Measured, and with good variation.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: