From 401d96362aa2c15617716d260e81a5af6a66d198 Mon Sep 17 00:00:00 2001 From: Matt Fisher Date: Tue, 6 Feb 2024 17:21:43 -0700 Subject: [PATCH] Flesh out index page draft --- README.md | 122 ---------------------------------- _notes/2024-01-11_meeting.md | 123 +++++++++++++++++++++++++++++++++++ _quarto.yml | 3 +- about.md | 5 -- index.md | 65 +++++++++++++++++- 5 files changed, 186 insertions(+), 132 deletions(-) create mode 100644 _notes/2024-01-11_meeting.md delete mode 100644 about.md diff --git a/README.md b/README.md index 33711df..73b9ee1 100644 --- a/README.md +++ b/README.md @@ -1,123 +1 @@ # Seaside chat: Psychological safety - -_Planning notes on a 2024-01-11 meeting with Sunny Hospital, Stefanie Butland, Matt -Fisher._ - - -## What is a seaside chat? - -The idea is encouraging a working team to have a regularly scheduled -session without an agenda but it's about conversations. Deciding what you want to learn -as a team, for example. - -The chat would start with a topic, and participants would lead. - -Reminds Matt of -[Open Space Technology](https://peggyholman.com/papers/articles/good-work-for-2100-colombian-street-kids/)! - - -## Defensiveness / psychological safety - -People would like to share but uncomfortable, fear of criticism, that's what they're -used to from their grad program, etc. - -That environment is TRAUMATIC. - -Our goal is to help open the topic, help people be more comfortable, make it easier to -talk about. - -Good _and_ bad interactions can be contagious / self-reinforcing. - -Stefanie: - -* Could be monthly repeated forum to share challenges and positive experiences, provide - long-term safe supportive space -* Avoid solution engineering! e.g. "You could have said" or "you should do" - - -## Sunny and my experiences working on Proj Forge from both sides are inspiring to share! - -* Sunny learned something from someone with a different perspective. - * GitHub Actions was new, shared it with colleagues. -* Matt received energy from Sunny's participation and warm reception of an idea. - * In another community, I felt challenged, discouraged, demotivated about the - response to the same idea. I'm not saying my idea was good and deserved a positive - response, but: both positive and negative responses are very inexpensive to give, - but the outcome of a negative response can be very expensive. "Open science is kind - science" (Andy Barrett) - - -## Structure - -1 hour - -Aside from basic structure setting the stage for the discussion, no leading / no -pre-defined speakers. Any speaking by facilitators should serve the purpose of enabling -group discussion, e.g. sharing an anecdote as an ice-breaker (more below). - -Topic is set in advance: "Psychological safety" - - -### Potential sub-topics from: - -* how to give and receive criticism -* trauma and how it effects our future decisions -* how to create a safe environment -* empowerment -* cultural understanding -* best practices to cultivate healthy scientific collaboration - - -People who propose topics briefly share why they think it's a good topic. - - -### Schedule - -If we have >8 people, let's vote with a tool like slido or menti - -Define psychological safety. - -Call out the current culture has psychological safety problems. - - -#### 5 minutes submitting topics - -What does psychological safety mean to you? E.g. - -* Constructive criticism -* Empowerment - -Some things about psychological safety that are important to you or have happened to you - - -How do you handle situations that make you unsafe? - - -#### 5 minutes choosing topics / voting - -#### Sharing experiences / ice breaker - -To set the tone, ask if anyone would like to share a psychological safety experience or -reasons they thing psychological safety is important. If not, we have some stories ready -to go. - - -##### Sunny & Matt's negative and positive experiences - -_TODO_: Think about how to share negative experiences in a way that isn't too shamey - -E.g. Sometimes our projects aren't well-received by our peers, and that can cause us to -"drop" ideas we would otherwise pursue. - - -#### Let go!!! - -Let the participants lead the conversation from here. - - -## TODO - -* Create a private GitHub repository to workshop our plan -* Figure out how to set a time? Ask Stefanie? Use when2meet to poll people? -* Develop an invitation that clearly describes what to expect from this meeting, i.e. - not a lecture, a safe discussion environment, etc. diff --git a/_notes/2024-01-11_meeting.md b/_notes/2024-01-11_meeting.md new file mode 100644 index 0000000..33711df --- /dev/null +++ b/_notes/2024-01-11_meeting.md @@ -0,0 +1,123 @@ +# Seaside chat: Psychological safety + +_Planning notes on a 2024-01-11 meeting with Sunny Hospital, Stefanie Butland, Matt +Fisher._ + + +## What is a seaside chat? + +The idea is encouraging a working team to have a regularly scheduled +session without an agenda but it's about conversations. Deciding what you want to learn +as a team, for example. + +The chat would start with a topic, and participants would lead. + +Reminds Matt of +[Open Space Technology](https://peggyholman.com/papers/articles/good-work-for-2100-colombian-street-kids/)! + + +## Defensiveness / psychological safety + +People would like to share but uncomfortable, fear of criticism, that's what they're +used to from their grad program, etc. + +That environment is TRAUMATIC. + +Our goal is to help open the topic, help people be more comfortable, make it easier to +talk about. + +Good _and_ bad interactions can be contagious / self-reinforcing. + +Stefanie: + +* Could be monthly repeated forum to share challenges and positive experiences, provide + long-term safe supportive space +* Avoid solution engineering! e.g. "You could have said" or "you should do" + + +## Sunny and my experiences working on Proj Forge from both sides are inspiring to share! + +* Sunny learned something from someone with a different perspective. + * GitHub Actions was new, shared it with colleagues. +* Matt received energy from Sunny's participation and warm reception of an idea. + * In another community, I felt challenged, discouraged, demotivated about the + response to the same idea. I'm not saying my idea was good and deserved a positive + response, but: both positive and negative responses are very inexpensive to give, + but the outcome of a negative response can be very expensive. "Open science is kind + science" (Andy Barrett) + + +## Structure + +1 hour + +Aside from basic structure setting the stage for the discussion, no leading / no +pre-defined speakers. Any speaking by facilitators should serve the purpose of enabling +group discussion, e.g. sharing an anecdote as an ice-breaker (more below). + +Topic is set in advance: "Psychological safety" + + +### Potential sub-topics from: + +* how to give and receive criticism +* trauma and how it effects our future decisions +* how to create a safe environment +* empowerment +* cultural understanding +* best practices to cultivate healthy scientific collaboration + + +People who propose topics briefly share why they think it's a good topic. + + +### Schedule + +If we have >8 people, let's vote with a tool like slido or menti + +Define psychological safety. + +Call out the current culture has psychological safety problems. + + +#### 5 minutes submitting topics + +What does psychological safety mean to you? E.g. + +* Constructive criticism +* Empowerment + +Some things about psychological safety that are important to you or have happened to you + + +How do you handle situations that make you unsafe? + + +#### 5 minutes choosing topics / voting + +#### Sharing experiences / ice breaker + +To set the tone, ask if anyone would like to share a psychological safety experience or +reasons they thing psychological safety is important. If not, we have some stories ready +to go. + + +##### Sunny & Matt's negative and positive experiences + +_TODO_: Think about how to share negative experiences in a way that isn't too shamey + +E.g. Sometimes our projects aren't well-received by our peers, and that can cause us to +"drop" ideas we would otherwise pursue. + + +#### Let go!!! + +Let the participants lead the conversation from here. + + +## TODO + +* Create a private GitHub repository to workshop our plan +* Figure out how to set a time? Ask Stefanie? Use when2meet to poll people? +* Develop an invitation that clearly describes what to expect from this meeting, i.e. + not a lecture, a safe discussion environment, etc. diff --git a/_quarto.yml b/_quarto.yml index 06342f6..c568132 100644 --- a/_quarto.yml +++ b/_quarto.yml @@ -7,8 +7,7 @@ website: navbar: left: - - text: "About" - href: "about.md" + - text: "Placeholder" format: diff --git a/about.md b/about.md deleted file mode 100644 index 07c5e7f..0000000 --- a/about.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "About" ---- - -About this site diff --git a/index.md b/index.md index 202a306..5326ce4 100644 --- a/index.md +++ b/index.md @@ -1,7 +1,66 @@ --- -title: "seaside-chat-psychological-safety" +title: "Seaside chats: Psychological safety" --- -This is a Quarto website. +## What is a seaside chat? -To learn more about Quarto websites visit . +The idea is encouraging a community to have a regularly scheduled session for +safe, self-facilitated discussion with a limited agenda. +These discussions often focus on technical, organizational, or interpersonal challenges. +For example, exploring challenges with data visualization, open science, or psychological safety. + +The chat would start with a topic, and participants would lead with facilitators playing +a role of ensuring the space is safe and that diverse voices are heard rather than +leading the discussion. + + +### Structure + +* Check-in / icebreaker (word cloud / survey / prompt): 5 minutes +* Discussion on experiences / challenges: 25 minutes +* Discussion on what we can do about it: 25 minutes +* Wrap-up / prep next meeting: 5 minutes + + +#### Discussion format + +* Gather ideas people want to talk about in some shared space, e.g. Google Doc, + Etherpad, Hedgedoc. Ideally, our tool can also allow voting. +* Anyone can start talking about something +* Use "raise hand" when others are talking to request to speak next +* When discussion slows down, refer to the shared space with ideas to find the next + topic. + + +## What is psychological safety? + +:::{.callout-note} +TODO: Add some reference material, maybe a research paper, about what psychological +safety is. Catherine Hicks might have one that's useful, but I think most of her +research is software development focused. +::: + +Psychological safety is the degree to which people feel comfortable speaking about +sensitive subjects without fear of negative consequences. + +For example, many of us have experienced traumatic hyper-critical environments +(academia, ...) that have resulted in low levels of psychological safety. Often, we feel +uncomfortable or self-conscious speaking up because we're worried about how people will +respond. + +Our goal is to help people become more comfortable sharing their work by discussing +psychological safety, our experiences, and how we can all do better. + + +## What can we do about it? + +Good _and_ bad interactions can be self-reinforcing or contagious. Our actions can +establish virtuous cycles. Let's talk about what we want to see. + + +## Cadence + +:::{.callout-note} +TODO: We haven't yet decided on a cadence. Should we meet monthly to provide a long-term +supportive space? +:::