I’ve spent a few weeks now playing with Google Wave, and like most people who first encounter the service I started out deeply confused (see below for my exploratory exchange with Forrester RA extraordinaire Zack Reiss-Davis). As I got further into the tool I began to get a much better feel for the value it brings to the table. For a comprehensive write up see Daniel Tenner.

So what is the biggest frustration with Wave? It’s not integrated with my email. I now have two inboxes — three if you count Google Reader. Thanks Google. I have no idea when new Wave messages come in. Now admittedly this is a pretty minor quibble, but what I quickly came to realize, however, is that this problem of integration is a MUCH bigger problem than just two inboxes. What it means is that Wave will never take off as an email a stand-alone collaboration client.

Lets start with the assumption that Wave is the next paradigm in corporate email, IM, and collaboration. How will the tool be adopted? Presumably corporate IT will either proactively decide it has value or (more likely) cave to pressure from a subset of the business and start offering Wave or a Wave-like tool for employees. So what happens when the team that desperately wants Wave needs to collaborate with a coworker that doesn’t have Wave? That other employee is either SOL or he has to get his butt on Wave. That’s right, there is no clear way to use Wave in a mixed-modal environment — either EVERYONE is on or it’s simply not going to work. Having closely followed the enterprise software space for quite a while now I can assure you that no matter how much people dislike email you’ll have to pry Outlook out of their cold dead hands. To make matters worse its not like one single company can easily make the cutover either; if you abandon a traditional email client in favor of Wave you’ll constantly interact with customers, partners, and vendors who can’t make use of the Wave construct. Not too bad if you can mix traditional email and Waves into one inbox (which is undoubtedly coming) but how on earth do you invite someone into an in-progress Wave if they only have a traditional email client? (To see exactly why this is a problem take a look at Daniel Tenner’s writeup).

I have faith in Google’s ability to engineer themselves out of major computing problems, but I have yet to see them truly commit to a user experience and see it through to the end. Maybe Wave will be different, but I’m not holding my breath.

That all said, I do believe that Wave can be extremely valuable, but not as an email or IM client. Instead Wave should be applied to a collaboration environment like SharePoint or Jive. In this scenario we would abandon the Wave inbox almost completely and instead focus on creating and embedding individual Waves in workspaces and projects. Anyone with adequate permissions would be able to navigate to the Wave, comment, add value, hit replay, and quickly collaborate with colleagues. Here Wave is simply another content type. However even more likely is a scenario much like what SAP has already shown with its own Wave integration. Here Wave is simply the user experience on top of another artifact — in this case a business process modeling tool.

The Wave interaction model is very cool, and definitely groundbreaking. Advances like an appstore and federation will surely help push it along. But it will not kill your corporate email or IM; lets see what we can do with it elsewhere . . .

View Comments

Today is the second day of JiveWorld, Jive’s first customer conference here in San Francisco, and so far it has been an exciting mixture of my current role at Jive and my past role at Forrester. Yesterday I had the pleasure of joining Jive’s Executive Advisory Board meetings and ran into several customers who had followed my work at Forrester. That evening I bumped in to a pair of attendees from a Forrester client I had consulted for this past summer, and I also got the chance to catch up with the always insightful Susan Scrupski.

The best though was attending a presentation from Forrester’s Corey Matthews, the firm’s top Web Marketing Manager, who was presenting some of the results from Forrester’s own use of Jive SBS for its Forrester Leadership Board offerings. Shortly before his session Corey and I chatted a bit about Forrester and Jive, at which point Corey said something that really struck me: “You are now like the 10th person at Jive I know on a first name basis.”

I stopped for a second, replayed the previous 24 hours, and suddenly realized that nearly every interaction between a Jiver and a customer started with the Jiver greeting the customer by name. Yesterday: “Hey Jim, we’re getting that code ready for you later this week, I think you’ll be really happy.” Lunch today: “Jennifer, how is your rollout strategy progressing?” Hallway: “Mike! Its great to see you, how are you enjoying the conference?” You’ll have to trust me when I say this interaction is completely genuine too. Frankly the conference badges are microscopic — you couldn’t fake it if you tried!

