Guest Post – Notes from Enterprise 2.0: Still looking for End User Adoption

[After a couple of years attending the Enterprise 2.0 show in Boston I decided to save myself the hassle of traveling cross-country and skipped the show this year. Turns out it was the best Enterprise 2.0 conference to date. My colleague TJ Keitt thankfully did attend and sent along the following impressions.]

Thomas_KeittBeing Boston-based typically isn’t convenient for an analyst covering companies that congregate in Silicon Valley, which explains why this blog’s regular author decided to pull up his stakes and head West. But last week’s Enterprise 2.0 Conference happened to be held in my fair city, allowing me to drive 15 minutes to meet with vendors that would ordinarily require a six-hour plane ride. After spending two days cruising the pavilion where vendors showed off their wares to a business world at once fascinated with and wary of social technology, Oliver asked me to share my impressions.

Going to this conference, what I really wanted to hear from vendors was how you go about convincing end users to take up your blog, wiki, social network, etc. This is a question that has been coming up more and more as companies shell out money for solutions that will ostensibly make their employees more collaborative, only to find that just a small sub-segment of the workforce is actively participating. It is particularly troubling for companies trying to move their workers off of social technologies that they do not control, like Yammer, and onto solutions that they do, like the vendors on display at Enterprise 2.0.

Coming into the show I didn’t feel that the vendors had a particularly good answer. Walking away I was left with much the same impression. There wasn’t a clear sense among the vendors as to how to spur adoption, and some of the answers they provided were wanting. For vendors who target lines of business in a bottom-up manner, their schemes for viral adoption work so long as users actually take to it and the IT department doesn’t eventually shut them down in favor of an enterprise-wide solution. For those with a more traditional IT-centric selling scheme, their reliance on corporate standardization on their offering works only so long as end users accept it and don’t have workarounds that they prefer. What I did not hear from these groups are the three things that I think are crucial to encouraging use amongst the rank and file:

  1. Helping business leaders map out what specific business problem the tool will solve. What we typically hear from information and knowledge management professionals is that there is some corporate mandate to “be more collaborative.” So, someone is put in charge of finding tools to make this happen. But without a clear sense of what “be more collaborative” means in the context of the business, there is no clear vision of who will be affected by the tool, what issues they face in their work and where a solution can begin to help the workers. [Oliver: I could not agree more. I hear from WAY too many businesses who's stated goal is to "collaborate better"]
  2. Providing assistance in re-engineering the business process that will be served by the tool. When bringing in any new technology and telling workers to use them in their job, you are mandating that they fundamentally change the way they work. This can be especially hard for someone who has become accustomed to doing something one way over the last ten years. A vendor could play a significant role here if they are willing to provide the professional services to help a client figure out how to tune the business process to naturally route people to the tool without completely disrupting their work.
  3. Embedding the tool within areas that the information workers live. Going hand-in-hand with the business process re-engineering is having the tool attached to the applications that the workers use in the course of their job. This is what makes offerings like EMC’s CenterStage and Microsoft SharePoint so compelling – the social tools are linked to the content that information workers are using in their daily job. This makes the experience natural and part and parcel of the assigned task.

Now, I am not saying that I did not see any of these things in the tools that I viewed at Enterprise 2.0. Most of the vendors had a story around the third point, but I did not see the complete vision – tying all three of these things together. For the point solution vendors, this combination of smart sales, consulting and product design can go a long way toward making them relevant as we race toward Oliver’s “Day of Reckoning.” And what could create excitement among those of us somewhat jaded from hearing the same pitch over and over is vendors coming up with innovative ways to address those three issues to drive end user adoption.

[Give TJ a piece of your mind in the comments or at tkeitt [AT] forrester [DOT] com]

  • TJ - nice to meet you in Boston.
    Oliver - sorry to have missed you.

    Looking forward to seeing how things progress - or not - by November's E2.0 in SF.
  • TJ, Oliver:

    Could not agree more with the post. It's taken a while for the "solve specific business problems" gospel to take root at PBworks--the company had its roots as a classic consumer-adoption story--but it's really helping us now.

    One of the things we do is provide professional services at a loss to help customers evaluate the solution. Recently, I did a session with a customer to help him instantiate his desired business process in PBworks Project Edition.

    We provide a 30-day free trial. The customer bought that afternoon, because he felt like he didn't want to waste time with a trial when he knew that we solved his problem.
  • Brilliant observations TJ. I couldn't help but stepping away for a moment and consider the foolishness of ALL of it -- can you imagine the level of cost/effort of vendors hawking their wares being similarly expended by iphone apps? This is the sort of scenario we should use as a metric for progress.

    Focusing on adoption changes the perspective of everything considerably. Part of the symptoms you've identified are due to classic methods -- IT has been focused on the wrong elements of reuse. The most critical elements of reuse are the evidences of the business and its operation -- real-world research and evidences of what it takes to make things happen, by the people making them happen.

    The 'innovation' you speak of is borne from this context of each business. We're dealing with 'disruptive technologies' imposing impact well-beyond the 'thing' itself -- the entire business macrocosm must adapt to adopt. This is alluded to somewhat in #2, but it goes beyond process -- the same reason I challenged a recent Gartner leader looking for a new BPM analyst, BPM is an 'old' answer, insufficient.

    So, are vendors responsible? If IT is ill-equipped to respond, can vendors provide relevant services as part of their overall offering? Would the offerings be viable? "By and large, a disruptive technology is initially embraced by the least profitable customers in a market", Clayton Christensen.

    "Drive end user adoption"? That's exactly the wrong way to consider the goal. It is the solution that must adapt for 'fit', not the other way around. Any solution with the appropriate 'fit' is naturally adopted...again, how much 'sales' is required for an iPhone app?

    Might the language we're using, which frames where and how we start tackling a challenge, be a major hindrance to our progess?
  • TJ Keitt
    Thanks to everyone one who's read this post and to those who took the time to share their impressions. It's nice to see that my first foray into blogging has generated interest.

    Chris - I think your points were illustrative of what I was suggesting vendors need to do in the first point. The salesforce needs to take the time to really get to the heart of the buyer's need. It seems that too often buyers see collaboration as the end as opposed to the means to an end. Thus, they throw technology - in this case social technology - at their workforce with the hope that they will figure out how to use it. You don't purchase and deploy a CRM system in that manner, so why do it with social software? Your willingness to work with the client to identify where the tool can benefit not only generates buy-in from the decision-maker, but it puts you on the path to selling him something that his employees will actually see the benefit in because there is clearly a purpose for its use.

    rotkapchen - It is an interest question that you pose about how we describe a business challenge relates to the success of social technology adoption. I'm of the belief that it does; as I mentioned above, social technology, and all of collaborative technology, is too often framed by business as a way of "being more collaborative" without any definition of what that means. In that way, the language that is often used is at a tactical level instead of a strategic level. And I believe this is not necessarily an IT problem, but a business problem -- business is telling IT what it needs ("collaboration") and IT is executing ("let's buy a wiki package"). And here's where I believe that vendors can help themselves and their customers by driving the conversation back to the strategic level ("what are you actually trying to achieve?"). Once that is done, I think the light goes on in the mind of the buyer and on the realistic conversations about what needs to change organizationally to meet the real goals -- and how a social technology can help you get there.
  • Nice job, TJ. I found guest blogging to be a bit intimidating. Your post just reinforces my disappointment in not being able to attend the E2.0 Conf.

    Your topic is an interesting one and strikes close to home for me. There are bus loads of smart communicators and strategists out there that are recommending enterprise collaboration tools. GREAT! Now who is going to lead the change?

    Each of these E2.0 service/product companies will best serve their customers by installing a representative to work with an internal project manager for the purpose of navigating the fear, decent, politics and roadblocks that stand in the way of adoption.

    Depending on the customer, this can be a long process... but a fun one.

    I have to disagree slightly with rotkapchen's comment. "Driving end user adoption" may not be ideal wording, however, gaining adoption in an F100 company with more than 100,000 potential users means that the service/tool/product needs to do more than just fit into workflow and solve a problem. Gaining adoption requires the understanding, usage and endorsement from leaders at many levels of the organization. In addition, employees and leaders in the organization will not likely pause to "check it out" long enough to adopt it virally. A structured plan is needed.
blog comments powered by Disqus