Why Many Social Software Projects Fail
By Daya Baran at September 17, 2008 7 Comments
Many social software projects fail because IT managers wrongly believe that successful communities form spontaneously after social software tools are installed, according to Gartner Inc. IT and business managers in charge of deploying social software need to choose a core purpose for the community and arrange implementation to achieve that purpose.
“Contrary to the common perception that vibrant communities arise spontaneously, starting with a carefully chosen purpose does not limit participants. It gives them the direction they need to form a productive community,” said Anthony Bradley, managing vice president at Gartner. “As those initial communities gain momentum, other groups will use the social application to build their own communities, and this is how social applications achieve widespread adoption across the enterprise.”
Mr. Bradley said that many IT organizations fall into the trap of following “worst practice,” installing social software in the expectation that productive communities will emerge spontaneously. Gartner’s discussions with clients suggest that the “install and they will come” practice rarely succeeds; about 70 percent of the community typically fails to coalesce. Furthermore, of the 30 percent of the communities that do emerge, many revolve around interactions that planners didn’t envision, that don’t provide business value and that may even be counterproductive.
The perception that communities on the public Internet appear to arise overnight and quickly grow to encompass millions of participants has led many organizations to assume that social software does not require the system-building rigor typical of many deployments. However, most successful social sites start with a defined purpose and a limited scope.
Gartner maintains that users need a well-defined purpose of appropriate scope around which to mobilize and that a good purpose for a social application has seven key characteristics:
1. Magnetic
The purpose should draw people directly to participate, immediately appealing to the “What’s in it for me?” characteristic.
2. Aligned
Purpose should align with business value, that is the “What’s in it for the business?” value, be it direct or indirect.
3. Low Risk
Organizations are advised to resist the temptation to opt for high-risk communities, which seem to offer the greatest potential for business value. They are better revisited once social applications have gained momentum.
4. Properly scoped
Gartner advises organizations to start with a minimal scope and focus on growing a community’s scale as fast as possible. Once the community has scaled up, users will guide on how to expand the scope.
5. Facilitates Evolution
Purposes must be selected that both the organization and community can build on. A “purpose road map” will allow for growing the scope of communities or establishing other applications and communities with the goal of progressing toward a highly collaborative enterprise.
6. Measurable
The success of a good purpose can be measured. Especially early on, when organizations are skeptical of social applications, Gartner advises choosing a purpose where business and community value can be clearly measured.
7. Community-Driven
The value must come from the community. The best communities contribute far more to themselves than do the enterprises that support them. If the purpose requires the enterprise to contribute most of the content, and the community participants are mere readers, the enterprise has simply used the new technologies as another channel to push communications.
Tags: online community, social media
RSS

7 Comments
Very nice post, and very true. I have seen more than one community dry up due to lack of such awareness.
[...] technologists, design Over on Web Guild (no relationship to Guildsmiths), Daya Baren wrote yesterday about a Gartner, Inc. finding that, “Many social software projects fail because IT managers [...]
Interesting to contrast with a recent survey at Information Week which found that IT-led Web 2.0 implementations had a much higher failure rate than those led by other groups.
BTW, in the study does Gartner distinguish between internal and customer-facing implementations? Some of the remarks above suggest this study focused on the former, but it isn’t explicit. For example, how often does IT lead a customer-facing social software effort? Not very, in my experience.
Best practices that encompass both internal and external social media without making distinctions between the two are about as useful as trying to teach someone how to ride a bike and play tennis with the same set of advice: “Get a good grip, keep your legs moving, don’t fall over.” Not wrong exactly, but also not really what you need.
Joe Cothrel
VP Community Management Services
Lithium Technologies
[...] Why Many Social Software Projects Fail "Gartner maintains that users need a well-defined purpose of appropriate scope around which to mobilize and that a good purpose for a social application has seven key characteristics:…" (tags: web2.0 community adoption) [...]
I am in conversations daily with companies regarding assumptions and ideas that they have for communities. I agree that the mistake that people (IT or otherwise) make is “build it and they will come” - and it looks so spontaneous. In fact nothing could be further from the truth. Successful communities take thought and planning and then careful management - not heavy handed “do this”, dont do this” but certainly active moderation and light guidance and assessment. Other critical success factors are dedicated resources, high level exec sponsorship and lastly a basic purpose that the audience shares. Oh, and did I mention numbers - there has to be enough of an audience so that a conversation can take place.
Joe Cothrel - VP of Community Management, Lithium Technologies, has written extensively on this - on the top 10 warning signs of potential failure.
[...] fails. Why Clogs will succeed. September 22, 2008 - 7:57 am by Eric Goldstein Clipped from http://www.webguild.orgMany social software projects fail because IT managers wrongly believe that successful communities [...]
[...] Why Many Social Software Projects Fail Gartner study: 70 percent of the community typically fails to coalesce! Found via headshift, of course. (tags: social software projects failure fail methodology gartner) [...]