post

Lessons from the TechCrunch Wiki War

Mike Arrington’s TechCrunch Parties have become “THE EVENTS TO ATTEND” in the Valley – in fact not just in the Valley: last time around I remember participants driving up all the way from San Diego, and this time people will fly in just to be there. The last party as well as the next one this Friday both sold out within hours after the announcement, and a lot of readers felt frustrated:

  • Some felt that first-come-first-served is not fair enough with such a short notice (an hour or so)
  • Some publicly asked for special consideration to get in
  • Some proposed to pay for “tickets”
  • Just about everyone complained for the lockups in the registration wiki.

I don’t envy Mike in this situation. It’s his party, his house (well, at least for the previous events), it would be perfectly OK for him to have an invitation-only party. Yet he obviously wants to see new faces, so he opens it up to anyone, but then of course he can’t please all… This time around, for the seventh TechCrunch Party hosted by August Capital there was more than the usual rush: the registration wiki has become constantly locked up and Mike was forced to move RSVPs to comments on his blog, closing the wiki.

Mike received ample feedback on why the wiki was not the right platform to handle hundreds of almost simultaneous registrations, and several entrepreneurs seized the opportunity to announce new offerings. Central Desktop announced a free public event wiki, and since it’s a hybrid not-just-a-wiki solution, Founder and CEO Isaac Garcia claims they do not have lockup issues (they use a form with a database in the background). Zoho Creator would have been another elegant solution.

However, what almost no-one talks about is that this was not simply a technical glitch. Having been lucky enough (?) to wake up 4am the day the wiki opened I managed to register myself at exactly position #100 in the wiki, then observe the wiki-war that soon ensued. The major “sins” I witnessed were:

  • Individual users registering entire blocks (dozen or more) names
  • The same users sitting on the wiki (blocking), probably while coordinating with their buddies who else to sign up
  • Previously registered names getting deleted

One can perhaps justify registering others, although I don’t know where the reasonable limit is ( I only signed up myself), but deleting others is the absolute cardinal sin. Apparently fair play is a strange concept to some.

This raises another issue though: are these people not aware that wikis provide a perfect audit trail and what they did can easily become public? Or do they simply not care? Is getting in on the TechCrunch party worth being displayed on a virtual “hall of shame”?

This particular incident aside, I think the major learning here is the overall lack of awareness of a typical wiki’s capabilities and how to “behave” while using it. I know many who’d like the collaborative capabilities but are afraid of “chaos” and the potential lack of civility… in short a major ‘wiki war’ if they open up editing to anyone. Most wiki platforms offer technical controls to limit chaos: even consumer /community focused WetPaint introduced several security schemes in their latest updates, and enterprise wikis like Socialtext and Atlassian’s Confluence have for long had elaborate security schemes – heck, that’s why they are “enterprise”.

Just as important as the permissioning is the role of social- behavioral norms, which clearly are more common and more forceful in a corporate environment, where all wiki “contributors” work for the same company. “Ross Mayfield said that in four years of building wikis for corporations Socialtext has seen precisely 0 trolls and 0 instances of vandalism.” He also maintains a Best Practices wiki (hey, it’s the new skin!). Now, remember, it’s a wiki – you can contribute, not just read.

As for the TechCrunch Party, the guest list is currently at 738(!) and here’s a preview of who’s coming, courtesy of CustomCD.us. (who may have intended to keep this a surprise, but I found it anyway….)

Update (7/28/2007): Here’s another case of wiki “who done it”.

post

Atlassian Taking On the World

(Update: apologies for the dead video links, Youtube is apparently down, here’s their message: ”

We’re currently putting out some new features, sweeping out the cobwebs and zapping a few gremlins.“)

I’ve recently had a chance to meet Mike and Jonathan in Atlassian’s San Francisco offices, and frankly was blown away by their enthusiasm, the company’s growth, but most importantly by a demo of Confluence, the market-leading enterprise wiki.

Market-leading? Never heard of them, you may say …. Certainly they enjoy a lot less brand recognition than let’s say JotSpot or Socialtext, both of which enjoyed abundant PR from the moment they launched, largely thanks to Joe and Ross‘s star-power. (Hey Joe, you were my early inspiration to get started with blogging, time for YOU to post again!). Lacking the “instant brand”, Atlassian spent their money on product development instead of PR, and it has obviously paid off. Watch this video for background:

