When introducing collaboration tools to an organization - creating the corporate intranet, defining project sites in Sharepoint, etc. - there are multiple skills you must master - well, at least get better at. You need to capture the ideas and communicate the data such that your target reader understands what you are trying to convey - but you also have to help them locate it in the first place. Three personas you'll need to adopt, three sets of skills to…
"What will you do with that car if you actually catch it?" -- what the cat asked the dog (from the Chicago Reader, circa 1989) So you've gone all "Enterprise 2.0", spinning up a wiki, a blog, and a SharePoint or Drupal server inside your firewall. Now what happens? The groundswell of interest in "cool tools" brings a wave of users and a burst of feed reader activity - for a few weeks. Before long, however, the organization will get…
After my last post ... more experiences at work, and observations in the trades and other blogs, regarding Web 2.0 tools for use in business ... Improving Knowledge Capture is Half the Battle In last week's Information Week magazine, the story of Procter & Gamble's push towards collaboration - the tools can meet some resistance. A critical quote: We consistently hear that information posted to the intranet is incremental work. Similarly, in my organization, I have folks continuing to send…
Trying to provide a simple, flexible search capability for your organization's reams of historical documents? Using a project process that generates the typical stacks of documents, databases full of status reports and issues, and other "stuff"? It's important to think about the knowledge we are generating, and the best way to capture that knowledge – and not worry too much about how we’re going to search through those deliverables. There is no one way to capture / store different kinds…
The outgoing intranet was nice, in that it gave content owners the ability to control what was visible / available. Unfortunately, we've come to discover that a number of corporate services areas (Safety, HR, Transportation, etc.) in our organization used the intranet but never took part of the content management (CM) - it all came "from above". Basically, these folks are about to get a "crash course" in CM and Knowledge Management (KM), albeit in small bites. When you read…
This week, we're kicking off a new project, implementing an intranet / portal for our newly independent company. I'm fascinated at how the "state of the art " has moved forward so much since the "old days" of the 90's. This is actually my third or fourth cut at an application like this (depending on how you define "portal"), and I'm sure it's going a bit faster simply because we're skipping over some portal design and admin process "dead ends"…