Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

Thank you so much for offering such great insights. I love the general flair of keeping the process light. I do have a couple more questions:

a) When does your google doc go "stale"? (The next 1:1? At the end of the year? When you stop having 1:1s with that person?)

b) In your approach, are there things you don't want to share but want to make note of (performance related notes, future ideas etc)? What do you do in these cases to stay organized?

c) If you are managing a team of several people over large time periods, that's a lot of google documents. Do you have the need to stay organized over time? How do you do it?



Not GP, but similar approach.

a) when the team changes, I just move the doc to an archive folder. If they leave the company, Iā€˜d likely delete. I actually had my manager change back to my first over time and we just continued the doc

b) Trying to be as transparent as possible, and keep everything in the doc. For performance reviews / career progression, linking from the 1:1 doc.

c) seems like you think a Google doc per 1:1? I have one doc per person. Seems pretty easy to manage, unless you manage dozens of people. I have one folder with all current reports and one archive folder with former reports

For more info have a look at our handbook: https://about.gitlab.com/handbook/leadership/1-1/


Thank you for all your answers - the handbook link is super useful!




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: