Data Platform Engineering/Meeting norms

These are agreements and guidelines on how we conduct meetings.
== Before meetings ==
# Set working hours in Google Calendar 
# Keep your calendar up to date with your availability
# It is highly recommended that you activate reminders 10/5/1 minutes ahead of the meeting
# Be mindful of time zones when scheduling meetings
# For every meeting, confirm attendance on Google Calendar. If you have a last minute setback, let the team know you won’t attend on Google Calendar
# When organizing a meeting, mark guests that are optional and the ones that are mandatory. 
# Write in the description the meeting objectives and share the agenda
# Attach a notes document to the meeting when appropriate. Store it in the team meeting notes folder. Create subfolders as needed. 
# Make sure all the documents you will share are accessible to all participants
# Communicate who is the meeting host/driver/facilitator
# If you are not able to make the meeting where your presence is needed rather than reschedule, consider providing your input ahead of the meeting with questions, considerations and then following up afterward
# If you are not able to make the meeting, when applicable, consider sending a delegate
# Slack Huddle is an acceptable alternative to Google Meet especially for impromptu work sessions
== During meetings ==
# Show respect for people’s time
# Join on time. Meetings will start at :03’ and end at (end - 5)
# Consider if the meeting should  be recorded and be shared with others who are not in attendance
# Communicate:
## Meeting objectives
## The agenda and time allotted to each agenda item
## Who will be in charge of taking notes
## Clear actions, owners, and timelines at the end of each meeting
# If you feel like you are not fully needed, don’t attend the meeting. Avoid multitasking
# Don’t be afraid to speak about uncomfortable topics. 
# Take notes to record important points and share with others who were not able to attend meeting
# Assign action items to the right parties in the google document
# Consider various community perspectives
# Help maximize inclusion
## Use simple, accessible language
## When you speak, just make 1 point
## Leave room for everyone to speak; each person should speak “1/n th” of the time 
## Actively solicit input from those who had not had an opportunity to speak
# When speaking, be mindful of the audience and make sure you provide sufficient context and err on the side of over-explaining. Ask the meeting participants if they have enough context.
# If you do not understand something in the meeting that is preventing you from following the conversation, ask the question then and there or post your question in chat. The speaker should make the best attempt to provide a response. If there are meeting time constraints to provide the full information, follow up after the meeting with additional information.
# For chat norms see Suggestions for parallel chat in meetings. Additionally:
## Copy links shared and important points to the notes document
## Avoid parallel conversations that take focus from the main conversation and topic discussed
# Raise a hand when you wish to take turns to talk. If a person is talking at the time, they should finish their thought before handing it back to the facilitator or calling on the next person in the queue.
## If you have something you want to respond to directly or urgently use “o//” in the chat.
# The facilitator should keep track of time.
## Ensure that we are progressing through the agenda topics in a timely way.Provide appropriate 5/2/1 minute time checks to keep the conversation on track and in line with the agenda.
## If more time is needed to discuss something, explicitly agree to drop things from the agenda and how to follow up on the remaining items.  
## Leave at least 5 minutes at the end to summarize important take-aways and discuss next steps
# If you are taking notes but are not able to follow the gist of the conversation given the unfamiliarity with the technical area or domain, ask one of the team members to take over to provide the accurate context/terminology/acronyms
# Everyone in the meeting, and especially the facilitator and host, should feel free to call out when the meeting is going off topic, and suggest that the topic be parked if it is not directly contributing to the discussion.
== After the meeting ==
# Share the notes document others who were not able to attend meeting
# When appropriate communicate any relevant meeting take-aways to the team in Slack and solicit asynchronous feedback where needed