Last Tuesday, 08 September, I hosted the Smithsonian’s National Museum of African American History and Culture (NMAAHC) researcher Tulani Salahu-din in a live behind-the-scenes event. The livestream Google+ Hangout allowed audiences to learn how Baldwin’s correspondence and personal items were acquired – as well as how Baldwin’s work is integrated into the inaugural “Making A Way” gallery.
Here’s a Storify of how it unfolded on Twitter – thanks to great collaboration with NMAAHC staff & boss social media team: https://storify.com/
Though I often host behind-the-scenes events, this was the first opportunity to connect our Transcription Center volunteers to the wider audience of a museum. Our Smithsonian Transcription Center volunteers completed the James Baldwin Collection in July, and they were keen to hear about the real museum work behind it. Here’s the hangout :
We had 40+ concurrent viewers of the program; they stayed with us for an average of 17 minutes. At the end of the 50 minute hangout, we also launched a new transcription project detailing Annie Malone’s Poro College that closed on Friday morning – in just 2.5 days. Our staff and audience found it easy to participate and learned from each other. Success all around!
I’m looking forward to discussing the practical aspects of this event and the ways it fits into a wider program of community management and coordinating all the things. I’ll share these thoughts and more with fellow experts in community building on October 1 in Washington, D.C. Hosted by DigiLab, the panel features tangible examples and best practice – please join us to learn more!
For her Nieman Lab fellowship, Melody Kramer interviewed me about my approach to volunteers and community with the Smithsonian Transcription Center.
In her resulting report “Putting the Public into Public Media,” Melody culls insights shared from contexts of many public(inter)facing projects. She puts forth alternative and manageable models for membership. For me, the take-away is to build from a simple but not-so-easy to achieve starting point: ask your public(s) to build with you, have a say in the product they consume, and work with your product to better suit their needs. Together, you can attain more meaningful, deeper, and resilient engagement.
Melody features my approach with the Smithsonian Transcription Center as a case study. In addition, she’s included some of my comments as a footnote. She asked me to detail “how” I build community and engage with our volunteers. Continue reading for my answers to Melody’s question: “How do you foster community?”
“I think I have fostered community by
- being authentic in my engagement (using my voice not hiding behind the Smithsonian, and being enthusiastic because this stuff is pretty cool),
- asking questions that furthered the dialogue (how did you hear about us? what did you think of that? what was most surprising? what would you like to do next?)
- establishing a rhetorical approach that made it clear that we/I was learning at the same time as the volunteers
- establishing a rhetorical approach that suggests there is ALWAYS more to the story and that this is a chance to make discoveries – and then by recognizing or acknowledging those discoveries
- creating the hashtag #volunpeers to allow volunteers to leverage the structure of social media spaces to communicate with one another and with me/us – encouraging them to use it as well to ask for help or indicate a project needs review, etc
- creating collaborative competitions, rather than leaderboarding: #7DayRevChall (7 Day review challenges) allowed people to contribute collectively to a goal, then metric and try to beat the group goal – and using daily updates to share progress. This also allows for skills acquisition and learning best practice for review AND addresses an issue we see frequently – folks love transcribing and pages languish waiting for review. Every 2 months, we draw attention to this
- focusing on the process of transcribing and reviewing often over the volume of the product – and cultivating/encouraging patience from experienced volunteers in regard to “newbies”
- letting volunteers speak to each other directly in spaces in which they already live and are comfortable (Twitter, Facebook, Tumblr) – and we have benefitted from volunteers who are welcoming and want to help each other complete projects
- Also by engaging through those 3 social media networks (also instagram some and hopefully reddit soon), volunteers have the ability to “curate” and own their experience and the product they have created. My perception is that creates more in-depth brand engagement, as well – these volunteers list “digital volunteer for @TranscribeSI” or “#volunpeer for @TranscribeSI” in their bios
- listening to the feedback and description of external interests from volunteers and gauging their excitement in subject matter – then actively courting the archives, museums, and libraries that have related material
- Finally, actually integrating their feedback into site design when(ever) possible”
It seems to me that many of these steps start with two words: curiosity and sharing. In practice, these two words create a cycle of behavior – as you’re curious, you investigate. When you discover, you may want to share so others can learn. When others share, your interests are piqued and you become … more curious. Asking questions, discovering connections, solving challenges, and bringing together people – these all emerge as actions grounded in curiosity and sharing. When I understand that a volunteer has had a lightbulb moment with a project, I try to connect them and this experience to the Smithsonian group that has shared the project. Then staff and public alike are experiencing the moment of discovery – and learning from each other in the process. This often happens in our social media spaces, but I also do this one-on-one with feedback e-mails and questions from our volunteers.
Are you a community manager or are you a volunteer for an organization? How do these approaches relate to your experiences?
Today is international Day of DH 2015 – here’s how I’m reflecting on (and doing!) digital humanities practice and possibility through the Smithsonian Transcription Center.
First, I’ve created a blog for Day of DH 2015. I’ve already posted about the opportunities “we” have to learn together with the Smithsonian Transcription Center. The “we” is me, volunteers, Smithsonian staff, the wider public, researchers and more – in any and many configurations. Today alone, we’ve learned about 19th c ink innovations, President Obama’s commitment to #PollinatorHealth and shared how the public can help, and helped new volunteers learn how to transcribe astronomical logbooks and botanical logbooks. It’s another in a series of ways #welearntogether.
Read more of my first post after the jump.
I spoke about three challenges in scholarly crowdsourcing in a CCLA panel discussion on 07 May 2015. Here is what I had to say about trust, workflow, and acknowledgement.
I was invited to participate in the CCLA workshop on scholarly crowdsourcing – hosted by the University of Maryland and Drs. Mary Flanagan, Neil Fraistat, and Andrea Wiggins. I was asked to join a panel discussion and share my thoughts on challenges for scholarly crowdsourcing. Here are my notes in full.
When I think about scholarly crowdsourcing, I start with possibilities – the distributed, collaborative, unexpected connection that inevitably occurs. I know these possibilities to be true from my practical work and research: expanding discussion with crowds who are focused on achieving shared goals. Stemming from this work and learning, I see three challenges for scholarly crowdsourcing. These challenges can impact practice, policy, and participation; they are trust, workflow (a.k.a. resources) and acknowledgement.
I believe people understand their worlds through cumulative experience and bundle that with them wherever they go. That means everyone brings baggage on these adventures – sometimes that makes collaborating a bit longer to sort out… But sometimes that baggage is like Mary Poppins’ carpet bag – providing what is needed in an enchanted moment of engagement. Without trust in the potential of the product and in the well-meaning nature of the community, we might not tap into hidden reservoirs of skill and knowledge.
That calls us to trust the process of connecting with people who have useful knowledge and skill sets. It asks us to trust that quality data can be produced by a truly motley crew – and to grapple with the potential of that crowd-generated information to paint a more complete picture than presented by an expert.
We have seen the results and we are bought in, to varying degrees, in this room and on the stream – but how can we make this a cultural shift to trust, so our starting point is no longer justifying quality but rather showcasing possibility?
Trust is Risky.
Trust changes design elements – for example, decreasing single key entry standards from 10 to 3. Trust is shaped by and reflected in discourse, rhetorical approaches, and instructions – these words+images+workflows can create or flatten barriers to entry.
Trust makes authentic communication and opportunity possible by — at least in small ways — becoming (temporarily) vulnerable. Trust is a vital component of successful public engagement – and it remains challenging.
The reality of crowdsourcing typically is born from the need for help – whether in expertise or scale.
I frequently find workflow concerns at the foreground of managing projects. It is one of the most underdeveloped (perhaps underrated) elements of crowdsourcing projects. I think we can address this challenge by listening closely to those managing projects and considering creatively solutions.
We can return to our designs and find ways to make them better… indeed, some of us never leave the design phase as we iterate and optimize experiences. We can also break down the processing of data and the crowdsourcing experience into small and manageable YET still connected and coherent steps. We must develop trust in new ways of “doing” as well – to be innovatively practical in rethinking resource constraints and workflow demands.
The final challenge I see is acknowledgement – in many ways, for participants, organization, and voices yet to join.
Acknowledgement is honoring the organization/ institution/ or project’s side of the bargain, whether reporting on outcomes or making products more available – to articulate through action: “we are doing our part as you do your part”
Acknowledgement is more than high-fiving or virtually fête-ing the crowd – though that is an extremely important part of the practice. It is building that acknowledgement into the system – such as noting crowdsourcing efforts in newly created collections records.
We must face the challenging pieces of acknowledgement, such as respecting the community’s new knowledge enough to give them a place to apply that knowledge – evolving the activities or tasks in which they can participate.
Maybe acknowledgement is making the product available in new ways, with less restriction (trust again!), and opening the process with interoperability in mind.
And still acknowledgement requires investment – being there, listening, thoughtful development and design, open communication, and a willingness to go a few extra steps to demonstrate what crowdsourced public engagement means.
Acknowledgement is also reflecting on who is NOT present, who is not yet participating, and taking clear steps to improve access at every level and to increase representation – to surface and tell stories that have been left behind, erased, or blurred.
Those are the challenges I see in scholarly crowdsourcing – and I hope the conversations we have today lead to discussions we hold elsewhere and practical steps to make these obstacles into opportunities for better experiences from every angle.