Team Contract

Communication

• Keep at least once a month full team meetings
• General updates on program areas
• Updates about org in general
• Takes notes & rotate who holds this role
• Team building exercises/get to know you
• Ex. likes the Miro board
• Problem solving
• Weekly slack check ins for staff
• Use slack as a place for brainstorming
• Intentionally keep lines of communication open - here are the notes, are there things that you'd like to add?
• More opportunity to talk about Civic Science — or what they are working on / special interests — more of a social meeting, things they love.
• Could do a formal work focused one, and one outside of work
• For work based one — have them be open to all people — record them. Ask for input/questions
• Slack:
• Overwhelmed
• There are 1,000 people in our slack but they aren't actually participating
• Who's there, how they use slack.
• Written updates
• Project based meetings
• Discussion based is helpful
• If it's just an update, then written is good
• How do you make sure people have the info they need participate
• Ex. read the written updates; do the NASA course before participating
• Tech meeting - review the Asana board
• Weekly Wellcome meetings
• If Court has questions, do in a DM — and then it's expected to post in the public channel.
• Present on work as it moves forward
• Ex. Jenna's plan for Climatematch curriculum updates.

• Bring this back

• What are their goals/priorities
• Big changes in the board
• Summary of every board meeting
• Secretary provides update after each Board meeting

• What are the exceptions

• Tools: Asana/Slack/Slite/Airtable

• Threads
• Bullet points / bold / clear CTA
• Clickable
• When to use @ channel —
• Only when it's relevant to everyone in that channel
• Individual / @ channel when people want immediate response
• If you reschedule a meeting w/ short notice ping the person
• Keep work calendar up to date (w/ OOO too)
• Week or more let the team know you'll be gone
• Make sure your calendar if updated for the next two ish weeks
• Message in Slack if you need something looked at/reviewed
• (Slite/Asana/Google Drive notifications can get missed)

• Private, but update will be shared publicly to close knowledge gap
• Prompt
• How to fix this / future oriented / learning oriented

• Monthly meeting committed to share kudos
• Can also do this for vols — can bring back form // post in slack
• Public is good

How do we work to avoid stressors/anxiety triggers:

• What data do we have
• What data do we need?
• How will we collect the needed data?
• How do we move forward if we do not have/cannot get data?

• Individual goals >> Org Goals
• Meetings for both, clear org goals
• Think in advance
• Adoption of new projects need to come w/ assessment of future work
• Explicit acknowledgment of what the future looks like

• At least annually/(more often) look at induvial role descriptions. Update them to be accurate.
• Share in a group meeting

• Be accountable for your role
• Acknowledge positionality and power
• Let us know when you mess up, and we'll find a solution

Commitments to Each Other

• Court: Share about board meetings w/ staff and broader community
• Leanna: Come out of her bubble, share more about what's she's doing
• Konstantine: Thinking more before he speaks

What you hope for from the team:

• Share more together about what we're working on
• Feel free to reach out!!!