Less PR or not, they are not exactly unknown to customers, as Confluence’s corporate market share is more than the others put together. From what I understand Confluence’s sweet spot is larger organizations, where administration, sophisticated permissioning schemes (groups, pages, activities…etc.) scalability, performance are increasingly important. (Yes, permissioning kinda goes against the social, “we’re-all-contributors” nature of wikis, but it’s a fundamental corporate requirement). The largest implementations currently run up to 30k users, but Atlassian is working on a clustered release that will be scalable to hundreds of thousands of users. Pricing also reflects the focus on large corporations: while at the entry-level Confluence is typically more expensive, at the high end (large user-base) it costs less then either Socialtext or Jot.

Despite it’s impressive feature-set and favorable price Confluence is not an available choice for some customers; namely those who are determined to use SaaS solutions. Confluence is strictly on-premise, download and install-behind-the-firewall software. Being a big believer in SaaS of course I would like to see them offer a hosted version, but today’s market reality is that only 10% of all software sold is SaaS. Atlassian’s own customer experience is that a lot of larger organizations do want their wiki behind the firewall, and competitors must have been receiving similar feedback, as both Socialtext and JotSpot are adding an installable product to their offering. However, Confluence may be missing out on the bottom-up, grassroots adoption by business users that both Jot and Socialtext are enjoying – at least until it becomes available on-demand.

And while the Founders did not have the star-power of their competitors 4 years ago, they are getting closer, having just received the 2006 Ernst & Young Eastern Region Young Entrepreneur of the Year award.. Watch the video of the Awards Ceremony here:

Congrat’s, Mike and Scott!

 

post

You Know Wikis Have Arrived When ….

You Know Wikis Have Arrived When …. they become the feature post in your regular junk mail – this time from an Executive Recruiter firm:

What in the World is a “Wiki”?

If you don’t know what a Wiki is, you probably should.
The term “Wiki” refers to both a collaborative site on the web or your company’s intranet/extranet and the software that runs the Wiki.

A wiki is a website designed for collaboration. Unlike a traditional website where pages can only be read, in a wiki everyone can edit, update and append pages with new information, all without knowing HTML, simply by using a MS Word type interface.

Wikis are the latest, greatest tool for group collaboration, project teams, document editing, etc. And, best of all, they are easy to use, affordable, and extremely flexible.

The easiest way to learn more is to click on the link at the end of this section of the newsletter and try it for yourself!

What can you do with a wiki?
Whether you’re at work or at home, you can access and use a wiki. The wiki allows free-form collaboration, but most wiki software providers and hosts also offer structured applications that allow you all kinds of very helpful functionality.

