Category Archives: volunteerism

Community Engagement: your agency does not have the budget to not support this

Funded research that includes a charge to engage a community (of scholars, end users, students, etc.) in doing this research, or in using its products (data, metadata, standards, etc.) is usually underfunded. There are two simple reasons for this. The first reason is that agencies typically underestimate the cost of doing community engagement through community governance. The second is that money is a very poor instrument for directly accomplishing engagement, mainly because of the perverse effects this has on volunteerism.

At the same time, efforts to support “community” are often pursued without actually building community-based governance. Project budgets may include large amounts of “participant support” for annual “community meetings” that could help build engagement. But without the governance structure that puts the community in a position to determine key aspects of the core activities, these meetings are really only very expensive alternatives to an email list. The attendees may learn something, and will forge their own interpersonal connections, but the work of building community through governance is left undone.

I was once “voted” onto the policy committee of a large agency-funded effort. The first thing we were told, after they flew us in to the annual “community” meeting, was that the committee did not make policies. Similarly, the act of voting was used without any available model of membership. There are better ways to get the community engaged.

One of the reasons that community engagement has become more visible as a goal is the realization that “network effects” can greatly amplify the impacts of a research project’s outcomes.  Indeed, Metcalfe’s Law tells us that value of a network is proportional to the square of the number of members (n2). Bringing network effects to research collaboratories can accelerate communication of ideas and knowledge sharing. A more recent study by David Reed points to an even larger effect: that of group-forming networks. Networks that allow members to self select into smaller groups (clusters) approach an exponential increase in the scale of interactions (2n), a scale that grows much faster than any power law distribution. Enabling the network to create internal, purposeful subgroups where members are highly engaged is one strategy that can really pay off for a funded research project.

The two curves in these graphs are familiar to most. The top one is the “power law” curve, which describes many distributions, notably, the expected relationship between the amount of attention/activity on an open Internet network in relation to the number of people so engaged. This is the usual “10% of the members do 90% of the work” situation. The bottom curve is the “bell curve” normal distribution, where the main mode is high-activity. What is important to notice here is that the space under the normal curve is much larger than the space under the power law curve. Much more activity is happening here, even if the number of people are the same.

The use of community-led governance to foster engagement is covered in several other posts on this site. There are some real examples of this that can be studied. The Federation of Earth Science Information Partners (ESIPfed.org) is one.  I would guess that many agency program managers can point to histories of counter examples: of projects that never created any governance capabilities, even while they spend huge amounts of budget on “community.”

The amount of real governance required to support activities also depends on what types of activities need to be supported. If communication is the goal, then a relatively weak governance system will suffice. If real collaborations (those purposeful subgroups) are to be supported, then a robust governance system may be needed. Clay Shirky examines three levels of social interaction: communication, coordination, and collaboration. Each of these levels needs its own type of governance.

Distributing activities across an engaged volunteer network of peers can use a very limited budget to accomplish everything that needs to be done. Money is not the driving force here. It is rarely the case that agencies cannot afford to support governance through project research budgets; more to the point, they cannot afford to not support this if they want to accomplish what only a community can do.

Volunteers or staff: Who is holding up your virtual organization?

Getting the right mix of staff and volunteers for a virtual organization is a crucial task for sustainability. The key is to take limited resources (if you have unlimited resources, call me) and invest these in directions that bring the best return for all.

What are volunteers good for? Many a community organizer has had moments when the answer to this is all too clear. Thankfully, those moments do pass. Volunteers are the heart of a virtual organization. Keeping this organ alive and well is job one for staff. Volunteers bring skills, vision, energy, and passion to the organization. They tend to do so in short-term increments. They need to know their efforts are valuable. This knowledge prompts them to stay engaged. Through the serial engagement of many volunteers, certain activities are maintained: governance, oversight, incremental work on infrastructure, a supply of new ideas, and, yes, occasional sidetracks. Nobody can sell your organization to donors and new partners better than volunteers. And nobody can grow your organization over time and on budget like volunteers.

