WikiSym 2008 Opens; New WikiFest Speaker Announcement

Bem-vindo! Welcome to WikiSym! If you are here in Porto, I’m looking forward to seeing you in the WikiFest symposium on Wednesday from 1:30-5:00 (13:30-17:00). We have seven distinguished speakers who will show how organizations like IBM, Boeing, University of Helsinki, //Seibert/Media, and University of Michigan have introduced and grown enterprise wiki use for collaboration, knowledge management, and project mnagement, and more.

In addition to the slate of speakers already announced, there’s one new addition. Holger Junghanns will join WikiFest to discuss enterprise wiki adoption at SAP. Here’s more information about Holger’s talk:

Holger will share his experience of implementing a wiki within the Customer Relationship Management organization of SAP AG. The goal of this project was to promote knowledge transfer among the different teams involved in the development process of SAP’s CRM application. Within a six month timeframe, the project team introduced a wiki as a central point of access for internal knowledge transfer and collaboration within the CRM organization.

At the end of the symposium, all speakers will gather for a panel discussion and joint Q&A. If you’re looking to successfully catalyze enterprise wiki use in your organization, WikiFest will give you the best advice, examples, best practices, and cautions as you get started. If your organization’s wiki adoption is already underway, come learn new ways you can use the wiki, see how to keep employees motivated and excited by the wiki, and share your own experiences during the panel discussion and Q&A. I look forward to seeing you there!

  • Comments Off

Wanna See My Wiki? The Chevron Story Continues

This is from guest author Camille Goksever, an independent Wiki consultant for Chevron, and is the second in a series about enterprise wiki use at Chevron. Be sure to read her first post.

Camille will be speaking about her work at Chevron at the WikiFest Symposium, part of WikiSym 2008 in September.

Creating Mozarts out of elephants wasn’t one of the scenarios I had played out in my head going into this wiki endeavor.  Okay, frankly, the only scenario in my mind involved people moving their fingers furiously in direct contact with a keyboard. 

I had assumed typing out one’s knowledge on a given topic would come naturally to most.  I took for granted my comfort for writing, and projected it onto the wiki team.  Try not to make the same mistake.  Most people hate to write.  I can see now why Stewart dubbed them “Barn Raising” sessions.  Though I can’t imagine building a barn (I had a hard enough time with the shed kit I got from Home Depot), there is the analogous “D’oh, this is really hard” feeling once you get started.

The core wiki team of thirteen grew to about twenty after the first two Barn Raising sessions. Some of the new members were recruited, but a few actually came asking to participate.  I thought that was pretty cool.  However, with such a large group, scheduling a hour-and-a-half Barn Raising session became impossible.  The only option was to schedule the sessions over lunch and provide the grub for free.  This did wonders for attendance!  Never underestimate the power of a free lunch.  Feed them, they will come.

The third Barn Raising session was when I started to see the first seeds of real collaboration.  After stomachs were full, and work began, those who had participated in previous sessions showed the new team members the ins and outs of the wiki tool, such as linking, file uploads, history, etc.  By the end of the session lots of conversations were happening.  People would ask questions from across the room; two or three various people would respond, while the person asking would type the information in the wiki.  Information was being shared freely and collaboratively.  A community began to form.

The wiki was to be officially launched on July 1st, and it was now April.  There were 130 pages created, and only 62 of them had content.  It was time to step on the accelerator and get the Mozart-thing going.  The sessions were only being held every other week.  And forget about getting people to work on the wiki at their desk.  I didn’t want to become the wiki monster (that I had jokingly been dubbed) to make that happen.  The wiki simply needed more fingers tapping it to life.  We went from twenty…to thirty five…then ultimately to fifty members.

By the end of May we grew to 190 pages.  120 pages had a decent amount of content, but a lot needed help.  And there were still topics that needed to be covered, thus more pages that needed creating.  Keeping everyone motivated to give up an hour and a half once a week to work on the wiki became a struggle, even with free lunches.  Within the course of two months I found my inner Tony Robbins.  It may seem cheezy, but the motivational speaking and keeping MY OWN enthusiasm high really went a long way.  Especially with the elephants.  I did a lot of one-on-one cheerleading in those sessions, and in return the wiki got a lot of great content.  It was really important to keep things fun too, which helped in keeping motivation up. 

