Live data from Hacker News

Ask HN: What do you talk about in 1-on-1s with your managers?

news.ycombinator.com

11–20 of 287 posts

Re: Ask HN: What do you talk about in 1-on-1s with your managers?

#11
Something I've noticed over my roughly decade career, having ~10 managers during this time...

If you're not having interesting conversation directly related to your work during 1:1s, it's likely that things are going well for you, or you have a bad manager.

Assuming you don't have a bad manager, then they would be discussing things that aren't going well with you. So if that's not the case, then you're doing fine. Use the 1:1 as a chance to talk about your backgrounds, interesting things you've noticed at work, eventual improvements you would back, possible cost savings opportunities, etc.

Re: Ask HN: What do you talk about in 1-on-1s with your managers?

#12
I find half an hour every fortnight is a better schedule, and the quality of the meeting has depended on the quality of the manager and my willingness to prepare and engage. When done right, it's a place to talk about my goals within the company and in my career, how they're going, how the company can help me, etc. It's a great place to show what you're interested in and what you want to do in the future, because hopefully the manager has a broader idea of what's happening at the company/team on a higher level, so they can talk to people to help you get where you want to be. E.g. want to talk at conferences? Your manager can ask around at their meetings, maybe someone knows someone looking to get company representation at a conference. Want to use and improve your architectural skills? Maybe there's a round of cross-Team engineers discussing and sharing tips regularly.

Re: Ask HN: What do you talk about in 1-on-1s with your managers?

#13
I would agree with what people wrote:

1. What you're working on 2. Blockers (or how the manager can help with those) 3. Anything going on with you which could impact your work

In my current role, people are highly autonomous. 1:1 being held once every 2 weeks, or once a month is enough. Once a week is way too high touch.

Re: Ask HN: What do you talk about in 1-on-1s with your managers?

#15
I tend to avoid focusing on status updates on my WIP. In my 1:1s, I want to talk about me.

1. What do I need to do to get my next promotion/payrise, or how do I get onto the next bit of interesting work? Even if I'm happy with my current work and compensation, I use this as an opportunity to constantly make clear what my personal objectives are.

2. How well am I tracking against Q1?

3. How do you suggest I improve on Q2? If I have things I know are pushing down on Q2, I will ask for help.

In addition, I tend to use them for managing upwards - setting expectations, and making clear where I need something from my manager.

Re: Ask HN: What do you talk about in 1-on-1s with your managers?

#17

1. Here's what I'm working on. (Is this a good use of my time?) 2. Here are my blockers. (Can you help clear the way so I can do my work?) 3. Here's what's going on in my life (relationship building, context for manager to understand your work and capacity)

Aren't the first two covered at standup every day?

Re: Ask HN: What do you talk about in 1-on-1s with your managers?

#19
post #7

These have always been an enormous waste of time from my perspective. They only serve to make a manager feel like they know what everyone is doing, all the time. Anything process-wise should be handled through scrum. Anything personal can be handled with ad-hoc 1-on-1 meetings as needed, but should be pretty rare. 1-on-1s for process really do harm to transparency and accountability. If I had a nickel for every time…

DO you consider yourself an introvert by any chance?

Re: Ask HN: What do you talk about in 1-on-1s with your managers?

#20
I've usually had 30 minutes scheduled for these (weekly or biweekly), both as manager and employee. >50% of the time it's "we talked about everything already on signal yesterday, so we can skip it this week? yes" but sometimes it's useful for discussing a new product idea or addressing a specific roadblock (resources from other departments, usually, or sometimes concerns re: a vendor). I tend to do things more async but unscheduled, though -- send an email or a message which doesn't require immediate followup but sometime in the next ~week.

I think 30m biweekly is more optimal. If I ever had an actually junior direct report I'd be more inclined to be more formal, available, or frequent on these, or someone who I knew to have difficulty raising issues in other settings. I've never actually had a 0-2 year experience direct report, though, as I actively try to avoid direct reports generally but particularly early-career people.

I find AARs on projects (successful and unsuccessful) to be far more useful than most of the cargo-cult-management tools. Also, having dashboards on status of various things and current blockers kept updated, ideally automatically through tools used in the workflow itself, and a clear directory of who to contact for what component.

Post reply on HN