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 these headers:
An important part of career development is feedback, but that’s not all. It also involves training. Please see our guide on giving career development.
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.
THINK- if the person who did not put it on the agenda wants time to think about it and discuss it next meeting.
FYI- informational, can be removed outside of the meeting by the person who did not put it on the agenda (the audience for the FYI).
DONE- to be removed by the person who put it on the agenda, only set after any related MR has been merged
MOVE- if you want to move it outside of the agenda, for example an issue tracker, removal by the person who put it on the agenda
DUPLICATE- An item that is an outdated duplicate of another item on the agenda, removal by the person who put it on the agenda.
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.
IDEA- if the person who put it on the agenda is offering a suggestion for consideration and possible dismissal rather than as a directive.
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.
FEEDBACK- this is feedback about your performance (also means that all the other items are not performance feedback)
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. For example:
DISCUSSSid: Should we look into a collaboration with Walmart? => Kate: I think so, I created https://gitlab.com/gitlab-org/gitlab-ce/issues/101
We move through the agenda top to bottom by header but bottom to top within those headers. For example, the very first discussion item in the call should be the last item under High Performance.
Consider this example agenda between a manager (Martina) and her direct report (Andre):