Digest: Cohort Call 2 [ 2022-SWRCB ]

[DevanBurke]

Hi Everyone,

Thanks for a great second session last Wednesday. Thank you to Ileana Fenwick for guest teaching about Data Strategies for Future Us and open dialogue during the Q&A! Below is a light digest of Call 2, including a reminder for your Seaside Chat and additional Co-Working time before our Call 3 on Friday, September 14th. Looking forward to seeing you then!

Have a good week,
Devan, Tina, Corey, and Anna

Digest: Cohort Call 2 [ 2022-SWRCB ]

CohortCall Google folder - contains video recordings and completed agendas
openscapes.github.io/2022-swrcb - Cohort webpage
MS Team Channel - Water Boards Teams Channel

• Note that links to recordings are posted here, too!

Slack -- Use this link to join the Openscapes Slack Organization so that you can connect further with the Openscapes Community. If you decide to join, please introduce yourselves in the welcome channel! The link expires on September 18th, so if you wish to join after this date let Corey or Anna know.

Goals: We discussed team culture and data strategies for future us, with special guest Ileana Fenwick, PhD Candidate, Nye Lab, University of North Carolina

Task for next time:

1. Have a Seaside Chat with your broader research group
2. Continue your Pathway (focus on Now: your Trailhead)

• Pathways spreadsheet (Make a copy in the PathwayShare Folder via File > Make a copy, if this does not work for you please email Anna)
• Note: teams can approach this differently. Maybe the team has one pathway or multiple.
• Consider adopting (or creating/iterating) a Code of Conduct for your research group, posting publicly (on your website, on GitHub, etc.)
• Onboarding/how-we-work examples
• Co-working: (optional). This is a time to come work on your own data science things, but also be able to talk things through and screenshare to get help from others. Upcoming Co-Working Session: Friday, September 9th, 10:00am - 11:00am.

Slide Decks:
These are also available publicly from openscapes.org/series

• Team Culture & Psychological Safety
• Data strategies for Future Us - Ileana Fenwick, Nye Quantitative Fisheries Ecology Lab
• Code of Conduct -- we did not review this during the call, but these might be a helpful place to start for developing your own code of conduct, potentially during a seaside chat.

A few lines from shared notes in the Agenda doc:
There were lots of positive Seaside Chat experiences!

• Folks were: inspired and getting to know one another’s workflows, discussing and scoping where to go from here. Teams are also focusing on identifying where people compliment each other’s skill sets!
• Many want to dive deeper/learn/figure out one anothers skills levels and commonalities in workflows (i.e., some Teams are using one Pathways doc while others are creating multiple for each unit within the Team).

Some things folks have done or seen on a team to make it psychologically safe include:

• Having leaders that are able to say “I’m wrong” or “I messed up/made a mistake” and show us that that is ok and we’ll work together to “fix it” +1+1+1+1+1+1
• Great to have the term “psychological safety” to describe something I’ve felt but can’t put into words +1+1
• Supervisors asking staff how they want to grow their career and where they want to go on their path +1+1+1
• Really cool when a member throws out an idea which might not seem relevant but was accepted by the team to discuss +1+1+1
• Leaders/Managers supporting learning through trial and error +1+1+1
• Given the safe space to use a new product/idea (against the norm) and was given the time to make it happen +1
  Ileana's Data strategies for Future Us presentation and discussion resonated with the group:
• I loved this presentation! Thank you so much Ileana! "slowing down to speed up", another great quote! +1
• I hear the term “tidy data” used a lot but we don’t spend a lot of time talking about what is meant by tidying our data, this was a great reminder and re-grounding +1
• Knowing these tips earlier in my career would have prevented many data headaches and made data much easier to share+1 +1
• don't leave any cells empty! Yes!