ThoughtFarmer finalist for Intranet Journal Product of the Year

Intranet Journal Product of the YearThoughtFarmer is a finalist for Intranet Journal’s Product of the Year in the “Document Management / Collaboration Product” category. Other finalists are:

If you’re a ThoughtFarmer fan, please put in a vote for us!

6 Tips for a Successful Wiki Pilot

Prior to a company-wide deployment of a new wiki intranet, many companies conduct a pilot to an initial group of users. Here are a few suggestions on making that pilot a success.

1. Choose the right group

Size: Don’t make your pilot too big, or it will become as big a job as launching to the whole company. But don’t make it too small, either: You need enough people adding content to make it interesting. 20 to 50 people is probably good.

Attitude: Choose keeners — people who aren’t afraid to try new things or to use new technology. Choose people that will be enthusiastic about the potential for open collaboration at your company.

Seniority: Try to get one or more people from the senior team to actively participate in the pilot. If they set the example, the rest of the pilot group will be more likely to actively participate and view the pilot as important.

2. Set up a basic information structure

Blank slate = bad. No one knows what to do with a blank wiki. So set yours up with a basic navigation structure.

Sample top-level navigation structure:

  • People (or Staff Directory)
  • Locations
  • Projects
  • Departments
  • Tools & Links

You might also try building out the information structure underneath some of the top-level items:

Departments

  • Finance
  • HR
  • IT
  • R&D
  • Sales & Marketing

Caution: Be careful not to be too granular in the way you define the initial information structure, or your wiki might seem too restrictive. It’s easy to move pages if you need to subdivide or rearrange sections in the future.

3. Populate some initial content

Users learn by example. If users see lots of examples of how others have populated content, they find it easy to imitate. Wikis are generally easy to use — as long as users see that something is possible, they can usually figure out how to do it on their own.

Users. User profiles are a central part of any intranet. Populate them with an initial import from your directory system, importing as much data as you have available.

Barnraising. You can populate a whack of content in a single day. Try getting 4 or 5 people together for an all-day barnraising.

Give users a reason to return. In the early stages of the pilot, make sure there’s something new on the home page every single day. News items, polls or the cafeteria lunch menu work well for this.

4. Set up email notifications

Email notifications: Many wiki systems can send you an email when someone responds to your comment or edits a page you’ve created. Make sure these notifications are enabled — they keep online conversations flowing and drive repeat traffic to the wiki.

Alternatively, you can rely on RSS feeds for these notifications. But RSS may still be poorly used or understood by many people in your pilot group.

5. Assign tasks to pilot group

Give your pilot group something specific to accomplish with your wiki. Ideas:

  1. Add a photo of yourself and detailed background information to your profile
  2. Use the wiki to share the agenda of your next meeting
  3. Forward a valuable email thread to the wiki (if it supports automatic page creation from emails)

6. Promote, launch and follow up

Promote. Prior to the pilot, send several email communications to your pilot group to get them excited about participating.

Launch. Have an event to launch the pilot. If you’re in a single office, reserve a boardroom, do a short demo, assign tasks, and eat some doughnuts. If you’re in several offices, launch via a web conference.

Follow up. Schedule group or individual follow-up meetings for the week following the pilot launch. See how users are doing with their tasks, and answer their questions. A weekly or biweekly group meeting to review progress will help keep things moving along.

Other resources

WikiPatterns is full of great suggestions on helping a wiki succeed in a corporate environment.

Off to London & Dublin

I’m making my semi-annual pilgrimage to London this weekend.

I’ll be visiting current and potential ThoughtFarmer clients as well as social software consultants. Schedule:

* Monday, Nov 19: London
* Tuesday, Nov 20: London
* Wednesday, Nov 21: Dublin
* Thursday, Nov 22: London

Are you a social software consultant? Let’s do coffee. Shoot me a note at cmcgrath@thoughtfarmer.com.

ThoughtFarmer vs. SLATES: Enterprise 2.0 compliancy

In his seminal article on Enterprise 2.0, professor Andrew McAfee lays out the six components of next-generation enterprise collaboration platforms:

S - Search

L - Links
A - Authoring
T - Tags
E - Extensions
S - Signals

How does ThoughtFarmer, my soon-to-be-world-famous wiki intranet system, stack up?

Search

“Users are increasingly bypassing [navigation] in favor of keyword searches.”

ThoughtFarmer has a fast, accurate, configurable search engine.

Search in ThoughtFarmer

Links

“Links are an excellent guide to what’s important… Many people have to be given the ability to build links.”

All ThoughtFarmer users can easily embed links in text, or even create directories of links.

Easily create links

Authoring

“When authoring tools are deployed… the intranet shifts from being the creation of a few to being the constantly updated, interlinked work of many.”

All ThoughtFarmer users can create and edit content with a few clicks.

Authorship - Create and edit content in a few clicks

Tags

“[Folksonomies] reflect the information structures and relationships that people actually use, instead of the ones that were planned for them in advance.”

All ThoughtFarmer users can apply tags to pages and documents.

Tags - Apply tags to pages and documents

Extensions

“Moderately ’smart’ computers take tagging one step further by automating some of the work of categorization and pattern matching.”

ThoughtFarmer tagging enables faceted browsing — quickly mine through lists of thousands of pages by progressively applying tags.

Extensions - ThoughtFarmer tags enabled faceted browse

Signals

“The final element of the SLATES infrastructure is technology to signal users when new content of interest appears.”

ThoughtFarmer alerts you to new content via RSS or email notifications.

Signals: RSS and Email notifications

ThoughtFarmer is 100% SLATES-compliant.

But is it FLATNESSES-compliant? I’ll address this in a future blog post.

My live demo at Office 2.0, San Francisco

Watch me be all hyped and nervous while demoing the latest version of ThoughtFarmer at the Office 2.0 Conference in San Francisco.

Sam sings “My Bonnie Lies Over the Ocean”

Want to buy a house in Nelson?

Dining room french doors

Gina’s parents are selling their house. They wanted to avoid the real estate commission, so I was nominated to do all the internet-based private-sale busywork. That’s okay I guess. I suppose I’m a professional point-and-clicker, and watching my inlaws navigate web apps is painful. I can’t subject them to that.

So I took some photos, built a little web page for them, and listed it on 6 or 7 different websites.

Want to live in Nelson?

Home for sale in Nelson: $439,000

Pussycat, pussycat, where have you been?

Gord and Chris in LondonI’ve been to London to visit the Queen.

Okay, I didn’t visit the Queen, but I saw the Thames, Tower Bridge, Trafalgar Square, The Eye, Notting Hill, Big Ben, and the Gherkin. More importantly, I met with Euan Semple, Headshift, the Strange Attractors and NESTA (our latest ThoughtFarmer client).

Gord took all the pictures — see his Flickr photoset ThoughtFarmer Goes to London.

Two tools: WD-40 and duct tape

Saw on Euan Semple’s blog:

You need only two tools: WD-40 and duct tape.

If it doesn’t move and it should, use WD-40.

If it moves and shouldn’t, use the duct tape.

- Via Ming

Moved home to Nelson

After almost ten years in St. Louis, Sarajevo, and Vancouver, Gina and I moved back home to sleepy little Nelson, BC. There’s 10,000 people here. No traffic jams. No smog. No noise. It’s perfect.

We bought a tidy little house, kind of like the one I grew up in, with a huge back yard and about 100 trees. We’ve painted, put down hardwood, and bashed out a few walls. Now we’re getting a soundproof office put in downstairs so the kids can play while I work.

I’ve started playing hockey again, after a 12-year hiatus. I’m still not any good, but I’m having a lot of fun.