McGee's Musings

This has been lurking in my RSS aggregator for the last couple of months, patiently waiting for me to get around to reading it (one of the core benefits of using RSS feeds).  David Gurteen provides a nice starting point for discussion around attributes of effective knowledge workers.

While I would certainly want people with these attributes working for me and around me, I am less certain that these are uniquely related to knowledge work. Nor, for that matter, am I certain that that matters. Your thoughts?

What makes an effective knowledge worker?

By David Gurteen

At the Osney Media European Knowledge Management Thought Leaders Forum last week In London we broke into several “discussion pods” to discuss topics of interest. Earlier, I had proposed a theme of “What are the habits of effective knowledge workers?” and was pleased that this was one of the topics selected.

There were about five of us at our table and we started by getting into a discussion about what were we talking about: habits; skills; attitudes; behaviors; values; mindsets or what? We decided quite quickly that we would run out of time if we focused on these differences and decided just to brainstorm everything without attempting to categorize them. This is the list we came up with. As the others carried on a conversation – I just scribbled down the key attributes – here they are – pretty much in the order they arose and unedited.

connect people with people connect people with ideas are good networkers do not follow the rules have strong communication skills like people feel good about themselves motivate others are catalysts ask for help demonstrate integrity are self reliant open to share are not afraid are goal oriented are able to identify critical knowledge add value to the organization have strong subject expertise in a specific area network for results

trustworthy – can be trusted and trusts others make decisions are not insular do not conform push the boundaries assume authority – ask for forgiveness, not permission strong belief in the value of knowledge sharing are informal active leaders take a holistic view are catalysts, facilitators and triggers good listeners – they listen first do not need praise see the wider picture work well with others do not have a ‘knowledge is power’ attitude walk the talk prepared to experiment with technology playful take calculated risks

An interesting set of attributes but by no means exhaustive. Will be interesting now to analyze them and pull them into some sort of structure and order. Seems to me though that many of these attributes are ‘soft’ in nature and difficult to teach or learn. How does someone learn ‘not to need praise’ for example and just how important an attribute is it?

Case examples of organizations employing information technology in strategic ways that are relevant to Enterprise 2.0 can be difficult to find. I know of an example from the late 1990s that nonetheless offers relevant lessons for today.

Black and Veatch is an engineering management and design firm that builds large-scale projects such as power plants. I first learned of them as the reviewer who vetted their ultimately successful application for an Enterprise Value Award from CIO Magazine.

What makes the lessons from Black and Veatch so relevant are the careful effort to marry technology to the core knowledge work process and the investment in organizational learning over time. Instead of simply deploying off-the-shelf CAD software, Black & Veatch developed software that supported a design process that was redesigned to leverage detailed data about past projects and the current project. Further, over time, Black & Veatch’s design engineers learned to make more effective and productive use of the software, and the software itself was updated to exploit that learning. Take some time to read about their effort to “reengineer the engineering process.”

If the set of technologies loosely identified at Enterprise 2.0 are to have any hope of real success, we need to take a closer look at how they are introduced into organizations. I see two basic patterns for technology introduction in general use and neither holds much promise.

The first pattern is embodied in the massive ERP rollout. Here, a highly structured set of technologies and corresponding processes are imposed on the organization. People in these systems have equally structured roles that are imposed on them in order for the overall system (organizational and technological) to perform as a designed mechanism.

In the second pattern, some fundamentally individual technology sneaks into the organization at the hands of discrete individuals. Spreadsheets, word processors, web browsers all infiltrated the organization. Even email and networking followed a fundamentally organic diffusion process.

Enterprise 2.0 technologies, of course, are social tools. Their promise and their challenge is that they exist at the boundary between organic and mechanical. Real success depends on blending aspects of both deftly.

Organizations deploying technology tend to view process too mechanically. They can put technologies in place, but aren’t adept at helping individuals and work groups learn how to put the technology to use effectively.

Innovative individuals can experiment with new tools and techniques and can encourage their peers to take up some technologies simply by example. But they generally lack experience and authority to craft the small group learning and experimentation to discover the joint ways of using technology to support more productive and effective processes that exploit the full potential of the technology.

The challenge is to find a third way. My own prediction is that the best path for introducing Enterprise 2.0 technologies is from well-positioned individuals up to selected work groups rather than down from the technology organization. By well-positioned, I mean individuals who have enough power and influence to persuade a work group to “run the experiment,” and whose work group is responsible for a consequential enough deliverable that the results of the experiment can carry some weight in the organizational hierarchy.

Successful experiments will have little or nothing to do with technology specifics. Instead, they will be characterized by how effectively they mesh with and advance specific processes within the organization. Or, by how they transform a loose set of existing practices into a process that can be managed and improved.