I’ve been at Jive for about a month now and of all the wonderful things I’ve seen this is the most amazing to me. I promised myself I wouldn’t breathlessly blog about how great Jive is, but this post will have to be the exception; it’s too hard not to share the excitement of working for a company that truly cares about its customers. Though on the flip side, I’m horrible with names . . .

View Comments

With great excitement and a bit of sadness I wanted to quickly announce that I will be leaving Forrester Research and joining Jive Software. My last day at Forrester is tomorrow.

All told its been a great (nearly) five years at Forrester and I am tremendously grateful to all the past and present Forrester employees who made the job so exciting for me. I’m confident that the Forrester team I leave behind will be in great shape to pick up my research themes and carry them as far as I would have, if not further. Specifically Laura Ramos, Rob Koplowitz, and TJ Keitt will be taking over where I left off.

As for me, I will be joining Jive Software as a Sr. Product Manager. I’m very excited for the new challenge.

Finally, for the loyal readers of this blog, I don’t expect much to change at StrategicHeading.com — the blog should be just as focused as before and cover largely the same content. As for the recent posting hiatus, please forgive me — I was a bit tied up working out all the above details!

View Comments

Well this has nothing to do with social media whatsoever, but I got a good laugh this morning when I checked in on the Detroit Tigers. I know newspapers aren’t doing well these days, but this is getting a bit personal (see below).

Here is the article in case you want to check in on the original.

Comments Off

One of the more interesting parts of the analyst gig is that clients have the opportunity to ask pretty much any question they like through the inquiry process. Sometimes the results in aggregate are pretty fascinating, but by and large I find myself answering the same general questions over and over again.

This was not the case a few weeks ago when I took what I expected to be a typical inquiry asking about how to kick-start an Enterprise 2.0 initiative. Instead of run-of-the-mill questions about staffing, content management, governance, and employee participation the client asked a very pointed question: how do we keep employees from unionizing with our Enterprise 2.0 platform.

All things considered I’m surprised I don’t get this question more often. The popular perception is that Enterprise 2.0 software is about revolution, and flinging open the gates to creative chaos. Possible, but not necessary. And for many companies, unproductive. So what should you do to make sure that the conversation in your Enterprise 2.0 system is to your liking? Here are few simple steps:

1. Do not allow anonymous posting: The simplest way to ensure the conversation is on-topic and constructive is to associate each and every artifact with an individual. If an employee knows their boss, CEO, etc. may see the comments they will be a lot more careful about what they say. This is, however, a double edged sword; in many cases employees will resist saying anything at all for just the same reason.
2. Publish your rules of the road: If you expect employees to comport themselves in one way or another you have to make sure they know what is expected. You should already have rules developed so make sure they are in an obvious place on the site and remind people from time to time of what you expect.
3. Use the keyword flagging features aggressively: Since most Enterprise 2.0 platforms were developed out of customer facing community software they generally have robust keyword flagging and moderation features built right in. If you are based in Chicago you may decide to flag “Bears” and “Packers” to discourage discussion of the NFL. But be careful, posts that contain these keywords should be moderated, not outright banned, especially if you sell bear skin rugs, or work for a meat packing firm.
4. Work with your HR, Legal, and Labor Relations departments at the very onset: Be sure to have a plan in place to deal with inappropriate content and behavior before you get rolling — your existing communications policy will likely suffice. The last thing you want is to put the company in legal jeopardy by reacting too vigorously to an incident. Plus you’ll want to have any legal or union “peculiarities” in mind before you start sourcing technology.

Now, I should say that I wholeheartedly believe that an oversight strategy that treats employees like adults and takes an open stance to employee communications is the better approach. But many firms still restrict access to websites like ESPN, Hotmail, YouTube, and Facebook and for those firms the above steps should get you well on the way to an Enterprise 2.0 strategy that allows for more dynamic employee collaboration and productivity without flinging the gates wide open.