My boss had the idea of coming up with a wiki slogan and having tshirts printed.  One particularly talented team member came up with a host of slogans.  Here are a few of my favorites:

Oh Wiki you’re so fine
You’re so fine you blow my mind
Oh Wiki
Oh Wiki

My Wiki isn’t icky

Wiki? You can’t handle the Wiki.

The team decided on “Wanna see my wiki?”.  But once we went to the corporate tshirt maker, the slogan was deemed as, uh…”risque and inappropriate”.  So we had to change it to “Do you wiki?”  We were bummed, but we had some good laughs.  Fortunately, my bosses truly rock, and support everything about the wiki, even when it pushes the envelope a little beyond their comfort zones.

My initial concerns of getting the elephants on board and playing like Mozart were tempered towards the final Barn Raising sessions.  Amazingly enough, the elephants just needed a boost in confidence.  This may seem trivial from where you’re sitting.  But think about it…having a person literally by your side, cheering you on to achieve a goal captures your heart and drives your spirit to accomplish that objective.  Hearing the words “You can do this”, is all it takes (most of the time) to overcome your personal road blocks.

I have such endearing respect for the elephants.  They have wisdom beyond my years.  They are humble, they are diginified, and face it…they truly are the main attraction at any given show.

Little did I know, however, that deploying the wiki to the entire Designs Engineering team would turn into a three ring circus.

To be continued.

  • Comments Off

Sure, Wikis Are Cool… But Can They Help My Business?

Lauren Trees wrote an excellent post addressing the question of how wikis can practically help your business. She cited the recent New York Times article on Diplopedia as a successful example of wiki use in an organizational context:

Success stories like this one are particularly valuable because they explain the tangible business benefits behind the slick new tools (and as the article says, “if wikis can work at the State Department, with its fabled bureaucracy and attention to protocol and word choice, they can work anywhere.”) I think most people know what a wiki is by now and are familiar with Wikipedia, but that doesn’t mean they grasp how a wiki would work in an enterprise context.

In the comments, Eric M. Johnson raised the important question of whether one can restrict reading and editing privileges too much, and end up with something that just looks like a content management system. Here’s how I replied:

This is the distinction between what I call “Internet Wikis” (ex: Wikipedia) and “Enterprise Wikis” (ex: the wiki your organization would use internally). The reality inside an organization is that some information does need to be secured, either from reading, editing, or both.

The principle I advise my consulting clients to use with an enterprise wiki is: “Share as much as you can. Secure only what needs to be private.”

I see both Internet and Enterprise wikis are two different types of true wikis. On the internet, being 100% open is necessary to building healthy participation levels from a virtual community. In an organization, the people are already there (employees), so the wiki needs to be focused on allowing some control over access to meet the variety of needs and uses and become indispensable to employees.

To be clear on one thing, though, wikis and content management systems are fundamentally different. A content management system puts restrictions at the end of a process (i.e. people can submit content, but it must be approved before it’s published), while a wiki puts any restrictions at the beginning of a process (i.e., a person has to have edit access to contribute to a wiki page, but once they have access, anything they contribute is immediately published and readable by others).

The chief place where access is important with Enterprise wikis is at the interface between the organization and the outside world. Enterprise wikis typically require an employee to log in (just as they would log in to access their email, the corporate network, internal WiFi, etc.) but beyond that, there’s typically a lot of access and openness between teams, departments, etc.

  • Comments Off

Business Exchange Beta Adds LinkedIn, Opens Registration

Last week, I wrote about BusinessWeek’s new Business Exchange. It’s a site the magazine’s publishers are hoping will engage - and build - its audience by giving them the ability to read, save, and add news items from around the web.

As of this week, the site is now in Beta, and you can register and try it out yourself. While you’re at it, check out Enterprise Wikis (35 news and 75 blog items) and Business Presentations (96 news and 161 blog items), the two topic pages I started.

Among a host of other refinements, perhaps the biggest is the site’s integration with LinkedIn. This connection gives you the ability to have your Business Exchange profile display data directly from your LinkedIn profile, including your current title, executive summary, work experience, and education.

This is a very smart move for two reasons. First, it saves time and duplication of data because your Business Exchange profile isn’t just another isolated profile that has to be built and updated manually. Busy workers will appreciate this.

Second, it’s a sensible connection between two complimentary services. LinkedIn wants to be the hub for your professional network, and Business Exchange wants to be the hub for professional knowledge sharing. Bringing the two together is a great way to unlock greater value from each.

