We’re now mid-way through the first year of the AAAS Community Engagement Fellows Program (CEFP), funded by the Alfred P. Sloan Foundation. The first cohort of Fellows is made up of 17 scientific community managers working with a diverse range of scientific communities. As they continue to develop their community engagement skills and apply some of the ideas and strategies from their training, the Fellows will report back on the Trellis blog, sharing their challenges, discoveries, and insights. Today, Fellow Stefanie Butland follows up on her earlier pieces about welcoming community members and running an unconference with more specific advice.
Posted by Stefanie Butland, Community Manager at rOpenSci, – Open Tools for Open Research
I’ve raved about the value of extending a personalized welcome to new community members and I recently shared six tips for running a successful hackathon-flavoured unconference. Building on these, I’d like to share the specific approach and (free!) tools I used to help prepare new rOpenSci community members to be productive at our unconference. My approach was inspired directly by our AAAS CEFP training in community engagement. Specifically, 1) one mentor said that the most successful conference they ever ran involved having one-to-one meetings with all participants prior to the event, and 2) prior to our in-person AAAS-CEFP training, we completed an intake questionnaire that forced us to consider things like “what do you hope to get out of this” and “what do you hope to contribute”.
A challenge of this year’s unconference was the fact that we were inviting 70 people to participate. As a rule, one third of the crowd will have participated in one of our previous unconferences and two-thirds would be first-time participants. With only two days together, these people need to quickly self-sort into project groups and get working.
So I sent this email to 45 first-time participants:
Arranging meetings is one of my least favorite activities, but the free Calendly tool made this process relatively painless. When a person clicks on the calendar link in the email above, it reveals only times that I am available in my Google Calendar, the time slot they choose shows up in my calendar, and I receive a confirmation email indicating who booked a meeting with me. In my busiest week, I had 19 meetings, but that meant the bulk of them were done!
To make the meeting time most effective I followed CEFP program director Lou Woodley’s model for onboarding our AAAS CEFP cohort by sending a set of questions to be answered in advance. I took the model to the next level by creating a free Google Form questionnaire so that all answers were automatically collected and could be viewed per individual or collectively, and automatically exported to a spreadsheet.
1. List three things you hope to get from the unconference
e.g., “connect with people working in a similar domain”, “learn about best practices in data science with R” , or “develop a new package that does X”
2. List three things you hope to contribute to the unconference
e.g. “expertise or experience in X”, “mentoring skills”, “write all the docs!”
3. Have you had any previous interactions with the rOpenSci community?
e.g. “I read the rOpenSci blog”, or “I submitted software for rOpenSci open peer review”
4. Do you have any concerns about your readiness to participate?
e.g. “I’ve never developed an R package” or “How do I decide what project to work on?”
5. Would you be interested in writing a blog post about your unconference project or your unconference experience?
6. Do you have a preferred working style or anything you would like to let us know about how you work best?
e.g. “I’m an introvert who likes to take my lunch alone sometimes to recover from group activities – it doesn’t mean I’m not having fun.” or “I know I have a tendency to dominate in group discussions – it’s totally fine to ask me to step back and let others contribute. I won’t be offended.”
These questions encouraged participants to reflect in advance. The example answer snippets we provided gave them ideas from which to seed their answers and in some cases gave them permission to show some vulnerability. Individual’s answers gave me cues for things to address in our chat and freed both of us to spend our time talking about the most important issues.
The answers to the question “List three things you hope to get from the unconf” were so heartening:
Beautiful, but in a different way, were answers to the question, “Do you have any concerns about your readiness to participate?”. People said things like: “I’m somewhat nervous about the whole thing, probably impostor syndrome is somewhat in play”; “Overwhelmed at the number of projects already, and feeling seriously outclassed by all the geniuses present”; “It’s intimidating for sure to be around all the awesome people I see on Twitter doing awesome things, and I’m afraid I won’t be able to contribute as much or as well as them”. These responses prompted me to reassure people that they were 100% qualified to participate, and opened an opportunity to listen to and address specific concerns.
To conduct the pre-unconference chats, I used video conferencing via appear.in, a free, browser-based application that does not require plugins or user accounts. Rather than being exhausted from these calls, I felt energized and optimistic and I experienced many direct positive outcomes. These conversations enabled me to prime people to connect on day-one of the unconference with others with similar interests or from related work sectors. Frequently, I noticed that immediately after our conversation, first-time participants would join the online discussion of existing project ideas, or they themselves proposed new ideas. My conversations with two first-time participants led directly to their proposing community-focussed projects!
An unexpected benefit was that questions people asked me during the video chats led to actions I could take to improve the unconference. For example, when someone wanted to know what previous participants wished they knew beforehand, I asked for and shared example resources. One wise person asked me what my plan was for having project teams report out at the end of the unconference and this led directly to a streamlined plan (See Six tips for running a successful unconference).
Big thanks to AAAS CEFP training for giving me the confidence to try this community experiment! Arranging and carrying out these pre-unconference questionnaires and video chats took a big investment of my time and energy and yet, I consider this effort to be one of the biggest contributors to participants’ satisfaction with the unconference. Will 100% do this again!