02 Cohort Call Digest [ 2023-SWRCB ]

[AHolder1]

Hi Everyone,

Thanks for a great second session this morning. Shout out to Devan (@DevanBurke) and Tina (@tures23) for instructing for the first time and teaching us about team culture, psychological safety, and diving deeper into the Pathway doc! Below is a light digest of Call 2, including a reminder for your Seaside Chat and additional Co-Working time before our Call 3. Looking forward to seeing you then!

Have a good week,
Anna, Devan, and Tina

Digest: Cohort Call 2 [ 2023-SWRCB ]
Cohort SharePoint Folder - contains agendas, slides, recordings and the Pathway template
Cohort GitHub Repository
Cohort Webpage
Water Boards' Openscapes Teams Channel - connect with all Openscapse Champions cohorts at the Water Board

Goals: We discussed team culture and took a deeper dive into the Pathway.

Task for next time:

1. ​Have a Seaside Chat and continue working on your Pathway:

• Focus on where your team is “Now” - Think about where you are now in your workflow(s)
• Pathways Sheet (File > Make a copy)

2. Accept our invite to join a team within the Openscapes Organization:

• You will receive an email from GitHub asking you to join our cohort GitHub in the Openscapes GitHub organization. Make sure you accept before the next Cohort Call!

Upcoming OPTIONAL Cohort Co-working Session: Thur., Sep. 7th, 2:00-3:00 pm.
This is a time to come work on your own things, but also be able to talk things through and screenshare to get help from others.

Slide Decks:

• Team culture & Psychological safety
• Intro to the Pathway & Seaside Chats

A few lines from shared notes in the Agenda doc:
Some things folks have done or seen on a team to make it psychologically safe include:

• Building a culture of being ok to fail. +1
• Be the one to ask “stupid” questions 😊 - chances are someone else has the same one! +1+1 +1
• A person in a leadership position admitting they made a mistake, and focusing on how to remedy the situation and asking for advice on moving forward +1+1 +100 +1
• When someone on the team (particularly someone in a leadership role) recognizes what is in your control and what isn’t in your control +1+1 +1

Many teams are on their way to developing their pathways and have asked (and answered!) the first big questions:

• Where will we store the Pathway so that we can all have access to edit over time! +1 +1 +1+1
• What is the scope of our Pathway
• Do we want different tabs for each project/program?