Musings on the intersection of training and technology

Monday, July 03, 2006

Living in Possibilities

Nothing like a really beautiful, sunny weekend spent playing with my little girl to remind me not to take myself too seriously. It is always easy to look back over something and think of things that would have been nice to improve. Today I'd rather reflect on what I've gained, and have yet to gain from this experience.

I am realizing that it is not my strength, nor, fortunately, my job to be so intimate with technology to be able to answer the question "How do you make it...?" It is both to be able to ask, "What about...?" And then to brainstorm with some really bright people and turn "how do you make it?" over to those who really love to answer that kind of question. In that context, I think this unworkshop has been quite helpful. It has given me additional exposure to technologies that were already on my radar, and brought them into crisper focus. It has provided me with a filtered set of really great resources/examples that I will revisit and peruse and perhaps even contribute to, assuming the wiki persists. And it has delivered on its greatest promise, that which drew me to the unworkshop in the first place: access to a community of people to share ideas with. I think I have not taken full advantage of this yet, but I believe that, like all relationships, this is something that will evolve. This has been such a unique way to make connections that I imagine that I will continue to reach out to my peers even after the pretext for our conversations has ended. In fact, I expect I'll reach out to some of the people I haven't yet had a chance to talk with, and, given access to additional unworkshop contact lists, perhaps even to past and to future participants...

Sometimes I'm a bit slow out of the gate, but I'm a hanger-on. It's a marathon, not a sprint.

Okay, on to the last assignment: three practical applications of what we've been discussing. In the spirit of "what about...?" I'll tackle this from the perspective of how I'd love to see these technologies applied, whether or not the technologies are there yet.

1) CoPs Close to the Heart

Provide all unworkshop participants, past, present, and future, ongoing access to the unworkshop wiki. Consolidate the profiles pages from the various unworkshops and add the following info for each participant:

  • Column for which unworkshop they attended
  • Links to each person's blogs

Allow people to "opt out" or to delete their info from the CoP.

2) Tagging in the Business World

A lot of my clients have extranet portals for their channel partners. Their extranet tends to be one of their primary ways of communicating with these audiences. Sometimes the portals are well organized and structured. Often they are a mess. However, no matter how well thought out, partners often complain that it's hard to find what they need. It would be great if tagging could be set up behind the firewall to provide:

  • Ability to tag content on the portal using your own terms.
  • Ability to create tags from phrases (more than one word)
  • Option to share tags publicly, or to keep tags private
  • "delicious" like tagging capabilities: select from tags commonly used by other users and/or create your own; provide access to tag clouds and most commonly tagged content; provide ability to view other users tags (if they have opted to share their tags)
  • Formal metadata provided as options to choose from when tagging
  • Regularly spidered documents and auto-generated tags from commonly used terms in the content
  • Easy (one-click) ability for users to "hide" or "demote" or "archive" objects from appearing in their search results (if content is dated or not relevant)
  • Ability to "block" tags from specific users

3) Social Networking and Wikis on the Job

I've used wikis on the job for specific projects and they tend to require a lot of care and feeding. Even with it, my experience has shown that they are not readily adopted. Perhaps the one we used just wasn't user-friendly enough. Perhaps it was because we tried to use it on projects where participants were from multiple companies, which made it all the more difficult to encourage adoption. Perhaps it was largely because it was a new technology, and a tangential one, and it was easier and faster for people to fall back on email. Whatever the reason, as the project work got thicker, and the deadlines closer together, the wiki was quickly abandoned. Yet, I'm not ready to give up on wikis. I think they have incredible potential, and look forward to watching how they evolve and become more widely adopted.

I was encouraged to hear from Peter Kaminski on the success his company has seen in encouraging adoption of their enterprise wiki. Some his comments that stood out to me is that wikis tend to seem harder to use then they really are. Though perception in likely reality in this case, it bodes well for wikis if they can just look and feel more user-friendly. Peter also spoke of how his company encourages the use of multiple wikis, almost used like team sites or email distribution lists, as a way to filter the content and the traffic so that it remains most relevant to the target audience, yet still available for others, as needed. And he referred to the way he personally tends to spend a lot of time on the "recently edited" sections, an approach which seems to lend itself to 1) a strategy for keeping up with the flow and 2) a natural filter that allows dated information to become "archived" as people simply stop touching it. Yet it also spoke to me of the great need to "teach" people to be successful wiki users in order to get the most out of them.

Here are some thoughts on easing the business world into wiki-ways:

  • First, create a social networking wiki internal to the company. Allow people to create their own profile and encourage them to include info about their work experience and interests, as well as comments about appropriate personal interests.
  • Include reviewing the corporate wiki and creating your own wiki profile as part of the week 1 onboarding for all new hires.
  • Next, create organizational team pages in the wiki that describe the group, their mission, processes, access to relevant tools and templates, etc.
  • Evolve to creating cross-functional team pages as part of a project launch to get people on board and give them a central place to keep up to date on the project.
  • Create wiki pages for each of the company‚Äôs clients.
  • Slap on a blog for internal communications to keep people up to date with company news.
  • Add access to podcasts, or recorded meetings, etc.
  • Allow people to set alerts for sections or pages.
  • Push alerts to specific lists of users, such as updated product info out to the sales team, or news of outages to the support desk.

Eventually I'm looking for the wiki to replace the intranet as people become more accustomed to its nimble nature and begin to expect content to evolve more organically and democratically. Keepers of the original intranet could be redeployed as the wiki gardeners to keep it weeded, and as mentors to help people learn to use it effectively.

Here are some things I would like to see integrated with wikis (perhaps some already are?):

  • Wysiwyg editor - including spell-check - no need for users to see or touch html
  • Integrate wiki with a data management tool, so that documents can be pulled from the dm repository rather than stored "within" the wiki. Would provide access to the most current version, as well as the ability to roll back to prior versions.
  • Layer tagging onto a wiki and create a knowledge management tool (personal or otherwise) that is really dynamic.

2 Comments:

Blogger jay said...

Beth, that's dynamite post. Unless you tell me otherwise, I want to include parts of it in our wiki. The how-to-implement is the most lucid wiki intro I've ever encountered.

10:21 PM

 
Blogger Beth Chm... said...

Thanks Jay. Please feel free to reuse whatever sections are relevant. :-)

8:43 AM

 

Post a Comment

<< Home