Note: The above picture comes from the “battle of the overpass,” one of the most infamous union clashes of Henry Ford’s rocky relationship with the UAW in my hometown of Detroit. It should in no way imply the inquiry came from Ford. For a fascinating look at the circumstances of the photos themselves check out the Iconic Photos blog.

View Comments

The last couple of weeks I’ve been working on a series of case studies looking at social media marketing. Specifically I’ve been interviewing small to medium-sized tech firms about how they have made the transition from a static, traditional website to one that is more interactive and community oriented. We went with smaller firms because, while Dell and Google have highly engaging Web presences, we wanted to find out how firms with limited budgets are making the transition.

I wrapped up interviewing this week and found some great case examples to work with (thanks to everyone who participated!) though so far no one has felt like they really nailed the strategy, as we expected. All told I got to speak with 10 firms, all in different stages of deployment and with different strategies. There was great diversity, except for one little thing. When I asked how the traffic on the community parts of their websites compared to the corporate site overall we got a relatively tight range:  15%-30% of the corporate traffic is now coming from the site’s community features.

Now, longtime readers of this blog know that I pride myself on my stats chops, so there should be no mistake that this is not a statistically significant finding. But I do find it curious that such a tight range would emerge from just 10 interview, and I have a sneaking suspicion that further research would reveal a finding that is not far off from what we have seen so far. For those readers that have the numbers to weigh in, what have you seen on your own sites?

Not surprisingly the firms with strong discussion forums were up in the 30% range, while those with young blogging efforts were down in the 15% range, though across the board the interviewees reported growing traffic. In addition much of that traffic has been coming from organic search, bringing new visitors to the site, associating the firm’s content with valuable keywords  like “steel pricing”, and generally raising the SEO of the site at large. In fact, the one value of social media marketing that nearly everyone pointed too was search-engine optimization. So, if you’re trying to get a social media project off the ground I highly recommend keeping that nugget in your back pocket. Client engagement may still be a bit soft, but SEO is something most CMOs and even CEOs are willing to get behind.

A 10% boost in traffic (there has to be some overlap) and dramatically improved SEO sounds like a win to me.

View Comments

Well, dead may be a bit of an overstatement, but it is clear that the phrase “Web 2.0″ is dying.

This week my new report “Inquiry Insights: Web 2.0 And Social Media Technologies, Q1 2009” hit the Forrester Website. Throughout a given year, Forrester fields thousands of inquiries from clients and non-clients alike . Analyzing the nature and frequency of these inquiries — while not yielding statistically significant conclusions — provides a fascinating window into the minds of IT professionals, marketers, and technology vendors concerned with specific topics and often shows major trends in technology interest throughout the technologies’ life cycle.

So what have we seen for the Web 2.0/Social media market? Though the arguments about what to call the market — consisting of blogs, wikis, social networks, RSS, widgets, etc. — have mostly faded away, what people call the market is no more settled than it was 3 or 4 years ago. The big shift: a move away from “Web 2.0″ and a move towards “social media” or even more frustratingly towards “social networking” as a overarching category (not pictured below).

The change has been occurring slowly over the last year or so, with the phrase Web 2.0 hitting its peak among Forrester’s clients in Q2 2008, and falling off from there. From my point of view Tim O’Reilly and John Battelle’s effort to evolve the phrase into “Web Squared” is effort well spent; Web 2.0 had been getting stale and had lost its cachet.

One final note for the Enterprise 2.0 enthusiasts out there, that phrase has clearly not caught on with Forrester’s clients yet at all. Partly this is due to the fact that — for reasons I don’t want to get into  — Forrester resisted using the phrase for the last couple of years, and partly because Forrester clients interested in Enterprise 2.0 topics also use the phrase social media. It makes life mighty confusing for our inquiry team whose job it is to route the questions to the right analysts.

View Comments

I’m loath to use this blog to just complain about things that annoy me, but this is one that REALLY annoys me. For some reason in the last couple of weeks the Wall Street Journal has taken to publishing a new RSS entry every time an article is updated. This has been bearable so far, but this morning I was faced with at least 20 different entries pointing to the same Yahoo!/Microsoft search deal (see below). I have yet to unsubscribe completely, but am thinking very hard about it.

