Showing posts with label knowledge economy. Show all posts
Showing posts with label knowledge economy. Show all posts

Wednesday, 11 June 2008

How much knowledge work do you actually do?

Or perhaps, more importantly, how much knowledge work does your organisation actually do? There's a whole host of recent posts that touch on the collision of innovation, knowledge work and systematisation in business. (e.g. Victoria Axelrod, Dave Snowden.)

One thing I am still struggling to understand and (roughly) quantify is how much "knowledge work" is actually going on. Over the years, many commentators have taken the "Gold Collar Worker" as a starting point and believed that the future of work for many (if not most) will be more flexible, more satisfying and more knowledge-based than before. This leads of course both to a view of education as a tool for income improvement (not to mention as the source of increased value-added for businesses.)

However, my own observation of various "knowledge industries" is that many firms may be large, but many of the people inside are doing rather routine work (which might be termed "mental labour") which is not particularly creative or flexible, but for various reasons is not cheap to automate at this time. So, I'll put the question to knowledge workers reading this, how much of what you do is really "creative knowledge work" and how much will be outsourced to lower-skilled subordinates using a computerised system in the next few years?

 

Technorati Tags:

Friday, 18 January 2008

Howard Rheingold, RSS, Knowledge Work

It appears, searching through the blog, that I haven't talked about Howard Rheingold's new set of video presentations yet. Fortunately, he's only on to his second one so far, so it's easy to catch up. I've linked to the wiki page for him, so I'll just say he's been writing about the culture of work and leisure related to computers since the age of the PC began.

This edition of his vlog is titled "Introduction to RSS" and it is a fairly clear and useful description of why RSS might be useful. There are other good explanations out there however, particularly the video from Common Craft, but the first 3 minutes or so of Rheingold's musings form a very tight description of the concept of "knowledge work" and point to why it is difficult to manage in an industrial fashion. It's not explicitly about that, but in describing how he works, Rheingold points up what it means to be in one of the modern occupations which is all about the processing of diverse sets of information. I highly recommend it for anyone interested in what some parts of the "knowledge economy" look like.

 

Saturday, 15 December 2007

The two worlds of business communication

A newsletter from Mindjet (who make the excellent MindManager mind map software) reminds me again of the two ways people tend to talk about "communication" in business and my own uncertainties about where they join up:

1) There are those known as "Internal Communication" professionals and they focus largely on what might be termed "community communications issues." This ranges from the hardnosed business case models around communicating "brand values" in the organisation to created "engagement" to potentially softer strategies around more journalistic exercises which create and reinforce a sense of community and well-being within the organisation.

I've spent a fair amount of time writing about these aspects recently.

2) The other people who tend to work with "communication" are IT consultants and Business Process Re-engineers, who (like the Mindjet people) largely talk about communication in terms of the needed exchange of information to make a business process happen. If you're designing a new widget, then there has to be an exchange of information regarding costs, design parameters, market needs, etc.

It is my feeling that these two worlds, which have largely been long separate are now starting to touch at the edges. Two major reasons why spring to mind right now:

a) The rise of the "knowledge worker." This deserves a post on it's own, but in short, industries are changing. Service industries are often all about manipulating information and even traditional manufacturing industries are finding that competitive advantage depends more and more on how they do things and the design of the things they make. As a result, the "knowledge" of various businesses now sits more than ever with the people. Where processes used to assume that people were interchangeable parts who existed to facilitate the process, we're gradually learning that in real "knowledge roles" the process isn't so easy to institutionalise. As such, the technological/process imperative is now more about enabling communication than specifying it.

This has parallels with:

b) The rise of social media. It is social media technologies, as much as anything that have produced an awareness in internal communications types (not to mention marketing departments too) that "message management" is a dying proposition. Where previously IC might have felt it was the medium of community information exchange in a company, it's clear now that people can talk to each other in myriad ways. Forward thinking IC professionals recognise this and seek to work with it, and thus they are also looking more at enabling communication than specifying it.

Where I think a crucial confluence exists is that the existence of communication technologies does not mean that necessary communications are taking place.

As such, in knowledge work, there is a need to bring the two perspectives together. From the BPR angle there is an expertise about incentives and formal rules for promoting specific information exchange and from the IC side there's a much greater understanding about the human issues around communication, which becomes ever more critical as the information we seek to communicate becomes more human (less numeric, less precise, less quantifiable) as the task involved becomes more abstract and more creative.

Add that together and that's some sense of my gut feeling of how the two worlds can help each other a little.