Blogs and designing a knowledge work environment

Part of me is missing the Weblogs and Business Strategy conference in Boston, despite the excellent liveblogging going on from so many of the participants (topic exchange channel and Denise Howell in particular). My aggregator is overflowing with great input from the conference. On the other hand, the distance and the need to focus on my work at hand also provides a valuable filter for processing that input.

While my last several large posts have focused on wikis (part 1 , part 2, part 3) and the social dimensions of knowledge work, I want to shift back to the personal level of blogs. There’s a thread to the use of blogs inside organizations that I want to spend some time exploring.

As blogs and news aggregators move from fringe activity to leading edge phenomenon, it becomes possible to talk about the design of knowledge work. Tom Davenport, for example, has a column in the most recent issue of CIO Magazine [via Internet Time Blog] that says it’s time to look at improving the effectiveness of knowledge workers. He talks about a new effort by the Information Worker Productivity Council to study knowledge work tasks with an eye toward how Accenture and HP and Xerox can help (possibliy with an eye toward selling us something). That’s great and I’ll be following their work with interest. They’ve certainly assembled an all star list of researchers. I wonder if they’ll be blogging their efforts?

Meanwhile, I’m interested in following the radically decentralized action research program now underway in the efforts of all of us knowledge workers beginning to narrate their work and share in their collective experiments at making knowledge work more effective.

Some of us are lucky or talented enough to roll our own tools. Moreover, they’ve been willing to invite the rest of us in as co-designers . Now, many of the tools already in our toolkits theoretically allow us to participate in a design process. They’ve been built by programmers, after all, and programmers almost always prefer to solve general problems with tools rather than provide highly specific solutions to specific problems.

Unfortunately, most of those programmers work in organizations where the marketing staffs graduated from the “have solution, will travel” school of marketing and really aren’t terribly interested in having active customers who actually are interested in co-designing their tools.

In the blogging community, however, the offer to participate as co-designers is serious. Blogging tools represent my favorite class of tools–ones that can be abused in interesting ways, even by ordinary users. They grew out of their developers needs to solve their own problems. What becomes interesting now is the alignment between the problems of developers and the rest of us doing knowledge work.

Taking advantage of that alignment does demand that we take an active role in the design process. Knowledge work is craft work brought into the 21st century. As many have observed, knowledge workers own their own means of production. If we are craft workers and we are judged by the quality of what we create, then we have an obligation to be mindful about how we use our tools and how we fit them to our own needs. To be most effective, we need to take design responsibility for our own knowledge work environment. I’ll grant that we are still only at the Visicalc stage of blogging and aggregators. But that does not absolve us of the responsibility to understand and capitalize on what today’s level of technology can do for us.

The power of grassroots in knowledge management

THE INCONCEIVABILITY OF GOOGLE, and the lessons to be drawn from that, are the subjects of my TechCentralStation column today, which carries the somewhat racy-sounding title Horizontal Knowledge: Just try this thought experiment: Imagine that it’s 1993. The Web is just appearing. And imagine that you – an unusually prescient… [Instapundit.com]

A great column from Glenn Reynolds over at TechCentralStation. Here’s the punch line:

The Web, Wi-Fi, and Google didn’t develop and spread because somebody at the Bureau of Central Knowledge Planning planned them. They developed, in large part, from the uncoordinated activities of individuals. [Reynold’s Wrap-TechCentralStation]

Glenn’s in one more voice in the growing realization that top-down planning and control strategies are relatively weak when set against the grassroots ingenuity of large groups. These are insights that have to be brought back inside organizations and put to use.

Improving the interaction between individual and organizational intelligence

Collective intellect augments individual. Scott Leslie wrote in his EdTechPost blog: “Don't you just love when, in the process of thinking about an issue,… [Blog of Collective Intelligence]

George Por began thinking about organizations and knowledge management long before most of us. It's good to see him sticking a toe into the blogging waters. There is particularly thought provoking diagram in his post here that is worth a look at and is worth spending some time thinking about. He's trying to get at how individual and organizational knowledge might interact to their mutual advantage. That leads to the question of how you might design things to make this interaction more effective.

James Robertson of Column Two on KM Standards

James Robertson of Column Two consistently provides useful insight and resources on knowledge management and information architecture topics. Recently, Robertson had a series of posts that compiled an inventory of available standards on knowledge management.

Weblogs and knowledge management, part 2

One unexpected fringe benefit of falling way behind in responding to all the fascinating posts accumulating in your news aggregator is that you get a chance to pull multiple items together into an integrated post. I did one recently on weblogs and knowledge management that a number of people found helpful. The backlog of posts shows no signs of abating, so it's time for a follow up.

Rick Klau sets a nice context by reminding us of Gartner's hype cycle and its application to blogs:

