Amazing. After years ago suggesting that our newsletter publications could/should be written more like newspaper or magazine-style columns or weblogs, there is now an interest in looking now at the weblog model to become part of our information services. If you weren't aware, I work for a corporate library/information services organization. Maybe this is because business literature about RSS is finally reaching business decision makers or because Gartner or Forrester said something about RSS. Could also be because people are noticing that customers inside the firewall are using weblogs to find/share sources of information with their peers. I don't know. Whatever the reason, RSS and weblogging have surfaced in conversations I'm being asked to lead.
The person I'm talking to is specifically (and perhaps mainly) interested in understanding weblogs as sources for current knowledge in subject areas of interest to our users. We already provide RSS feeds to many of our databases. At a basic level what we offer is much like Feedster, and I'm proud to say we implemented it before Feedster came out, but it doesn't do as much as that great application. Ours simply allows you to execute as simple or advanced a search as you want on a source, e.g. Factiva News or our Internal Technical Documents databases, and we can give you a URL to fetch those results as RSS. The RSS can be sorted by whatever methods the database offers (e.g. date, relevance). But the focus now is on looking at some of those non-print sources that webloggers follow as a source of information for our users. One of the thoughts associated with this is selecting a few of our team of indexers and talking to them about the prospect of researching and following these sources in order to begin blogging within their subject areas of interest.
A few years after I first liked the idea of indexers/newsletter writers as columnists or bloggers, I find myself all too aware of the many obstacles to getting this to work. They're mostly to do with individual fear and resistance to being visible within the company. Sounds sad, but people are afraid of being seen as and outwardly thinking as individuals in large corporations. I've read in Jim McGee's and Lila Effimova's blogs about cultural and organizational aspects as obstacles to knowledge management using weblogs, and I'm inclined to agree that if you want to tap the potential of the knowledge worker to create/contribute/share knowledge, you have to spend a lot of time making sure the environment makes them feel enabled/empowered/rewarded for doing so. I think there is value of having knowledge loggers of different types: the pointer, the one who finds the most recent resources and blogs them frequently; the teacher, the one who finds the gems and decodes them into practical information in jargonless language you can use; the pundit, who finds the most relevant issues and ideas and through wisdom and experience creates understanding and opportunity. There are more types of bloggers, I'm sure, but the fundamental idea here is that bloggers, through continuous exposure to the right literature in a subject area, become potential authorities with time and experience. Over time these reporters can become thinkers and pundits if they feel their understanding of a subject area is strong enough to begin synthesizing the ideas in what they've read into new ideas of their own. Of course, it takes the right person as well -- someone with previous subject area experience or exposure makes a better blogger. But the question remains for me, can you nurture an environment that helps subject area experts find their voice in becoming information authorities?
The person leading this effort/exploration is focussed on getting RSS sources integrated into our indexing processes and thinking about weblogging as a vehicle for delivery. She's rightly concerned that we're relying on old methods of information delivery -- indexed content from published sources go into standard databases, get delivered via newsletters, portals, etc. -- and she's worried that we're not tapping into sources that are clearly viewed as valuable by some of our users. Specifically, the users who maintain subject area weblogs are reading/pointing to more news from C|Net and various blogs than they are published sources, e.g. journals. Think of ideas like the invisible college where publishing is often so far down the line that by the time important material gets published, the publishers may have forged ahead past the published material onto new areas. The lost time in knowledge share/exchange is important, here. More important to me, however, than the mere siphoning of external weblog information into information systems is the idea that provocative or interesting voices can emerge from this effort and be used by the company to help further it's organizational knowledge of relevant subjects. If we can carefully engineer this situation to avoid the obstacles, the potential for helping people feel completely useful to themselves and to the company is immense here. Try as you might, you can't measure that in terms of information work productivity.
This is how I feel with my small contribution to the fields I hold conversations with as a weblogger. Some questions for me remain, when thinking about the prospects of this project. I wonder how you identify potentially good webloggers -- we have at least 2 in mind -- and how do foster the right environment for them to grow into that role if they want it? When I started writing iaslash I did so with no ideas that people would actually care about my opinions about information architecture. I did have them, but I never intended to put them out there. I wanted to simply report. To summarize or abstract what I was reading with a sterile indexer's voice. I found that it was far too boring to do that for long and started inserting my opinions once in a while, realizing that I'd strayed from the model that began that blog. And I found an incredible amount of pleasure in inserting my voice into my reporting. The interesting outcome was that once in a while people would respond. I was happy to start getting into conversations with the people that I respected as the authorities or pundits in this field. I wasn't just indexing anymore, I was participating in conversations and people were taking me, my opinions and experience, very seriously. Somehow, I even got lumped in with the userati, and even got referred to as a pundit by some people. That's far from the truth, but what's important is that I gained from this new experience the confidence to let my voice be heard. And this is the thing that I wonder about when it comes to asking librarians in my organization to lend their voices to subject area blogs.
Can indexers be made comfortable enough to begin to have voices as subject area experts -- to become bloggers? I don't know. Some things have to happen for this to come into being. The environment has to be right. Potential bloggers can't be forced into this role, but must be willing to fall gently into it. Potential bloggers should be selected among those that have the appropriate skills and subject area exposure for the topics you want to cover. If these (and other important factors that I haven't identified yet) are in place, perhaps this can happen. Perhaps we can employ librarians/indexers as bloggers. I don't know. I'm afraid of this approach because it doesn't seem organic enough. If we have the right people willing to engage in this conversation about library bloggers it may happen. Only time will tell. I may have more to say about this process as I have opportunity to be a part of it. Sounds like an interesting way to join my personal interests in weblogging with some practical use in my organization. I'll try to capture my thoughts if and as they occur.
Comments
03/04/04 @ 00:05
Personally, and also in the context of my company, I've experienced how weblogging has positively 'infected' a core group of people to galvanise along a common objective. In the second week that we started our internal blogging trial, there was an 5-fold increase in postings. I was also pleasantly surprised at the topics discussed.
At that time, I became interested in how weblogging actually contributes in an organisation. This was when I chance upon something called "social constructionism" - a learning phase where people start to 'construct' (read 'blog') something out of their knowledge and share it with a social group. I discovered that, in my own blogging experience, I would go through a learning cycle starting with constructivsm (a lot of reading other people's blog while assimilating one's own ideas, concepts and know-how), constructionism (attempts at creating something that represents one's own interpretation of knowledge) and social constructionism.
Perhaps, one way to motivate employees would be to highlight weblogging as a "Personal Learning Platform".
03/08/04 @ 18:23
I've been consulting with an R&D lab for the past four months putting together some communications / pseudo-KM tools using Drupal.
I think you're spot-on re: the process having to be more organic. Our recent experience validates that, anyway. The situation here is we're an R&D lab (one of many) with a lot of knowledge-workers in disparate groups, with significant IP / propriety issues. And some political ones. They're all quite real and need to be acknowledged, functionally, within the communications systems -- or they simply won't be used.
Blogging makes all the sense in the world for a group/groups of workers like that, but identifying the attendant requirements for usability -- and I mean usability entirely independent of design -- has been challenging. The "indexers" in this case are already comfortable as subject area experts -- mostly postgrad researchers, PhD's, etc -- but, getting them comfortable with the idea of blogging the activity is another matter.
One of the most important things we've had to establish is -- in drupal-speak -- node level permissions. Folks are really reluctant to let their research notes and thoughts-of-the-moment fly when they consider that a sponsoring representative of an external business unit might read that and take it out of context, for example. They're also reluctant to share notes in a manner that might expose them to individuals within a competing group within the org.
We've come up with a short-term solution of establishing content scope on a per-node basis, and tying it to a hierarchy of roles. Leaves much to be desired, but addresses immediate concerns. Now, we're faced with the potential issue of extending that to RSS, as we ponder aggregating multiple blog installations.
We're also faced with the possible need to integrate vocabularies. I recall reading through the Drupal aggregator module's comments that at some point taxonomies would be exportable as feeds -- that may offer us a foundation for addressing that issue.
Also, a note on context: one of the things I've found raises the interest level -- and thereby the return visit to the resource / tool, is context-aware "information value adds". Integrating external RSS feeds, automatic Google queries to the current article (node) title, and other things -- like related links from Waypath -- elicits a favorable response from the end-user, and they tend to find their way back sooner as a result, which can leadthem to gain some add'l comfort with the blogging aspect of it through repeated exposure.
Overall the process has been enlightening if a bit frustrating, insofar as a few of us have a clearer larger vision for this, but there's no internal mandate to really build it out. Looks like you have a stronger opportunity.
Interested to hear how this works out, and good luck with it.
03/09/04 @ 14:32
Thanks for telling me about your experience, Benjamin. Finding conversations about how people are approaching weblogging -- and in particular with community or group-oriented use in mind -- is extremely valuable to hear/read, but also difficult to find. I find that there are enough people like myself who muse about what seems to make most sense. We even discuss the softer and more problematic things related to blogging and KM such as the environmental/cultural/political aspects that affect use and sustainability. But finding people strategizing an approach to weblogging and talking about experiences over time is hard to come by. Over time I think we might see the case studies emerging in conference proceedings, etc., but for people looking to learn from others' experiences now, much of the strategy must be based on deep understanding of blog authors as users and the audience as users. User research and strategy go hand in hand here.
My group has only now started trying to discuss a few things: 1) the value of finding/publishing authoritative RSS sources to our clientelle, 2) the value of using weblogs as a medium for distributing this information.
Clearly at issue for a library is the collection of scope. Is the collection of RSS sources within our purview? We do already collect links in various forms, so the question is whether RSS sources make sense for inclusion. How do we integrate this information into our sources? Do we merely present the URLs for RSS feeds along side other "See also" resources we list in pages of our directory? For example, should we list a particular WiFi weblog as a resource on our WiFi topic page? Should we be collecting/aggregating data from feeds and parsing/indexing the data in the feeds and presenting them on the page as we do records from our News sources or various internal document repositories? How does this information relate to the topical newsletters we produce? To the alerts/custom topic trackers (Special Delivery of Information service)?
These are big questions. At this point, we seem to need to focus on the types of resources out there and to continue the discussion of whether there is enough of value that our customers need to see that they can't track better on their own. The question of whether or not internal bloggers can do this well will have to wait.
In any case, I hope to read more about *your* experiences as well.
Post new comment