Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

02 Cohort Call Digest [ 2024-SWRCB ] #3

Open
AHolder1 opened this issue Aug 29, 2024 · 0 comments
Open

02 Cohort Call Digest [ 2024-SWRCB ] #3

AHolder1 opened this issue Aug 29, 2024 · 0 comments
Assignees

Comments

@AHolder1
Copy link
Collaborator

AHolder1 commented Aug 29, 2024

Hi Everyone,

Thanks for a great second session last Wednesday. Thank you to Tina and Anna for 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,

Elena & the rest of the Mentor + Instruction Team

Digest: Cohort Call 2 [ 2024-SWRCB ]

Cohort OneDrive Folder - contains agendas, slides, recordings and the Pathway template
Cohort Webpage
Link to Pathway Template

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

Task to complete before next time:

1. Have a Seaside Chat & continue working on your Pathway

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

  • You should have received an invite on Friday morning (8/23) from GitHub asking you to join our cohort GitHub Repository in the Openscapes GitHub organization. Make sure you accept before the next Cohort Call!

Upcoming OPTIONAL Cohort Co-working Session: Wed., August 28th, 10:30-11:30 am.

  • 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:

A few lines from shared notes in the Agenda doc:

Team Culture

  • Pac-Man rule! Stand in a way with room for others to join your group

pacman

  • Psychological safety doesn’t mean there will be NO conflict or that there will be no accountability (high safety + high accountability = more creativity)
  • Innovation is inherently risky, and therefore completely integrated with and reliant upon psychological safety

Examples of fostering psychological safety:

  • Team Chat where anyone can ask questions +1+1+1+1+1
  • Leadership admitting mistakes +1+1 +1 +1
  • Creating an environment where it is actively encouraged to acknowledge limitations and celebrate failure as a learning opportunity:

awesomefail

Pathway discussion

  • Refer back to the shared notes for some great tips & tricks for streamlining the Pathway and optimizing its utility for your team!

Some wholesome content from America’s favorite Uncle, the one and only Snoop Dogg:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants