inicio mail me! sindicaci;ón

The Paradox of Enterprise Knowledge Management: What Does it mean for Enterprise 2.0

by Bill Ives

Enterprise 2.0 is much more than knowledge management but KM is a piece of it and Enterprise 2.0 helps KM to achieve its early, and often unfulfilled, promise. However, looking at knowledge management at the enterprise level raises a paradox. To be successful, KM and portals must focus on real business challenges at the functional and process level. This results in function specific solutions and business cases. Attempts to build a generic enterprise business case for KM can fall into such vague concepts as “saving everyone twenty minutes a day” which become meaningless to balance sheet.

Does this mean that enterprise knowledge management is an oxymoron? Not necessarily as these divisional solutions can operate with improved results under a common enterprise infrastructure. This common structure can provide both operational efficiencies, clarity on governance issues, and enhanced cross-functional collaboration and knowledge sharing.

In a KM Review article, “Mastering Enterprise Knowledge Management,” (scroll down the list a bit to find the article) I did a few years ago with Kasper De Boer, we offer suggestions on how to get the most out of taking your KM efforts across the enterprise. There a series of key decisions to address.

First, you need to pick realistic goals to ensure that EKM stays aligned with enterprise business goals at the functional level. This is often bypassed to set up a organization.

You can then define and design the components of the EKM services. We list a number of EKM services that generally make sense at the enterprise level such as supporting end users, setting strategic goals, facilitating the careers of KM professionals, supporting knowledge communities, and taking care of the tools.

After that you can determine which services are best handled at a global, functional, or local level. This also allows you to decide which services to outsource, buy, or build internally.

The decisions do not stop here, an EKM organization and its services must be properly positioned with other enterprise support services such as learning and performance management. This final integration step is essential to successfully coordinate the efforts of each of these functions, both minimizing turf wars and optimizing enterprise level performance.

The article explores these decisions points in more depth and is built around several case examples. It also suggests some enterprise-wide goals for KM. When you are using Enterprise 2.0 to support knowledge management these issues remain on the table. The benefits of carefully designed enterprise support remain and should not be overlooked simply because the tools are so easy to implement at the grass roots level.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • E-mail this story to a friend!
  • Print this article!
  • TwitThis
  • del.icio.us
  • Facebook
  • Reddit
  • bodytext
  • Google
  • StumbleUpon
  • SphereIt


3 Comments »

LyndarJune 14th, 2007 at 11:00 am

You nailed it when you said “KM and portals must focus on real business challenges at the functional and process level.” But in these days of blogging, tagging, RSS, wikis and social networks, why engage in a centralized KM planning process? Information flows naturally when people have the tools they need, and most of these tools are broadly available, for little or no cost, via the web. The trick is changing reactive enterprise tendencies to block information flows because of perceived threats, and to view new technologies through the lens of the opportunity they offer.

Bill IvesJune 14th, 2007 at 12:20 pm

Lyndar - good points. Any centralized planning should not be an obstacle to indiviudal initiatives which arr epart of the essence of enterprise 2.0. However, sometimes a common structure can increase cross-entperise collaboration and communication. In addition, the central group can be a clearing house for lessons learned from individual efforts.

RikaJune 19th, 2007 at 12:42 am

A centralized KM planning process will also go far towards managing expectations for both content producers and consumers. Often, these are cross-functional, and mis-communications and unmet expectations occur - these are the fuzzy things that the central group can meet.

Social web tools such as blogging and wikis are great for collaboration, but do remember there are many technophobes in the enterprise who barely caught up with email and certainly are not ready for openness and self-service approach of the social web. That’s where a centralized approach will help.

Remember, the ultimate aim of KM is to serve the business. If the most optimal approach turns out to be email-based, then that too is EKM.

Your comment

Want an image to appear near your comment? Go to gravatar.com

HTML-Tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>