If you’re wondering about the process to connect your LinkedIn and Business Exchange profiles, it’s very smooth and well thought-out. If you already have a Business Exchange profile, simply click on the link to edit your profile and you’ll be offered the option to enter your LinkedIn login information. That’s it!

If you’re new to Business Exchange, you can connect your LinkedIn profile right when you register. It’s the first option on the registration form.

The bottom line: Business Exchange is shaping up to be a formidable, and useful, business social networking and information exchange site. BusinessWeek appears to have learned a lot from the shortcomings of other social bookmarking and networking sites, and Business Exchange is benefiting from that.

  • Comments Off

Quoted in AMD Accelerate: “time for companies to ‘wiki up’”


I’m quoted in a new article from AMD Accelerate - Web 2.0: It’s time for companies to ‘wiki up’:

Wikis are popular because they have certain advantages over e-mail, says Stewart Mader, a wiki consultant and author of two books, Wikipatterns and Using Wiki in Education. He also writes a blog, Grow Your Wiki.

“Each new e-mail message can be an interruption, and the fact that a separate copy goes to each person means that it isolates people from each other,” says Mader. “By contrast, a wiki pulls people in to look at content—on a single, shared page—that a whole team can edit. This streamlines collaboration and builds a stronger, more cohesive community.”

  • Comments Off

Effective Project Management Using a Wiki - Next Week!

I’ll be in Europe in early September for WikiSym 2008 (Porto, Portugal - 8-10 September), but before I get to Porto I’ll be stopping in the UK to give a workshop in Brighton.

Evening Gathering - 3rd September

On 3rd September from 7-9PM, the Whuffie Club is holding an evening gathering at The Werks (Map). I’ll conduct a short session on wiki use in organizations, answer questions, and then we’ll have a mixer afterward. Sign up for 3rd September

Workshop - 4th September

On 4th September at 9:30AM, I’ll be conducting a half-day workshop at The Werks on Effective Project Management Using a Wiki. If you’ve been thinking about using a wiki, are just getting started with one, or want to maximize existing wiki use, this is an excellent opportunity for you and your team to learn how a wiki can help you manage projects.

Teams can use a wiki to organize and work on critical documents and project plans. It lets people work more efficiently between face to face meetings and becomes a magnet for all the information relevant to a project. This workshop will show you how to:

  • Organize your project on a wiki
  • Help your team make the change from trading emails and attachments to gathering, building, and editing information on the wiki
  • Manage everything related to the project, including background research, notes, URLs, timesheets, meetings agendas & minutes, action items, and finished documents, presentations, and files

Sponsors:

social8.co.uk

Register

If you have any difficulty registering, please let me know.
This page requires frame support. Please use a browser that supports frames.

  • Comments Off

Quoted in Edutopia Magazine: What’s Next: Ten Predictions for the Future of Public Education

The August/September 2008 issue of Edutopia Magazine is out, and I’m quoted in the feature What’s Next 2008: Ten Predictions for the Future of Public Education. Wikis are number 7 on the list, and Grace Rubenstein interviewed me for The Way of the Wiki: Building Online Creativity and Cooperation. Here’s a brief excerpt:

it allows for asynchronous cooperation, so one student can work on a group project in the afternoon, one in the evening, and one at night, and each will build on what the previous one did. Unbound from fixed meeting times, says Mader, each team member contributes when she’s at her best.

  • Comments Off

5 Effective Wiki Uses - my latest article, in Website Magazine

The August issue of Website Magazine is out, and it includes an article I wrote: 5 Effective Wiki Uses and How Companies Benefit From Them. Here’s a brief excerpt:

A wiki can be especially useful for commonly needed information, like FAQ, guidelines, HR or purchasing policies. Editing permissions can be set so those responsible for these policies have the ability to edit them as needed and everyone else can read them. This eliminates the need to distribute paper copies of policies each time a change is made. Instead, the HR department can simply send an email announcing changes, with a link to the full policy page on the wiki.

Eliminating all that paper is also a good way to save money, fuel & shipping expenses, and do something to ease your organization’s impact on the environment.

  • Comments Off

Interview with me on the Front Page of Campus Technology

Linda Briggs interviewed me last week for an article on wiki uses in higher ed, and today it’s on the front page of the Campus Technology web site.

  • Comments Off
Next Page »