confluence Archives - Page 4 of 4

You Know Wikis Have Arrived When ….

Posted on June 1, 2006 ·

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.

Filed Under: Blogging, Collaboration, Marketing / PR, Personal Productivity, Software · Tagged: atlassian, Central Desktop, Collaboration, confluence, intranet, Jotspot, socialtext, wetpaint, wiki, wikis

Software 2006: Wikis Win

Posted on April 6, 2006 ·

(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.

Filed Under: Bay Area, Collaboration, Enterprise Software, Personal Productivity, SaaS, Social Networking, Software, Startups · Tagged: atlassian, confluence, Jotspot, miki, Social Software, socialtext, software2006, wiki, wikis

Wikis are the Instant Intranet

Posted on March 4, 2006 ·

(Updated)

Since I received a few questions after my post: 43 Wiki Prank and the Whiteboard Test, I though I should add a bit of clarification. The underlying thought in that article was to pick the right tool for the right situation, and the whiteboard-test is just one trick to differentiate when Wiki’s are helpful vs. Forum, Blog ..etc software. It’s by far not the only situation when a wiki is invaluable.

Another example is setting up a living, breathing Intranet, one that people can actually use. Anybody who works in large corporations probably thinks of the IntraNet as a one-way communication channel for Management to talk (down) to employees. Getting your own content in? Forget it! Even when I was VP in a mid-sized organization and did not have wait for approval, I still had to talk to the IT Director, wait for him to fit it in his team’s schedule, then tell him what was wrong when my content finally showed up.

It does not have to be this way! Companies “own” (well, at least part of the day) the intellectual capacity of their employees, so why not put it to work? Even in the large corporate environment a wiki can be a lively collaborative addition to the Intranet (see the wiki effect by Ross), but for smaller, nimble, less hierarchical business a wiki is The Intranet.

At a much smaller organization I wanted to introduce a wiki for collaboration, for all the reasons explained in the video below. The company was a bit more old-fashioned, not exactly the early-adopter type. I expected some resistance against something with a geeky-funny name like wiki… so I simply announced we’ll be creating an editable Intranet. People started to use it from day 1, and few cared that the thingie behind is called a wiki.

David Terrar describes a somewhat similar story here.

Finally, the excellent video by JotSpot Founder Joe Kraus.

43 Wiki Prank and the Whiteboard Test

Posted on February 28, 2006 ·

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 the open community at large, too.

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

Filed Under: Blogging, Collaboration, Social Networking, Software · Tagged: 43 Best Blogs, 43 Wiki, atlassian, Collaboration, confluence, Jotspot, ProductWiki, socialtext, Weblogswork, wiki, wikis

You Know Wikis Have Arrived When ….

Recent Posts

Recent Comments