I've written about using RSS for internal as well as external information sources. This past week, I found a couple of interesting tidbits in my feed reader (behind the firewall) ... Eyes on the Skies: It's that time of year again; oil price volatility will continue if any big storms create problems for refineries in the Gulf - something new to keep an eye on. Never fear - our friends at NOAA kindly put out an RSS feed for storm…
Lots of organizations have to deal with the challenge of implementing standard work and best practices over physical distances. With sales offices, distribution centers, and manufacturing locations scattered across the country, what's the best way to get people who know their stuff to collaborate on process improvement - and then take that knowledge back to their home office? While wrestling with this challenge, one executive I know preemptively ruled out videoconferencing. It's a common suggestion, but the general feeling was…
I sat in on the report-out session from a kaizen event this week, and something occurred to me as I reviewed a ton of interesting findings in a very short time ... Best Practice Self-contained deliverables are the most powerful tools for knowledge knowledge transfer you can have in your organization. I'm talking about a document that stands on its own, and effectively communicates an idea without needing the author nearby to explain anything. The topic doesn't matter - conceptual…
Different areas of our IT department are using internal blogs, wikis, and collaboration spaces, with varying degrees of participation, readership, and success. Some observations: Blogging is Easy ... The blogs and wiki(s) have effectively removed the hassles of capturing and distributing information quickly. One important early decision was to not implement an editorial approval process for the wiki, and most blogs are wide open for public comments. No more excuses or complaints about a lack of documentation; if the explanation…
I've written about the basic project proposal (for consulting groups) or charter (for internal IT) in the past. The point of any project summary document is to tee up the what and the why, using an outline like this: Description: What are we trying to accomplish here? What is our ultimate goal? Objectives: These are project objectives, not business objectives. How will we know we are done? Benefits: Why should we consider doing this? What are we getting? Alternatives: Are…
no, that's not a typo ... Preamble: This starts out sounding like a diary entry, but some interesting wiki-focused observations are found below - including metrics! Catching up on old items in my feed reader: Back in November, TechCrunch had an item on AboutUs, which at first glance looked at little self-referential, a web site on web sites. Digging in a bit more - we find it's a wiki about web sites, which is still seemed a tiny bit redundant,…
Knowledge Management (KM) may sound amorphous, but here are three specific examples of real business value generated when basic KM principles are applied.
Project managers must communicate the trade-off between additional functionality and the time required to fully test the work. Don't assume testing will be completed - it's something that takes time!
Some will be taken a bit by surprise to read the title of this post; we have implemented a wiki in our group at work, and I have the evangelist role in promoting the tool. Still, a recent "event" brought home the fact that wikis are not the silver bullets that some breathless articles may make them out to be. To be fair, Hickins' article does call out the "law of large numbers", although the idea is buried in the…
McDonald sent a nice comment on my last post - he's writing a lot about project management lately, and we even chatted about some research he's doing around boomer flight. Since I don't get a ton of comments, I thought I'd respond with a post, instead. He poses the question: I am wondering if documentation of the communications associated with coding and testing (emails, archiving of successive release of code, meeting recordings, archiving of test results, etc.) can in any…