We are almost certainly in the trough of disillusionment when it comes to blogs. Lots of critical comments, much confusion over their “true” benefits, etc. Yet hundreds of thousands of people continue to use their weblog as a way of cataloging their thought. And companies are starting to explore how they might use weblogs for other purposes.

My prediction: we will emerge from this trough into the “slope of enlightenment” during which it will become obvious that personal weblogs can be tremendous tools for capturing ad hoc knowledge and archiving it for future use. Furthermore, businesses will figure out that blogs can serve as both a content management system as well as an internal knowledge sharing platform – a much different use from the personal application, but a critical one for the business world to adopt weblogs with enthusiasm.[tins:::Rick Klau's weblog]

Dina Mehta is relatively new to the blogging world. She offers some helpful fresh perspective on the challenges of introducing weblogs into corporate environments. Thinking about the problems of knowledge management and how weblogs may fit, she says:

I'm not really sure that KM is being adopted in a really useful or effective manner in many organisations here. More importantly, while its great to have a system in place as a talking point, i'm not really sure what real value is being created and disseminated. They tend to be led by the HR department and are usually one-way monologues that not many participate in – (but this is really a topic for another post).

There is a constant generation of content in an organisation – via email, via IM, through documents, presentations, training workshops and seminars, and sometimes through discussion boards. KM systems tend to be slow and heavy in capturing and disseminating this content – in the process, the value may be lost[Conversations with Dina]

Like many of us, she sees that blogs may be the answer, but isn't sure how best to make the case to those in a position to make a decision.

Part of that case will hang on the availability of some concrete examples of weblogs in use in organizations. Two areas that are generating some early examples of weblogs in organizational settings are project management and marketing. Both are naturals for the technology, being high-paced and communications intensive.

On the project management side, Jon Udell at Infoworld is a regular source of good insights into weblogs in organizational settings. Here's a post he ran on the use of weblogs to improve project communications plus the corresponding article at Infoworld (Publishing a Project Weblog).

The value of a project Weblog has a lot to do with getting everybody onto the same page — literally. You want to deliver a manageable flow on the home page, drawing attention to the key events in the daily life of the project. To do this well, think like a journalist. …

The newspaper editor's mantra is “heads, decks, and leads” — in other words, headlines, summaries, and introductory paragraphs. These devices are, in fact, tools for managing a scarce and precious resource: the reader's attention. A well-written title (or subject header if you happen to be composing an e-mail message) is your first, best, and often only chance to get your message across.

There's a particularly useful diagram Jon reproduces in another Infoworld post on blogs, scopes, and human routers and drawn from his his equally useful book, Practical Internet Groupware. It captures a notion of the multiple overlapping groups that we belong to in the pursuite of knowledge work.

Jon has also talked about the notion of what he calls the conversational enterprise and how weblogs will serve as a key source of the raw materials for knowledge management in organizations (Technical trends bode well for KM);

What k-loggers do, fundamentally, is narrate the work they do. In an ideal world, everyone does this all the time. The narrative is as useful to the author, who gains clarity through the effort of articulation, as it is to the reader. But in the real-world enterprise, most people don't tend to write these narratives naturally, and the audience is not large enough to inspire them to do it.

There is, however, a certain kind of person who has a special incentive to tell the story of a project: the project managers, who are among the best power users of Traction Software's enterprise Weblogging software, according to “Traction” co-founders Greg Lloyd and Chris Nuzum (see “Getting Traction”).

“Traction” certainly is powerful software, although the power does come at the expense of a somewhat steeper learning curve than systems like “Radio” or Moveable Type whose origins were in personal weblogs rather than enterprise. Actually, it might be better to think in terms of a steeper implementation curve, rather than learning curve. Setting up “traction” in terms of project structures and tags takes some thought to get full advantage of the tools. Using them on a day-to-day basis is pretty straightforward.

The use of weblogs in marketing settings is also drawing attention. Some of that is in the form of early, and rightfully ridiculed, examples such as the faux-blog Raging Cow, which tried to force its traditional marketing strategy through a blog format.

Others have made more sensible progress (I suppose that makes me terminally boring). Inc. Magazine ran a recent piece on Blogging for Dollars (link found via Blogging News), for example, that highlights some examples of the real use of blogs as a marketing tool.

Gary Murphy at TeledyN offers up a couple of interesting examples of KM in organizational settings in a recent post on Walmart's KM rocks.

Both searches were initially pointless because, for very good reasons, both the sought after data items did not exist in the superficially logical locations. This is probably the number one flaw with most dead-robot KM systems: They fail to accommodate how Reality is inherently messy!

The only possible method to locate either the ribs or the cards was to do what humans have done since the dawn of archives, ask someone who knows. In both instances, we needed someone who knew where the target was, and who could refer us to someone who knew how to extract it.

Murphy provides the critical link here between weblogs and organizational need. It is the realization that KM in organizational settings is primarily a social phenomenon and not a technology one. Most prior efforts to apply technology to KM problems in organizations have been solutions in search of a problem. They have been driven by a technology vendor's need to sell product, not an organization's need to solve problems.

Weblogs are interesting in organizational KM settings because weblogs are technologically simple and socially complex, which makes them a much better match to the KM problems that matter. One thing that we need to do next is to work backwards from the answer – weblogs – to the problem – what do organizations need to do effective knowledge management. We need to avoid the mistakes of other KM software vendors and not assume that the connection is self-evident.

Weblogs and knowledge management

Another stream of recent posts has focused on weblogs as a tool for knowledge management both to capture and share knowledge. They include a mix of posts focusing on individual knowledge workers and on knowledge workers within organizations.

Lou Rosenfeld, author of the excellent Information Architecture for the World Wide Web, has a good post on blogging k-logging.

Dave Pollard has generated a great set of posts on weblogs as knowledge management tools. His weblog in general has become a must read for me.:

Blogs in Business: The Weblog as Filing Cabinet

Weblogs could be a mechanism to coherently codify and 'publish' in a completely voluntary and personal manner the individual worker's entire filing cabinet, complete with annotations, marginalia, post-its and personal indexing system.

A Weblog-Based Content Architecture for Business (this post also has some excellent diagrams of how weblogs fit within the entreprise)

The fundamental difference between this and traditional enterprise-wide content architectures, is that knowledge under this model resides with and is controlled by the individual. The knowledge of the community is simply the sum of the knowledge residing in the weblogs of the community members (within any shared categorizations the community members decide to establish, and pushed to other community members by the weblog's 'subscription' functionality. The knowledge of the enterprise is simply the sum of the knowledge residing in the weblogs of all employees, made accessible through the weblog's publishing and subscription functionality, using the tools present in the weblog itself. Theoretically, depending on the robustness of the company's networks, the Intranet could be slimmed down to nothing more than a set of organized links, with no actual 'content' whatsoever.

Blogs in Business: Finding the Right Niche

Weblogs can be effectively pitched to senior management of major organizations by explaining how they help solve the six problems:

  • They make contributing knowledge simpler, easier, and more automatic
  • They make it easier to update knowledge on a timely basis
  • They make knowledge more context rich
  • They allow the authors of key business knowledge to build and retain 'pride of ownership'
  • They make contributing knowledge more fun, since it becomes more like 'publishing'
  • They make contributing knowledge more fun, since it becomes more like 'publishing'
  • Each individual's 'collection' of shared knowledge is easy to define and assess at performance evaluation time
  • They make knowledge easier to route, to 'subscribe' to, to canvass and to 'mine'
    • Dave Sifry, creator of Technorati, and Doc Searls did a piece for Linux Journal on Building with Blogs. One key excerpt:

      As weblogs account for more and more of the traffic in knowledge about a given subject, they become powerful instruments for hacking common wisdom. In many categories, they are moving ahead of mainstream journals and portals and building useful community services where over-funded dot-com efforts failed spectacularly.

      Sébastien Paquet adds a piece on “towards structured blogging” where he starts to think about how to begin adding a next layer of metadata to collections of weblogs.

      Right now what we have, globally speaking, is pretty much a huge pool of blog posts, each implicitly tied to a particular weblog author and with a date slapped on.

      Donald Luskin makes the following observation in his weblog (pointers courtesy of “Scripting News” and Roland Tanglao)

      At the dinner table I explained what a blog is. There was the usual polite, partially feigned fascination with anything having to do with the Internet. But when I said that blogs have completely transformed my utilization of media and the way I acquire information about the world — that I basically get everything from blogs now — everyone stopped being polite. One fellow at the table was utterly shocked that I would trust any information I acquired online. I asked him if he trusted information he got from politically biased mainstream newspapers like the New York Times, or for that matter, from any commercial media biased toward at least some degree of sensationalism, if not some particular political view. I asked him if he had ever, once, read a newspaper account of some event of which he personally had expert or eye-witness knowledge, and found it to be accurate. I asked him he had ever once been interviewed by a reporter who quoted him accurately or in context, or who didn't already have the story written before the conversation even began? Well, no, he had to admit… but still… “…not the Internet! You can't be serious!”

      Roland is always a source of good observations and links about blogging in knowledge sharing and knowledge management contexts. Some recent commentary via his blog include

      Blogging is too difficult but it will get better. Like I always say we are at the VisiCalc stage of blogging. Compare and contrast Excel and VisiCalc; lightyears better and people in 2003 understand spreadsheets. Same thing will happen with blogging; we need years of experience and iteration to get from the VisiCalc of blogging to the Excel of blogging.

      and this pointer to Value Creation by Communities of Practice

      Blogs encourage cross-functional disruptive thinking.
      I read a great quote that, like a magnet of meanings, pulled together layers of my thinking into a surprising pattern of possibility. Here it is: “Here is the paradox: You need a great team of people with diverse skills to perform a symphony well, but no team has ever written a great symphony! … While cross-functional teams are key players in defining and implementing incremental innovation projects, cross-functional disruptive individuals tend to be key players in defining radical innovation projects.”

      That should cover it for tonight, although there are still a bunch of good posts on this topic filling up my aggregator.

      The lineage of good ideas

      I’ve had several comments on my post on the risks of knowledge work that I’ve misattributed the comment:

      “Better to remain silent and be thought a fool, than to open your mouth and remove all doubt.”

      I attributed it to Mark Twain, but my readers believe it belongs to Abraham Lincoln. Certainly wouldn’t be the first time I was wrong on an attribution. I did a quick bit of googling to find that the quote is also attributed to Einstein and Groucho Marx among others (according to Ask Yahoo). They suggest that you can even trace this one back to Proverbs 17: 28:

      Even a fool, when he holdeth his peace, is counted wise:
      and he that shutteth his lips is esteemed a man of understanding

      Of course, in a knowledge management context, this kind of problem is interesting beyond the immediate feedback from my readers. Good ideas, like successful projects, are likely to be a product of many parents (another maxim usually associated with Kennedy, although he didn’t claim it as his own insight). Getting the record straight is only one consideration in moving from good idea to successful implementation. The value in tracing lineage isn’t so much about parceling out credit as it is about learning from both the successes and failures of others.

      The real risks of knowledge sharing

      Don’t worry about people stealing your ideas!. I just love this quote from Howard Aiken:

      Don’t worry about people stealing your ideas. If your ideas are any good, you’ll have to ram them down people’s throats.

      So true! [Gurteen Knowledge-Log]

      I have a new hypothesis about why it’s difficult to get people to contribute to knowledge management systems in organizations.

      Conventional wisdow says it’s because people are worried that someone will steal their ideas. I think that’s a rationalization. I think the real fear is the fear of being ignored. The fear that the knowledge I share is so obvious or trivial that no one will care. What’s the old maxim from Mark Twain? “Better to remain silent and be thought a fool, than to open your mouth and remove all doubt.” (some input from my readers about the correct attribution of this quote. See my comments here for some more)

      The issue may still be fear, but it’s a fear that we need to address in a very different way.

      Weblogs in organizations and finding voice

      An interesting little piece in Business 2.0 about corporate use of weblogs

      Business 2.0 – Web Article – Management by Blog?

      Most of the companies I've observed using blogs are trying it on their customers before unleashing it internally on their staffs. The external need, apparently, is more pressing. Many businesses already have other systems in place for managing internal information, ranging from simple brown-bag lunches to overkill knowledge-management regimens.

      I disagree that the external need is more pressing. I suspect that the truth is that the external weblog strategy presents less risk in the eyes of the implementer. Or to put it differently, internal weblog experiments feel risky.

      Even if they're about knowledge management and not cats, good weblogs are personal.  They are an outlet for personal voice. Organizations aren't sure how to deal with personal voice and most of us have learned a healthy caution about expressing it inside our organizations.  I've come to believe that organizations that wish to survive will have to learn how to let organizational voice emerge from blending the unique voices of its members. A necessary step in getting to that harmony will be to help individuals find their own voices first.

      Weblogs provide a tool to find, exercise, and develop your voice in a potentially manageable way. You can start by adding grace notes to what others are saying and gradually build to more extensive contributions. The chronological structure of short posts encourages and gently forces continuing practice. And plugging into a piece of the weblogging community gives you a support group who provide examples of their own voice, material to try harmonizing with, and encouragement and support to newcomers.

      Helping weblogs to succeed inside organizations has little to do with technology features.  It depends instead on nurturing a grassroots process of tentative practice evolving into confident process. Think Harold Hill in The Music Man not General George Patton in Patton

      Grassroots knowledge management

       

      One critical feature of most first generation knowledge management efforts is that they were designed and implemented following the standard corporate approach of top down, centralized, resource planning and implementation. In an industrial environment you can maybe get away with planning processes that treat all resources as fungible. Then centralized processes might be adequate, although you would think that the failure of Soviet style centralized economies would give more corporations pause.

      Knowledge work, on the other hand, depends on extracting maximum advantage out of the unique characteristics and experiences of each knowledge worker. Knowledge management, from this perspective, has to be a decentralized, grassroots, activity. If you accept that premise, the promise of weblogs in knowledge management becomes clearer. Weblogs operate on grassroots assumptions by design.