For marketers there is a clear lesson: RSS, and social media in general, have a very low switching cost for users. A simple click and I’m gone. If you spam users, get too “salesy”, or get too far off topic users can easily move on to something else. The reward of an engaged audience can be high, but the risk of alienating them, or tripping over your own feet is high as well. Experiment, but be careful.

For The Wall Street Journal, please, for the love of God, fix your RSS feeds!

View Comments

[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.]

Being 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]

View Comments

Chris Lynch over at CIO Magazine has a nice write-up on the Enterprise 2.0 market that is likely to ruffle a few feathers — Microsoft Sharepoint vs. Enterprise 2.0 Start-ups: Day of Reckoning Arrives. All in all the article does a very nice job of aggregating a diverse set of viewpoints and there are a few quotes from me personally (turns out I was the one to call Sharepoint 2010 a “day of reckoning”).

There are few things that do need a little clarification:

• The day of reckoning is at least a year off. SharePoint 2010 won’t be out this year, and it will take 4-6 months before a mass of companies actually complete their rollout. That said the SharePoint marketing machine will likely start working overtime in the next few months, so the impact will start to be felt before then. Then again I was speaking at the Gilbane Conference last week and noticed the Microsoft booth was still pushing SharePoint 2007.
• Existing Enterprise 2.0 customers will be unlikely to sink a lot of resources into switching. For companies like Jive, Telligent, NewsGator, and Atlassian the problems with SharePoint 2010 are going to crop up with new deal flow. It is unlikely that existing customers will jump at the first opportunity to take on a major transition that will require major IT resources, content migration, and (most importantly) user training.
• The market will be defined by incremental innovation for the foreseeable future. In the article Ross Mayfield, president and chairman at Socialtext, makes the important point that Microsoft is on a much longer development cycle than its smaller competitors: “A year ago, the idea of having micro-blogging and activity streams for the enterprise was a new concept. Well, that’s around the time they probably froze the spec for SharePoint 2010. Overnight, the demand for social software changed, and it will change again.” These innovations will have an impact on the usefulness and fidelity of Enterprise 2.0 tools, but I would not characterize these as major innovations; it seems unlikely that many companies will make a decision based on these incremental innovations.

Now, while I do believe that there is a base level of collaboration that will become a commodity (the broad collaboration that Microsoft and IBM will provide) there are some very important ways that the smaller vendors can stay relevant.

• Focus on the customer facing market. The customer facing side of enterprise Web 2.0 — the use of these tools by marketing departments — is going to remain hot, and differentiated, for quite a while longer. There is big business here and most vendors in this space already play in both camps.
• Tie the internal and external market together. Customer facing communities are great, but few thus far are having a real material impact on the business. Why? It’s a long manual process to take insight from the community and bring it into the business. Those vendors that can best tie these external marketing communities to internal productivity and collaboration communities will help their customers truly realize the value promised.
• Provide customer and partner communities. The extranet has long been the red-headed stepchild of enterprise collaboration because, frankly, its costly to get customers and partners working alongside employees and so far the tooling has been poor. That problem is rapidly disappearing and the vendors that can best equip their customers to get real work done with outside groups stands to make a lot of hay — and unless Microsoft changes its licensing model this is not a place it can compete.
• Get vertical specific or process specific. If the base level of collaboration is commodotized what is the next logical step? Get more relevant to the business. This will mean creating collaboration applications or modules specifically tuned to the industries and processes of the customer and providing a much improved out of the box experience for things like project management and innovation as well as a top shelf application for Law firms, doctor’s offices, and restaurants. NewsGator is already heading down this path with innovation and PbWorks is already heading down it for Law firms. Its a smart move and will save a lot of companies.

All told this market is set for a major change, and many of the vendors we know today will no longer exist — Microsoft is raising the bar and some vendors won’t get over it. But some will, and those that do should have solid businesses to show for it.

View Comments