What is your staff good for? Staff are the backbone of any virtual organization. They keep it on track and guide its fortunes. They have responsibility for those tasks that volunteers should not be asked to perform (more about this soon). They also have responsibility to keep volunteers engaged. They do the thank-less work and get paid for this. But that doesn’t mean the organization doesn’t owe them a heap of thanks. Still, they are professionals, and need to step up an take charge when the need arises. Generically, the work of staff falls into two buckets: everyday necessary tasks and putting out fires. Volunteers should not be asked to perform these types of work. Staff run the events on the organization’s calendar; they manage the web-presence, the accounting, the teleconferences, and a hundred day-to-day activities. They facilitate volunteer efforts. And, when the website is hacked, or the projector bulb burns out, they fix it.

Volunteers get called in to plan and direct new activities and articulate new goals. Ideally, they are given a say (not just a voice) in the organization’s operational budget. Because they do the planning and determine the budget, it’s only fair that they do some of the work. They can be tasked to scope out any new work required by a new goal and to build new capabilities to meet this. Then they either do the work, or determine that the job is too big for them to accomplish. When the volunteers are done with their efforts, the outcomes are passed back to staff to incorporate into the organization’s operational inventory. Sometimes the outcomes are not fully ready to use (having been built by volunteers). Staff might need to hire an outside expert to polish the work. Note: this person should be fully “outside” and not a community member. Never hire a community member as a consultant to fix another community member’s volunteered contribution.

When the job is too big, volunteers might ask for some support (more often they just stop answering emails). There are many ways to support volunteers. Paying them is the least valuable, as this transforms them into non-volunteers. There are several descriptions of the negative impacts of paying volunteers. Basically you are pissing in your own soup. Other means of support are always better: find them assistants (pay for interns), pay their travel, pay for hardware and software when required, and, if nothing else works, add staff to help. Sometimes, this might mean making a skilled volunteer a “fellow” for a short period of time. This move should include a community vote, including an open call for the fellow position within the community. The community is tasked to help staff fill a temporary (less than a year) need from within their ranks. By this, the “fellow” can be paid for a time and then return to the ranks of the volunteer community.

Remember that volunteers need to know their efforts are valuable. The organization needs to build and maintain recognition systems for volunteers. These include online and in-person awards. The three motivations for engagement are money, love, and glory. When it comes to volunteers, if you are stingy with the glory, don’t expect any love. And when you let the community add to their own glory, then you can stand back and watch new leaders emerge and know your virtual organization is healthy and growing.

Image Credit: Used on CC license. Photographer: Leo Reynolds on Flickr

Unintended Consequences Mock our Best Efforts

The dog was just a puppy, and it came rocketing across the street with its tail down. The dog’s owner, rummaging in his garage, the door open, yells out to dog. It’s some kind of lab mix and it jumps up on us with joy. We are mindful of the traffic on the street, and corral the pup by its collar. The owner trots over and we pass the dog back to him.

“Is it a lab?” my wife asked.

“Some kind of mix,” he said. “I got him from a shelter. They don’t euthanize here, so we went down to Riverside where they do, and rescued him.”

My wife has volunteered for years at the local Humane Society, where they struggle to find owners for their orphaned pups and kittens. Their pledge to not euthanize was designed to reassure locals of a mutual responsibility to manage their pets. Unintentionally, the Humane Society has also “rescued” their charges from death, and by doing so has removed that action from the scope of the people who come in to find a pet.

*******************

The local blood bank in Santa Barbara ran as a non-profit organization for decades, as a vital partner in local health and medical services. One day it announced that it was selling its operation to a for-profit blood services organization that would help manage the blood supply with new organizational tools and greater funding for new technologies.

Within a month, the number of  blood donors to the blood bank fell to the point where it was in danger of failing both economically and in its roll to provide for the local demand. Soon after, the blood bank resumed its operation as a non- profit organization, and the volunteers returned.

*******************

