thoughts on knowledge logging

K-Log Pilot Recap

I hate to call these “k-logs” since pronunciation seems to make them sound less than useful.

Many were in agreement that the k-log would be a great vehicle for senior execs to share wisdom with others in the company. Oddly enough, those same people were uncertain whether they as individuals would have information that would be valuable outside of their team. Somewhat contradictory, however, was a comment made by one user (and echoed by others) that it would be really nice to learn what was going on “on the other side of the house.”

I found it interesting that some felt a weblog was a useful thing for senior execs to use but that they themselves didn’t have anything important enough to publish. Sounds like a case study for some organization psychologists . . . .

Found this at Holbrook’s site.

And this reminds me of nothing so much as the Five Blind Men and the Elephant . . .

Given the flexible nature of weblogs (unlike structured applications, weblogs really can be what you want them to be), it wasn’t entirely surprising to see users shape their own expectations in testing out the software:

* A senior developer saw Radio as a great annotated bookmark tool – a way to save URLs and provide his own commentary for others in his team.
* A marketing manager saw Radio mostly as a clipping service – the ability to snag snippets from other web sites to save to her own site.
* A sales person used Radio to distribute industry news relevant to other sales people.
* A QA tester who frequently lunches with customers in training often provided recaps of discussions at lunch – sharing the customers’ interests and inquiries.