Here are some of the things that can be done (depending on whose software you use and what applications may be available:

  • Create an intranet
    Publish company information, such as news or employee guidelines
  • Project management
    Schedule project deadlines, assign tasks, and define product specifications
  • Document collaboration
    Multiple users author documents with aid of version history
  • Manage a group’s activities
    Utilize event calendars, discussion forums, blogs and other apps
  • Collaborate with virtual teams
    Communicate with remote contractors or clients
  • Track software bugs
    Log defects and build custom queries
  • Call center support
    Access case histories and increase customer support

A wiki can be hosted on your company servers or there are a number of hosted versions available. There are a number of suppliers, each touting advantages over their competitors, of course.

One important aspect of a wiki — it is highly cost- effective and versions/solutions range from those for the smallest teams on the most limited budgets scaling up to full enterprise versions.

If you are unfamiliar with this explosive growth phenomenon, you may want to take a look for yourself. [Company name] has found one supplier offering free trials. It’s pretty neat stuff and has become indispensable in our own operations. Click the link below for a free trial.

This is not a [Company name] product but we have used the free trial ourselves and had no problems, no hassles, and no sales calls. It just takes 30 seconds or so to sign up.


For spam, this is actually pretty good. The original letter pointed to the signup page of one particular provider, and of course the sender forgot to disclose the paid referral relationship … So instead of just one, here’s a list of a few wiki providers:

Confluence and Socialtext are both Enterprise Wiki’s , robust, well-supported, targeting corporate customers.
JotSpot is more geared towards smaller businesses and consumers and in fact it’s a mix of a wiki plus a few basic applications.
Central Desktop is a “wiki without the wiki”, more of a full-featured collaboration platform with calendar, task, project ..etc features.
WetPaint blurs the line between wiki, blog and discussion group, providing an amazingly easy to use interface, but it’s currently at beta stage.

The above list is by far not complete, it’s just a few of the top of my head – feel free to contribute in the comments section.

 

 

post

Software 2006: Wikis Win

(Updated)
Wikis and blogs -social software in general – were the “latent” subject at Software 2006, popping up at several sessions throughout the conference.

In his opening keynote Ray Lane talked about the inter-personal enterprise: collaboration, increased participation through friendlier, better user experience; the user as an individual, “consumer” has to like the software, then will use it, and usage spreads within the company: a pull process, rather than push – the traditional enterprise sales model. This is exactly the model wikis are “sold”, as we discussed earlier. Ray specifically mentioned how useful they found using a wiki at Kleiner Perkins.

Then during the last panel, Toby Redshaw, CIO of Motorola talked about how he installed wikis and blogs: turned it on, decidedly not telling anyone “above” or laterally until it was too late for anyone worried about “control” to interfere. People discovered the new tools, started to use them, and before he knew there were 1900 blogs and 2000 wikis used in Motorola. Grassroots action at it’s best, just like Ray explained. Joe (JotSpot) and Ross (SocialText) could not have asked for a better plug of wikis, just minutes prior to their software showcase.

On the way from this session to the showcase room Ross was showing me his latest baby, Miki, the mobile wiki. One of the conference attendees (Director at a major organization) walked alongside us, overheard the conversation, and jumped in: “where can I get it?” Wow, I think Ross just closed a 30–second sale

There is something funny about these product names, though. Ross just found out that Miki in Irish slang means male genitalia… hm… close .. here’s the Urban Dictionary definition. Never mind, it didn’t hurt Jobby, won’t hurt Miki either. Incidentally, Miki in Hungarian is nickname form for Nicholas, and in Japanese a female name meaning “flower stalk.” Not bad.

The Miki launch was the last announcement of the day, then we headed off for some “Open Source” cocktails and appetizers.

Related posts – Miki seems to enjoy a warm welcome:

Update (4/8): It was fun to see JotSpot and SocialText together – would have been even more fun to see the third (and by the number of enterprise customers definitely not last) product: Confluence by Atlassian.

post

43 Wiki Prank and the Whiteboard Test

Weblogswork is making fun of Ross Mayfield using a wiki for everything. Ok, so it’s really Alex Muse’s idea, check out his story. They set up and CrunchNotes announced the 43 Best Blogs page, which is open for anyone to edit. Of course Ross typically ends up selling / using / donating Socialtext wikis for the right purpose, while this 43thingie is just a mess. I could have my 5 minutes of fame by inserting myself in the #1 position. Not that being a mess is bad … I suppose it’s just a cool prank to get some buzz and attention – otherwise a digg-like voting system would make more sense.

Let’s use this opportunity though to make a point: wikis are a wonderful productivity tool, they help cut down on the flood of email we’re all buried under, reduce “occupational spam” (those unnecessary CC’s, even worse, BCC’s) ..etc…etc…etc. But most importantly, a wiki is for collaboration. Not everything we do is a collaborative effort, and as such, a wiki is not always the best tool to use. Key in picking the right tool is the intention, the desired outcome of the communication.

For ad-hoc, one-to-one, or one-to-some type communication email is still the winner. Blogs are the best for one-to-many regular communication and dialogue. When the value is in the individual contributions, preserving their original content and sequence, traditional forum software is probably the best. Movie-, book-, product reviews are typical examples, for example I would question that Amazon’s ProductWiki is such a good idea. (well, it is, if you enjoy wiki-wars).

The simple “whiteboard-test” helps determine when wikis are really helpful: if ideally you’d like to have all participants of your conversations together in a room, where anyone can walk up to the whiteboard, wipe off content, correct, overwrite what others done until the group collectively reaches the desired outcome, then you should use a wiki. In other words it’s not the debate, the process, the individual arguments that matter, but the synthesis of the collective wisdom. (actually, you get all the other stuff from the change logs). It’s clearly easier to use wikis in a self-controlled environment, like project teams, companies … essentially any team driving towards a common purpose, but Wikipedia is proof that collaboration can be achieved with Pigeonthe open community at large, too.

For everything else, there is always good old pigeon-mail.

Related posts: