Communicating Complex Technical Concepts

We've faced this problem a few times, as we roll out a distributed application across a network of remote locations. A fairly typical challenge is to explain the impact of a technical architecture improvement in a relevant, meaningful way - without resorting to techno-jargon. A good approach includes: Keep it short - Too much detail and you will lose them. Find the balance between enough information to be valuable, but not so much as to be boring Focus on the…

Implementing Intranet on Speed: An Uh-Oh Moment

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…

Implementing Intranet on Speed: The Beginning

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"…

Heisenburg KM

On this site, I've implemented multiple blogs (thoughts, essays, updates) - and it's not because I see many nails for my shiny new hammer. I'm trying out blogging for a couple of different applications / uses ... for example, I'm playing with the updates blog as a test for project status blogging at work. It's a fairly common request - "please keep us up to date with changes, additions, etc." - but that can be labor intensive, and I'm looking…