This page describes how Sid formats his 1-1 agendas. If you are new to 1-1s or not sure how to make your previous experience with 1-1s work in GitLab's culture, this can be a great starting place for you to learn. However, remember that 1-1s are private meetings between a manager and their report, so consistency is secondary to effectiveness - please make sure to find a format that works for you and your team.
Give your agenda document four headers:
Please see our guide on giving feedback.
ISO DATE(example: 2017-05-21 or 2017-05) - indicating when this item will be discussed next
RELEASE NUMBER(example: 9.4 or 9.5) - alternative to
ISO DATEto indicate when this item will be discussed next
TODO- report needs to set date of when this will be completed or just do the task, if we should discuss them report changes them to
DOTO- manager needs to do something, with this a (case sensitive) search for '
DO' finds all
DISCUSS- cover in the next 1-1 meeting
REVIEW- there is a Merge Request (MR) or document that can be approved, the MR should not be a Work In Progress (WIP)
HELP- if you need help with anything.
FYI- informational, can be removed outside of the meeting by the person why did not put it on the agenda.
DONE- to be removed by the person who put it on the agenda, only set this if any MR has been merged
MOVE- if you want to move it outside of the agenda, for example an issue tracker.
DUPLICATE- An item that is an outdated duplicate of another item on the agenda. To be removed similar to items marked as
WONT- if you think this is no longer something that should be done.
WHY- if you get the suggestion but wonder why this is important and what the problem is.
THINK- if the person who did not put it on the agenda wants time to think about it and discuss it next meeting.
FEEDBACK- this is feedback about your performance (also means that all the other items are not performance feedback)
THANKS- mostly used by the manager to praise the report, these should not require a follow-up action. There is a tendency to focus on issues and challenges. Do not forget to recognize accomplishments and success.
SORRY- if you want to say sorry for something.
DONE. The 1-1 is one list that is continually modified. It is not a meeting agenda that is duplicated every week under a new date.
=>to indicate a response/followup to an agenda item and prefix with your name. One example is at the bottom of this page and one is given here:
DISCUSSSid: Should we look into a collaboration with Walmart? => Kate: I think so, I created https://gitlab.com/gitlab-org/gitlab-ce/issues/101
6. 2017-07 Sid: Kubernetes wishlist email => Spoke with Job, he'll create the issues => Eliran to stay involved 7. Sid: Do a webinar with all cloud partners, all container schedulers, all config management systems. => Eliran: Dimitrie might be interested in helping. Get the webinar without doing a lot of integration. => Eliran: Starting with Puppet, Dimitrie said he didn't do any dev work for the i2p demo so I am not sure he will be able to do the dev work required here. => Sid: Goal is not to have dev work. Just combine their demo with our i2p.