A large, federal agency funded digital library effort struggled for years to achieve greater impact. During this time, the project was run by a funded core of organizations. They had originally drawn up a community governance plan, but this had never been implemented. A cadre of volunteers, people who shared the vision of the effort, soldiered on with committees and working groups, but nothing seemed to gel. The agency provided some additional funding for new work, and the project parceled out these funds to a handful of former volunteers. Almost immediately, the remaining volunteers stopped volunteering, and the entire effort was soon defunded. One might argue that it was not the presence of money, but the lack of community that doomed the project, however, the impact of money was immediate and damaging.

*******************

The presence of money can interrupt the work of a volunteer community in unintended ways. But these do not need to be unexpected. If money is made available, it needs to be managed by the volunteers (they need to have a say in the budget), and it needs to support their voluntary efforts, not pay them for the same work.

As for the unintended (perhaps even perverse)  impact of not euthanizing stray pets; instead of, say, holding mock executions to give people the joy of rescue, there might be opportunities to advertise the burden of maintaining these pets, and the need for them to have real homes.

Photo Credit: Stephen Poff on Flickr

Creating Community is a Process and a Goal

People who talk to me about “adding a little Web 2.0” to their sites fail to understand that the heart of every successful Web 2.0 venture are the various communities that grow to depend upon the opportunities they acquire through the service. That frosting of Web 2.0 people apply to their portals and websites is mostly aggravating overhead. For the user, it’s like getting a box of chocolate-covered gravel.  Sure, you can add a dozen social media posting links for readers, but if you really want to start a conversation, then you need to dig a little deeper and offer the reader a better bargain for their end of the deal. Find a way to reward those readers who offer feedback or repost your content, and they might just do this again and again.

Should your Web 2.0 designs include building and supporting one or more communities of users, then you will certainly need more than a little Web 2.0 in the mix. Mostly you will need to start with a modest number of tools (microblogs, group support, media sharing) and then tune this list using the recommendations of active users. As soon as someone needs to sign in, they should also want to sign on as a member of something larger than just the software platform.  Make your Web 2.0 services launching pads for those who are ready to become community leaders. And then just stand back and watch.

Photo Credit: Chris Devers on Flickr cc license

Community, Democracy, and IT work

ITworkshop

ANOTHER FAMILIAR SCENARIO: Those of you from the IT world recognize this room: PPT up the old wazoo. But then it’s over and the work plans that have been listed on slide 17-23 (if not 117-123) are slated to become deliverables. The listserves get busy, the telecons are scheduled. Perhaps your IT group tracks tasks on BaseCamp and pings you whenever someone else has completed something. But if your not in the critical path, you might not know what others are doing and what your next step is. You might be able to volunteer a couple hours this week, but how do you know where these are best spent?

There might be a couple hundred people like you in the virtual organization (VO) that surrounds this particular project. Some were brought in to advise, others because of a current interest. At the core, decisions are being made and money spent. But the whole idea was that this was more than a distributed project among a small group of  paid Co-PIs. Most of the room was excited about helping move this forward, looking at the outcome as their payback. The workshop cost the government agency $100k to put on, and spent up three person-years in a week.  It had the carbon footprint of a small town.

The feeling of engagement that many participants experienced at the meeting lasted a few days. The funded Co-PIs went back to work. The larger VO languished as everyone else’s calendar’s filled up. Opportunities to pull in the talent and skills of the larger community passed by and dried up.

This doesn’t have to happen.

What is the answer?

One answer is, of course, cash. Spread the funding around and more people pay attention. But that is rarely possible. Another answer is community: grow it, use it, let it manage the work. And give it just enough funding to help people work together.

Be warned: when you let the VO community run the project you invite a range of voices into the room. You have to deal with competing interests and conflicting priorities. The good news is that these interests and priorities were there hidden (more or less) all the time in the VO, so dealing with them is something you can now do and move on. Otherwise you face these same issues when the project of over. To succeed, the VO community will need some form of internal governance. Since you are working with IT professionals, you’d better treat them like peers.

Your peer-based VO community will demand something that looks a lot like a democracy. Do not be afraid. You know that’s not how business gets done. At least you think you know that. In VO communities, democratic governance paves the way for volunteer participation, for leadership, for constructive criticism, and for active attention to the goals of the project. Try getting things done without it.