On our April community call, we considered how Customer Relationship Management platforms (CRMs) can be used to manage communities in STEM. We heard presentations from community members Yamina Berchiche, Erin Conn, and Chris Hartgerink, who are each using different platforms in their work, and learned about their similarities, differences, and general utility for relationship-building. We also took a few minutes at the end of the call to brainstorm some of the features we’d like to see in a CRM that was optimized with community management in mind.
In this post, we describe some of the themes and insights from the call, and share the recordings of the three presentations. This is not meant to be an exhaustive review of all of the CRM platforms available today, nor is it an endorsement of the products mentioned. Instead, we hope it will help you as you to work through your own requirements, and consider whether a CRM might be useful in managing your community.
As part of the latest cycle of grants under the Chan Zuckerberg Initiative (CZI)’s Essential Open Source Software for Science program, CSCCE will be working with the software nonprofit Bioconductor as they develop a new training program and community platform for their users.
Bioconductor is built on the R programming language, and is an open source platform for the statistical analysis of genomic datasets.
Over the course of the past 20 months, scientific communities have worked hard to pivot their member engagement strategy to support meaningful interactions in the digital space. Earlier this year, CSSCE worked with the Environmental Data Science Inclusion Network to reassess their members’ needs and ensure that the content and programming provided is responsive to them.
Launched in 2019, EDSIN’s mission is to facilitate and support diversity, equity, and inclusion efforts within the environmental and data science fields. EDSIN was established during an in-person conference sponsored by the National Science Foundation (NSF), and its leadership was planning a second in-person workshop to develop long-term sustainability plans, which was cancelled due to the pandemic.
For our “First Birthday Series” of blog posts, we are taking some time to reflect on CSCCE’s community of practice, which turned one year old on 21 October 2020. Our first post summarised the community “by the numbers,” and is a fun run-down of just how far we’ve come. In this post, we go a little deeper into the strategy and philosophy behind our programming. This post was jointly authored by Communications Director, Katie Pratt and Center Director, Lou Woodley.
A community of community managers
We are in a unique “meta” position at CSCCE in convening a community of community managers. That means members of our community of practice already know the potential value that’s waiting to be released when people with experience, knowledge, and ideas that are valuable to others in the group are brought together. Part of our job as community managers is to devise programming that supports the realization of that value, and that signposts to members what might be possible together. That’s true for CSCCE staff, as well as for our members as they support their own communities, although what that programming looks like will be specific to each community’s context.
This week we’re thrilled to share CSCCE’s Community Participation Guidelines with our community. These guidelines are the result of several months of careful consideration, and were co-created by members of our community of practice in a dedicated working group.
In this post, we, the members of that working group, outline our process. Over the coming weeks, we’ll also share additional blog posts in which we reflect on some of the nuances of preparing community participation guidelines. We are doing this for two reasons: We want you to know how we ended up here, and we want our experience to assist you as you develop similar guidelines for your community.
If you have any questions or comments, please don’t hesitate to reach out to firstname.lastname@example.org.
In January’s Community Call we reviewed our plans for CSCCE’s programming for the first few months of 2020. In this post we recap our intentions to launch three initial working groups this month – as a precursor to creating the supporting structures for future working groups later this year.
Why working groups?
CSCCE provides training, programming, resources and research to support community managers in science – and organizations looking to nurture scientific communities. One of our core activities is to host a community of practice, where existing community managers can learn from one another and ask questions of a supportive group of like-minded peers.
In addition to our Slack channel and monthly community calls, we’re now offering community members the opportunity to work more closely together in a working group.
We’re delighted to announce thatwe are now accepting applications for the 2019 cohort of AAAS Community Engagement Fellows, generously supported by the Alfred P. Sloan Foundation. The fellowship is a year-long professional development opportunity for existing scientific community professionals working in research collaborations, scientific societies, and other organizations supporting scientist-to-scientist or “in-reach” activities.
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, in part one of a collaborative two part series, Fellow Rosanna Volchok shares her thoughts on the similarities between community engagement and community organizing, as well as the importance of recognizing leadership skills in community managers.
When one thinks about fast-paced work, community engagement may not be the first thing that comes to mind. But ask the Fellows in the CEF Program and I am certain that many (if not most) would agree that effective community managers must be both agile and adaptable to change. The beauty, then, of the CEFP is that it provides those of us working in scientific community engagement with the space and time to reflect upon our roles. These meditations, in turn, allow us to define what it is that makes our work both unique and important to the communities we represent. In reflecting on my own role, I keep coming back to this idea that community management can be viewed–and perhaps should be viewed–as another model of community organizing. Blame my background in public service and advocacy, but I’m inclined to think that us Fellows are all community organizers no matter the title listed on our business cards.
That said, if we want to make the distinction between community management and community organizing (and many do), drawing parallels between these two fields has helped me to understand the critical role that leadership plays in my day-to-day work. Cultivating the art and skill of leadership is essential to mobilizing one’s community to action.
In January 2017, we wrapped up the training week for the inaugural class 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 the January training, the Fellows will report back on the Trellis blog, sharing their challenges, discoveries, and insights. Yesterday Stephanie O’Donnell described several different audiences and use cases for community playbooks.Today, in the final post in her three part series, will dive into the content of community playbooks.
Posted byStephanie O’Donnell, Community Manager at WILDLABS.net, Fauna & Flora International
Now that we’ve established how useful a playbook might be and how different audiences might use it, we come to the big question: what goes in your Playbook? Read on to learn about the different kinds of content and content mediums that you can choose from. The credit for this framework goes to the Community Roundtable, who presented the following information in a CEFP webinar.
In January 2017, we wrapped up the training week for the inaugural class 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 the January training, the Fellows will report back on the Trellis blog, sharing their challenges, discoveries, and insights. Last week Stephanie O’Donnell introduced the concept of community playbooks. Today, in part two of her three part series, she looks at different audiences and use cases for community playbooks.
Posted by Stephanie O’Donnell, Community Manager at WILDLABS.net, Fauna & Flora International
Once you’ve learned what a community playbook is, the next step in building your own playbook is identifying your audience. In this post, I’ll cover the two main use cases for community playbooks and highlight different potential audiences.
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.