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

My experience has been that engineers tend to resent this kind of stuff. Many of them would consider it 'fluff' that essentially distracts them from important work.

I have one on one meetings with my team, but I don't force a lot of structure on it. If it takes 2 minutes fine. If it takes an hour thats fine too. If nobody wants to do it during crunch time then we don't do it.

Not saying one on ones are not important, but given a certain kind of team and a certain kind of employee they are not necessarily required or a productive use of time.




I'd still say you need to book at least 30 minutes. If your staff don't want/need more than 2 minutes, then fine. The important thing is telling them "this time slot I'm all yours".




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: