Source for Meltano's public handbook (https://handbook.meltano.com/) and public issue tracker for process and policy proposals that will be documented there.
MIT License
3
stars
4
forks
source link
Protocols for calendar invites outside of working hours (and/or when there's a known conflict) #10
Originally created by @aaronsteers on 2021-10-11 18:06:13
As we grow, we're just naturally going to have more meetings. And seeing as how we are a company which is geographically dispersed, it's going to be common for meetings to happen outside of one or more team member's working hours and/or holiday schedule. In effort to promote our values of Community and Empathy, I'd like to propose some protocols for how we can handle these situations. If agreed, I can submit an MR to update the handbook. (Not sure where though and would appreciate input if anyone has an idea.)
I propose something like the following:
Requesting time from other team members
While Meltano values asynchronous and inclusive conversations whereever possible, there are times when we may still want to schedule time with each other. This applies when scheduling time with external partners or vendors, when scheduling 1:1s, or when setting up time to discuss critical decisions.
Whenever requesting another team member's time, but especially if you can see that they are busy or out of their normal working hours, the person requesting the time should take responsibility for communicating clearly and proactively on the following points:
Specify if the meeting will be recorded or can be recorded.
Clearly note on the invite who is "required" vs "optional".
For anyone who is in the "required" list and is marked not available (due to time off, working hours, or other conflicts), it is the requestor's responsibility to initiate the conversation: "I see I am inviting you at a time where you are already blocked. Can you attend?" along with the following important details in the body of the invite, or in a slack direct message:
Provide relevant context to why the meeting is being booked over a blocked time. (Example: "this was the only time I could find before I leave for vacation", or "this was the best time I could find given everyone's schedule", or "because Company X is in Alaska, we had to schedule a late evening meeting")
Let the person know if it's okay for them to not attend if they are unable.
If applicable, let the person know what will happen if the person is not able to attend? (Could the meeting get rescheduled or would it need to be canceled? Will folks meet anyway, will a recording be added, etc.)
If the person invited does not receive this context, because calendars weren't up to date, or because the requestor did not see the conflict, the person with the conflict likely will not have proper information on whether they need to change their plans - for instance: changing their wakeup time, hiring a babysitter, canceling other meetings, etc. In that case, the person with the conflict can simply inform the organizer that the time is blocked, and request "context and guidance" given the identified conflict. This "context and guidance" request can be inferred to be shorthand for all of the above information in point 3 above.
MeltyBot
commented
2 years ago
Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/11
Originally created by @aaronsteers on 2021-10-11 18:06:13
As we grow, we're just naturally going to have more meetings. And seeing as how we are a company which is geographically dispersed, it's going to be common for meetings to happen outside of one or more team member's working hours and/or holiday schedule. In effort to promote our values of Community and Empathy, I'd like to propose some protocols for how we can handle these situations. If agreed, I can submit an MR to update the handbook. (Not sure where though and would appreciate input if anyone has an idea.)
I propose something like the following: