We were mentioned recently on the Second Life blog. They were blogging about communication and transparency and asked for comments on the companies that were doing it right. Very few of the comments took them up on that suggestion–more on that later–but one LibraryThing/SL user dropped our name as “a small start up that knows to admit it when it has got it wrong. and answers questions instead of ducking them.” SL repeated the recommendation.

The hat-tip got me reading the post and its comments. It gave me a powerful sense of deja vu! I’ve seen many of the same negative patterns on LibraryThing. Some I’ve seen and it got me thinking about why the patterns happen. Others I’ve seen us deal with successfully, so I thought I’d write about how I think we did it.

The post got so long I’ve split it in two. The first part describes the post and offers a partial defense of Linden Labs. The second will describe some of the things I’ve learned about member involvement, and some of the things Linden–and LibraryThing–could do better.

In defending Linden I want to make it clear that I am not a high-volume user of Second Life. I visit about once a week, usually for something like the BookMooch/LibraryThing meet-up. As a low-frequency, low-impact user I did not have strong or informed opinions about whether they’re doing a good job, and, except for admiring the book they put out, no opinion about whether they communicate well with their users. Until now, I enjoyed the site, but I wasn’t passionate about it.

Now, Doughty Lindens, I am on your side! And I would like to take this opportunity to extend my person invitation for Boston-based Second Life employee to drive up to Portland, Maine for a lobster roll and a beer at the LibraryThing apartment. Seriously. Expense it!

I sympathize for two main reasons:

1. The quantity of feedback was enormous. They cap the blog at 149 comments (and are excoriated for it). Users hit this in twelve hours. Comments totaled 28,000 words. The longest comment was 2,100 words long!*

   But I only saw the the horror of the situation when the blogger revealed that, as one response, Second Life was going to hire its first dedicated community-relations person. Not having dedicated community “handlers” is the brave way to go. I think its the best course of action—that “filters” are bad for both company and users. But man, I sympathize!

2. Most of the comments were negative, and many were downright nasty. The negatives wrote the most and screamed the loudest. They mentioned competitors; they talked about ditching the site; they went ad hominem. If you read only this post you would believe that Second Life was a buggy disaster, managed by lying, incompetent and venal “hypocrites,” focused on screwing its users and deaf to their unanimous and desperate pleas. In particular, they hate Europeans.

Now, I can’t beat back any of the specifics, but something tells me that this picture is flawed. It certainly isn’t my feeling, and I’ve never met anyone in Second Life or out with such strong, negative opinions.

More the point, people don’t write paper-length comments about something they hate. Or, if it is hate, it is a hate that only the deepest love can engender. While Linden Labs surely has much to learn from criticism, there is a meta-message: you’re doing something right.

Back-seat driving. I was caught by the amount of back-seat driving and second guessing. Stability was the main topic. Take this comment (much reduced):

“How many people at Linden Research know what the value of plus or minus three standard deviation on metrics is? Does anyone at Linden research know what control limits are? Has Linden research implemented +/- 3 sigma trending monitors … Does anyone at Linden research know who Deming was? Does anyone at Linden Research know what Kaizen is?”

Now, again, I don’t have proof, but I can’t believe that the commenter is better equipped to run Linden than the people at Linden. Everything points to a pretty stellar team–the sort of team that only an extremely exciting project and stock options can produce.

And think of what they’re doing. Linden (unlike LibraryThing) is doing something fundamentally new. Second Life isn’t just an online 3D world—itself a pretty new idea—but an infinitely plastic one. Everything is editable and scriptable, from buildings to sun glasses. It’s a world where members create buildings in real time, to an audience, and eyeglasses have their own programming code. It’s a word where you can not buy user-generated genitalia—many brands—but if someone has a compatible set, you can use them!

If that weren’t enough everything needs to be communicated to computers all over the world, running different hardware, with different networking constraints. Wikipedia puts their storage at 24 terabytes. They run thousands of machines.

Three sigma? This isn’t data processing for an insurance company!

Entitlement. Customers have every right to get upset. But this can get out of hand. Take this comment:

“[About] LL’s inability to provide full help coverage to basic accounts, one can compare this to the US’s inability to provide full health coverage to basic families.”

Excuse me, but the United States is a government! Whatever duty the US has to provide basic health care to families is utterly unlike the duty of Linden Labs to non-paying users. It might still make sense for Linden to do as much free customer service as it can; we do as much as we can. But failing to do so is not a grave injustice.

Opposition to change. I grew up in Cambridge, near Harvard Square. It used to be great, but it isn’t any longer. I think this. My older brother thinks this. My father thinks this. But none of us have the same Square in mind. The truth of the matter is that the Square we had in our teens and early twenties is the Square from which all subsequent examples deviate.

The same goes with software, particularly social software. Users wanted stability, not new features. There was particular hostility to LL’s addition of a voice option, although users were not apparently calling for it (“NOONE ever asked for the VOICE thing”) and didn’t use it (“except for escorts”).

That voice was only for escorts is clearly wrong–a number of users, including a member of the “SL Shakespeare Company” contradicted this. But I can’t believe the first assertion. Users don’t ask for game-changing changes.

But a company like Linden Labs needs to try new things. I’m not a big fan of voice either, but, as I see it, it had to be tried. It could have open Second Life up to a whole new audience. It may yet.

Expectations outpace openness. The more you let users in, the most they can expect. As one user put it:

“Saying ‘We goofed’ is not enough. What the goof is, and the steps being taken to see it does not happen again, that to me is being transparent.”

The commentator goes on the ask “Why did it take LL so lon
g to fix the ‘vanishing water bug?'” Now, I have no idea, but I can suggest some possibilities.

1. The “vanishing water bug” may have been hard to find. Back when software ran on stand-alone computers and was released in integer-number versions every year or two, nobody noticed. Web delivery speeds everything up, most of all expectations. Programming is still hard.
2. The “vanishing water bug” may have been deep. It’s unlikely that water was vanishing because of an error in the “prevent water from vanishing” function. More likely there was a basic problem with gravity, or transparency or some concept I’ve never thought of. Maybe Linden Labs was working overtime to prevent the vanishing water problem from becoming the “vanishing everything” problem.
3. Mundange things were more important. If Second Life is anything like LibraryThing, the “vanishing water bug” may have taken second place to the “we-grew-by-20%-this-week” problem.
4. Maybe a new feature was more important. Which was more likely to attract new members, stay-put water or voice?
5. To adapt mayor Giuliani on ferrets, “this excessive concern with [vanishing water] is a sickness. You should go consult a psychologist.”

As I’ll detail in part two, the answer to the cycle of expectations is more communication, not less. But man, I feel their pain.

Nobody answered the question. Users often take any opportunity to talk as an opportunity to talk about anything. In this case, the blogger asked for examples of companies doing transparency right.

Now, in fairness they can hardly restrict comments to this alone; the bulk of the blog post was about their transparency. But it was still remarkable that only 14 comments too them up on the request. Of these, only a few seems applicable. Walmart may be a great company—although I’m girding up my loins to doubt that—but it wouldn’t be at the top of my list of companies for Linden Labs to imitate. Ditto Amex, Southwest Airlines and Coca-Cola.

Looking forward to part two. I do not think LibraryThing’s discussions are as dysfunctional as this exchange. LibraryThing members may get angry, but they seldom get nasty. (And with fewer fuck-yous, I think our responsibility to listen goes up.)

But these are familiar patterns, and worth talking about as such. Some questions:

• Is disfunction inherent in the medium, or are there ways of doing it better?
• What obligations does being open impose on a company?
• Are there limits to openness?
• Does communication have to change as a company grows?
• How can a site encourage everyone to talk?
• How can a company understand member communication when you know not everyone is talking?

I’ll try to tackle those questions in part two.

*Shorter than this post, and man is this post long.