inicio mail me! sindicaci;ón

When Simple 2.0 gets painful

by Jevon MacDonald

One of the things I keep hearing from customers (buyers of enterprise software) here at the Gartner Portals, Content and Collaboration Summit is that as they start to make the leap and begin purchasing social platforms and tools from vendors, they are getting left out in the cold when it comes to roll out. Often broken deployments, poor documentation, ever changing interfaces with lagging documentation, half-baked features, the list went on.

These conversations are just reinforcing something for me that I have believed for a long time: When you sell collaboration tools, you are taking on a level of responsibility that software vendors have not assumed in the past.

One of the big offenders appears to be IBM. The chief complaint being that their new platforms such as Quickr are so poorly documented and there is so little use case and other guidance that IT departments that are installing it aren’t able to properly train users. There were also several mentions of incomplete and downright broken features being put in to the software at critical social junctions. The response from IBM, according to was that those particular features were still in testing. You hear this less about Sharepoint, but the reliance on integrators would explain most of that. I have also heard the same thing about smaller vendors, but the level of satisfaction seems to be higher.

I did not experience this first hand — I am not a customer and have only demoed these tools — so take it with a grain of salt — this is all anecdotal of course, but it is making a clear point: Vendors need to understand the implications of social software and guide their clients in both achieving the maximum impact from social tools but they must also help mitigate the initial pain.

This is a new depth of the customer-vendor relationship, but for the short-term at least, it is going to be a prerequisite for successful deployments.

What we have right now are traditional vendors, IBM, Novell, Microsoft and BEA in particular, who understand that Social Software can open up a huge new market for them, but they are not at all ready yet themselves to properly address the market needs. They are showing a level of immaturity and irresponsibility that is unsettling. Instead of looking to outside thinkers and experienced practitioners for guidance, they are putting their customers at a huge risks post-deployment while promising too much up front.

Organizations with an internal locus of self control will gravitate toward smaller vendors and vendors who provide toolkits that the organization can customize and deploy in their own way. Longer term, customer are going to start buying social tools that fit specific needs in their value chain and workflow, and we are finally starting to see vendors popping up to provide these tools.

Much of this runs counter to my recent position that the incumbents are going to sweep up the majority of the new market and the space within the existing markets. I still think that is true, but I think the long term outlook is much fuzzier.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • TwitThis
  • del.icio.us
  • bodytext
  • Facebook
  • Google
  • StumbleUpon
  • SphereIt
  • E-mail this story to a friend!


3 Comments »

maggiefoxMarch 26th, 2008 at 9:20 pm

Great post, Jevon, and you raise just the first of many issues. Beyond implementation, what cultural change that can be expected within the organization, and how do vendors support/prepare the org for that? Internal marketing to get users to understand the value of adopting these new tools, support, training and communications plans go hand-in-hand with successful roll-outs (as AT&T learned with their collaboration suites, a great case study).

Social media/enterprise 2.0/whatever you want to call it is a crazy and fascinating mashup of disciplines that traditionally don’t come in one package and tend not to play all that well together - marcom and IT. We all have a lot of learning and exploring to do on our way to figuring out how it works best - whether the big guys will recognize that the rules/needs are different in time to leverage their size and relationships to dominate the market is the big question.

Michael ClarkeMarch 27th, 2008 at 12:14 pm

Or those smaller customers will gravitate towards solutions (wikis, hosted or otherwise, social bookmarking, whatever) that cost little or nothing and can be engaged with without the overhead of an IT department’s involvement.

Steve RadickMarch 31st, 2008 at 4:45 pm

Maggiefox brings up a great point about the cultural change. What is the change management plan for Enterprise 2.0 implementation? How are the needs and concerns of employees being met? How are they being communicated? What is the support system? In my current position at Booz Allen Hamilton, we look at Social Media more as a cultural thing than a technical one.

Social Media isn’t about the software - it’s more about the culture change that has to happen. I’ve seen wiki implementations where the organization created a process where everything that went on to the wiki had to be approved before it could be uploaded. While the technology is technically doing its job in this example, I’d argue that the organization didn’t even implement Social Media; rather, they’ve simply used a new tool to continue doing things in the same way they always have. This is why successful implementation of Social Media depends on integrating technology, people, and processes from the very start. All the Social Media technology in the world won’t do any good if people aren’t shown how to incorporate this technology into their work and understand that the same old processes don’t work. I hope that someday the major software developers will be cognizant of this fact.

Your comment

HTML-Tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>