Category Archives: Knowledge Management

Has Knowledge Management Been Bad For Us?

In the world of Knowledge Management, we frequently talk about at least two different types of knowledge we deal with. The first is explicit, or codified, knowledge (stuff that’s captured and, hopefully, readily accessible in some useful form); the second is tacit, or tribal, in-the-head, “between the ears” knowledge. For most of my nearly 15 years of knowledge management practice in the aerospace business I have noted we spend an incredible amount of time, energy, and money working on the former.

At the same time we have continually asserted the vast majority of useful knowledge was the latter. I had a graphic that showed the ratio of explicit to tacit knowledge at 19 to 1, but it’s no longer accessible. So I created this one from a graphic in the public domain and added text in Photoshop. While the ratio shown here isn’t nearly what I believe reality provides, it does give a glimpse of how much remains under the surface when comparing the two types of knowledge. Actually, I found another available graphic that shows the ratio as a little greater than the one I put together, and it also lists more details of what types of knowledge comprise each of these two main categories.

For me, this is huge! In fact, where I come from we tended to use an adaptation of the Pareto principle, i.e. an 80-20 distribution, so this graphic helps make my point a fortiori. Now let me get to my point. Last Wednesday (12 May 2010), Rob Paterson published a wonderful post at the FASTforward blog entitled “Have books been bad for us?”, where he discusses the question of whether or not the web is making us stupid, as well as his belief the opposite is true. He argues that books have actually stunted our ability to innovate and create new knowledge. You really have to read the whole post, but here’s a sample I like:

But with the book comes authority. With the advent of the book, much of knowledge development stopped. Only the in group was allowed to play. What mattered was not observation. Not trial and error. Not experiment. Not sharing. But authority. Most of the accepted authority were texts that had no basis in observation or trial and error. Ptolemy, St Augustine and Galen ruled.

Rob goes on to argue, rather than making us stupid, the web is providing us with the kinds of information and knowledge connections we used to have before the book removed the more communal ways in which most of our collective knowledge was arrived at in the past.

So, here’s where I find an analogy to the work I’ve been doing for some time. Much of of what we call Knowledge Management (at least in my experience) seems to spend an inordinate amount of time and expense on dealing with the 20% (or 5%, depending on who you listen to) of an enterprise’s knowledge that is explicit. We work on organizing share drives, federating search capability, and scanning and rendering searchable (through OCR) much of our paper-based, historical information. I’m sure there are other ways in which explicit, recorded information is analyzed and organized as a function of a knowledge management activity.

But I think we’re missing the point about the real value of knowledge. If, in fact, the largest (by far) percentage of an enterprise’s useful knowledge is locked between the heads of its employees and, if (as we frequently say about tacit knowledge) much of it can’t be accessed until it’s required, why are we not spending more of our limited funds on facilitating the connection and communication, as well as the findability and collaborative capabilities of our employees?

I’m not suggesting there isn’t value to content management, smarter search capabilities, etc. I am saying, however, that I think most organizations are missing the boat by not spending more of their resources on the thing that offers to connect their people; to create organizational neural pathways that promise to be far more beneficial to the overall health of the company in terms of product innovation and design, manufacturing processes, customer relations, project management, etc. (or on and on). I am speaking of Enterprise 2.0, on which I will have a lot more to say in future posts.

The problems we face with acceptance are monumental. People in organizations that have traditionally been hierarchical and within which silos and fiefdoms emerge, turf wars and power struggles go on, and people are both kept in the dark and made afraid for their jobs hasn’t exactly set the stage for the trust required to do any kind of knowledge management effort. Nevertheless, if we’re going to participate in the struggle, we ought to be shooting for the things that are going to prove the most valuable – in both the short and the long run.

I’m a book lover myself. My reverence for books is almost stupid, actually, but I’ve worked hard on overcoming it. Unlike Rob, I no longer wonder. I see the web, and the enterprise and its internal network, as the future of our group intelligence and knowledge. What do you see?


Saying “I Don’t Know” Will Set You Free

If you’ve ever been in sales, I’m willing to bet you know it’s never a good thing to pretend you know something you don’t. Unless you’re making an opportunistic, one-off sale and you don’t really care about any relationship with your customer, it’s far better to admit ignorance and pledge to get an answer ASAP. Frankly, I think it’s always the best tactic regardless of your relationship; it’s just plain ethical and, a bit ironically, smart.

Most people know when they’re being fed a load of crap and pretending to know something of which you are ignorant can open up so many cans of worms it’s hard to define all the consequences. One of the major ones, however, is never being believed no matter what you say. Not a good thing, whether in sales or elsewhere.

Anyway, this came up again for me today because of a tweet by @wallybock, who pointed me to an article in the New York Times’ Corner Office section. The post is entitled “What’s Wrong With Saying ‘I Don’t Know‘?” It’s a good interview of Rachel Ashwell, founder of Shabby Chic and, besides her admonition to not be afraid of admitting ignorance, there’s a wealth of good business (and life) advice in her words.


Behind The 8-Ball . . . or Hand me The Hammer & I’ll Fix This.

Now that I’ve had a little while to work with my new iMac, I’m beginning to come down from the techno-induced stupor I’ve been in and am thinking about what this all means to me. I’ve also been thinking about what it should mean for many people who work in corporate America, where I have been laboring for the past two decades and more.

Let me explain what I’m getting at. From the first day I started working at what was then Rockwell International’s Rocketdyne division (formerly North American Rockwell), I was stuck using technology that was already a little behind the eight-ball. Back then (1987) there wasn’t much in the way of personal computers, but they were developing rapidly. I went from an IBM 8086 to an 8088 to an AT and, finally to Windows and on and on. As time wore on the level of state-of-the-artiness of the available technology I had available at work, unfortunately, fell further and further behind.

Now, this isn’t about the battle that took place between IT (formerly MIS) and Engineering for many years, and how it affected the development of the first LAN in the company (hint – it wasn’t pretty), but rather about the level of security and, perhaps, paranoia that built up over the years with respect to the use of computing resources.

Part of the problem for my line of work was the very real issue of the International Traffic in Arms Regulations (ITAR) which, sometime after we were purchased by the Boeing Company, was painfully and expensively learned after an inadvertent and ignorant violation of the Regs (another story this really isn’t about). This lesson required some education and was fairly easily addressed once understood.

I think I need to throw in a caveat here. I am not an IT person. I have absolutely no formal IT education. I am merely a business person who has worked with (mostly) micro-computers – now called PCs – for close to thirty-five years. I have participated in or led efforts in knowledge management and Enterprise 2.0 for Pratt & Whitney Rocketdyne, and I was instrumental in bringing in our first web-based social system over 7.5 years ago. I have also been the project manager for that terribly under-used application all this time as well. My point here is I may not use language that’s accurate, but I know the kinds of functionality available and I know all of it is – from a corporate point of view – there to serve the business.

What I’m concerned with is the application of a one-size-fits-all mentality to the provision of information technology to a company’s workforce, as well as the imposition of blanket security regulations that serve to cripple an organization’s ability to keep abreast of developments in that same technology. This becomes increasingly important as more capability moves out into the cloud (this includes micro-cloud environments, i.e. inside the firewall capability that utilizes cloud-like architecture.)

I have tried to argue, to no avail – I’m sure others will recognize this particular kind of frustration – for the identification of power users who could be provided with, for lack of a better term, beta capabilities they would exercise and learn about. These people would provide a cadre of workers who are constantly looking at new ways to improve communication, collaboration, and findability. People who’s job, in part, is to find newer and better ways to get things done. In my eyes, this is a no-brainer, and I have to say with the speed things are changing nowadays, I think this kind of approach is even more important.

I recognize it is difficult to get large organizations to move rapidly. One doesn’t turn a battleship on a dime. Nevertheless, it is conceivable to me (much more so now than a decade ago) a small group of people could help any organization understand – at the very least – how work gets done, how workers are communicating and collaborating with each other across various boundaries, and how knowledge is being shared in a timely and useful fashion. I also think, daring as it may seem to some, that paying attention to – and preparing to learn from – the processes that are changing the way we do these things can position a company competitively to be a player, rather than an also-ran. I quite certain failing to do so leaves you with the situation I grew used to; a company with computing resources and experience years behind state-of-the-art. In marketplaces where this can change dramatically in under a year, I think that’s unconscionable.

Have any of you experienced this situation? Does it resonate at all? Am I totally off-base or do you think this would be a viable approach for large organizations to engage in?


Transportable Medical Records

Being at the Doctor’s office (routine visit) reminds me of a pet peeve. I am all in favor of any move toward digitizing and sharing my medical records with my providers; present & future. I hope that our sensitivity – I might allege hypersensitivity – over medical privacy isn’t crippling us from moving forward with an effort to save us from repeatedly filling out the same histories every time we go and for every new provider. Just a thought!

Rick

Posted via email from rickladd’s posterous


Reflecting on Some Other Reflections

Two posts got me thinking today. I’m not usually one to see the year as abruptly changing when December rolls over into January; I don’t do New Year’s Resolutions and stuff like that and I am more prone to celebrate the Winter Solstice than to celebrate Christmas or Hanukkah. Yet, it is the end of a calendar year, and there is some sort of change that always seems to take place when the year rolls, so I thought I’d take a crack at looking back just a bit at the previous 12 months. Having said that,  I’d also like to look a little forward as well, but that will come just a bit later.

The two posts I’m referring to are by Andy McAfee and Susan Scrupski, two people I have come to know better this year due to my work as an internal evangelist on Enterprise 2.0.  Andy’s writings on E2.0 and Susan’s tireless work on establishing and greasing the skids of the 2.0 Adoption Council have made my job much easier. I have learned a great deal from them and expect next year to bring even more knowledge, enthusiasm, and innovative ideas and practices I will no doubt benefit from. The post I refer to by Andy is very upbeat and strikes an optimistic note. The one by Susan is more hopeful than optimistic, but is definitely upbeat. Nevertheless, they’re both wonderful posts that look forward to bigger and better things. You can read them here (Andy’s) and here (Susan’s).

This last year has been a year of transition for me. Our fairly new President (I’m talking about where I work, not the country) recognized the value of E2.0, as well as numerous other efforts I was engaged in, and began leading the company in a new direction at the beginning of the year. He even christened our direction PoWeR 2.0 (PWR is an acronym for Pratt & Whitney Rocketdyne. Since our main business is Rocket Engines and Energy Systems, PoWeR is a decent way to characterize who we are internally). In addition to E2.0, PoWeR 2.0 includes the continuing integration of Program  Management, Knowledge Management, and Enterprise Thinking, the latter of which is our approach to the Systems Thinking propounded by people like W. Edwards Deming, Russell L. Ackoff, Peter Senge, and Edward de Bono, to name a few. To my way of thinking it will ultimately (I can dream) result in a relatively holistic, portfolio approach to the management of the entire enterprise, ridding us of silos of knowledge and performance in order to more efficiently and effectively meet the challenges of a fast-moving and demanding economy.

This very positive direction came at a time when our parent company announced our merit increases would be postponed by six months and that we would be given five days of unpaid “furlough” during the year. To their credit, when the six months expired we were given increases and the furlough days were designed mostly to intersect with holidays so we would get four day weekends. The financial hit was also spread through the remainder of the year once the decision had been made. This made it a bit more palatable and easier to assimilate financially. For that I am grateful. I’m not blind to the difficulties of the economy and we’re in a sector that can be hit pretty hard. Frankly, I’m pretty happy to still be employed and have a challenging and exciting job to do.

This year I also managed to complete my Masters Degree in Knowledge Management at CSUN. For me this was a major accomplishment. Not only was I working 46 – 50 hours most weeks, but I also have two young children and I’m no spring chicken, having arrived in this world back in 1947. It was sometimes grueling work, especially the last trimester when all I wanted was to get on with my life and put more attention into what I was doing at work. Nevertheless, I now have another degree to add to my accomplishments. Maybe some day I’ll get a Baccalaureate as well.

I’m almost embarrassed to say I became a Cancer patient and survivor all within the space of less than a month. I say embarrassed because I didn’t suffer at all. I must admit to being a bit concerned when I discovered I had a malignant melanoma on my back, especially after doing a little research and coming across descriptions that referred to it as the deadliest form of Cancer. Nevertheless, it was caught early, surgery was successful (and proved it hadn’t metastasized), and the Doctor’s say the chance of recurrence is around 3% – less than the chance I’ll have a heart attack or stroke in the next decade or so.

So, for me this has been a pretty upbeat year – all things considered. My kids are healthy; my wife, though still unemployed, is doing a great job of organizing the children’s education and extra-curricular activities, and (for the most part) I’ve been pretty healthy. Now for next year.

I’m really looking forward to next year. I believe I will be involved in some very exciting and innovative activities at work and, through the 2.0 Adoption Council, will be learning more and more about how to help my company reap the benefits I believe the development of what Andy calls emergent social software platforms (here for more info) will provide for any company willing to work at their adoption and profitable use. I have made plans to attend the next Enterprise 2.0 Conference, though I have already been working on methods of using social software (like Twitter) to allow others to virtually attend many conferences and possibly provide for far greater participation while saving money on travel expenses.

If I don’t post before the New Year I wish everyone a wonderful, joyous holiday season shared with friends and family in relative peace and comfort, as well as a happy and healthy new year. BTW – Susan, 2010 is the end of the decade. It won’t be over until 2011, but who’s counting?


2.0 Adoption Council One of the Best Stories of Year (says Dion Hinchcliffe)

Well, I’ve spent the better part of two years now learning about Enterprise 2.0 and how it can be applied at Pratt & Whitney Rocketdyne. I have been practicing Knowledge Management for over 10 years there and it has been a constant struggle to get people to see the value in sharing knowledge, learning from our mistakes (though we pay great lip service to it in the form of never-quite-realized attempts at collecting “lessons learned”), and not re-inventing the wheel.

I first became aware of E2.0 after reading Tim O’Reilly’s seminal paper, “What is Web 2.0“, and it started me thinking about how we could use the design concepts he laid out so well to our inside-the-firewall efforts to increase our communication and collaboration capabilities. I actually thought I was in the forefront of the effort and was somewhat chagrined when I discovered Professor Andy McAfee had been writing about it for at least a year prior to my discovery. He was the one who coined the term Enterprise 2.0 and, after my initial disappointment with NOT being actually in the vanguard, I was thrilled to find there was a body of work out there I could learn from.

I also soon found Dion Hinchcliffe, who wrote prolifically and lucidly about E2.o, as well as created lots of excellent graphics that made sense of how the connections worked and what, in fact, should be connected. I have a large collection of Dion’s graphics gathered together in a rather large PowerPoint presentation that I drag out and look at now and again to remind of why I’m doing what I’m doing and how it all fits together.

At the end of July of this year I was fortunate enough to become a member of an organization of E2.0 practitioners, the 2.0 Adoption Council, dedicated to advancing the acceptance and application of Enterprise 2.0 design principles. Rather than tell you much about it, I want to point to Dion’s latest post entitled “Enterprise 2.0: The 2009 Year in Review, where he has the following to say:

Communities of practitioners began to form. One of the best stories of the year was the formation and rise of the 2.0 Adoption Council. Founded by my good friend, the tireless Susan Scrupski, the 2.0 Adoption Council is a practitioners-only community (no vendors or consultants allowed) that has developed an impressive following. Well over a hundred companies are now represented on projects from the quite small to the quite large. It’s also one the very best sources of data — their latest report is packed full of useful information — for what’s taking place with Enterprise 2.0 today. If you’re engaged in Enterprise 2.0 work, I urge you join the council and increase our collective knowledge of what’s happening with enterprise social computing.

If you are at all interested in how your business can perform better and be more effective – not merely more efficient – you owe it to yourself to understand what E2.0 has to offer you. If you are working now to get your company to adopt these practices, consider doing what Dion suggests, joining the Council and learning from some of the best practitioners in the world. You can read his entire post here.


Are We Really Communicating All That Better?

In my over twenty years of experience at the large, very successful aerospace company where I labor, I have spent a great deal of time trying desperately to get the IT people to talk to the Engineering people. I haven’t, for the most part, been all that successful. Back in the day IT was truly an empire unto itself and it was pretty blind when it came to listening to the needs of the Engineering community. Furthermore, many of the systems that were used by various programs were dictated by the customers who were paying for our services and our products, basically NASA, the U.S. Air Force, and DOE.

This resulted in some very interesting problems with respect to systems, tools, and their use and subsequent development. What used to happen was Engineering would get an itch for a certain type of functionality but, since it hadn’t been contemplated in the original contract and since it might be some time before it could be renegotiated in order to get some money for developing the code required, Engineering would take it upon themselves to develop what they needed. You can imagine what happened many times. Though not an Engineer myself, I believe all Engineering students study one or more computer languages . .  . I’m fairly certain most of them  do.  Well, they would just get on the problem themselves, either writing code or – even worse – creating a tool in Excel.

So now we find ourselves in the interesting position of having something like a couple hundred tools, many quite useful, many overlapping in functionality. Many of them are unwieldy and kind of out-of-date, yet we don’t quite know how to get rid of them. This does seem to be changing somewhat as the tools of Enterprise 2.0 are gaining traction, i.e. blogs, wikis, user-generated content in general. Regardless, there are still numerous choices for how to deal with each of these as well. What wiki should we use? What about Open Source? (Anathema, btw, in my company – at least for now).

So the beat goes on. We keep adding tools, if at a slightly slower rate than previously (I think), and we seldom shed any. I suspect, as more and more content gets generated through the use of social media, and the ability to organize and make sense of it improves, we will eventually move away from many of the tools we’ve kind of grown up with. Data, too, will probably migrate toward a common format that can be accessed easily by anyone who wishes to and has authority to do so. It would be nice to see everyone on the same page, rather than pockets of people talking about the same thing in slightly different, and frequently incompatible, formats and locations.


To Search or Not to Search

About a week and half ago, while searching for I have no idea what, someone where I work came across a document or two that contained sensitive personal information. They should not have found this information, yet there it was. They were using a tool we have called Goldfire Researcher, a very powerful semantic search engine developed and sold by Invention Machine. The discovery precipitated an order from our IP Attorney to immediately remove access to all the databases generated from our huge share drive. This occurred almost on the same day I had another of Invention Machine’s products, Goldfire Innovator, installed on my machine and a couple of days before I was to receive training on its use. Needless to say, the training became exceedingly difficult as there was nothing to use for research; at least nothing internally.

Today we are to meet with two of our lawyers and decide how to proceed. I don’t believe anyone thinks it is in the best interests of the company to not be able to search our own data for useful information in either performing our daily work, or in our innovation initiatives. I understand the position of the lawyers. Being one myself (though that is not my position where I work), I appreciate the need to protect the privacy of our employees and the information that was found should not have been where it was. We need to put a process in place that allows access, yet protects all kinds of sensitive information. It will be interesting to see just what we come up with.

I should point out this is not a shortcoming of the tool(s) that Invention Machine provides. Rather it is, in some ways, a fortunate side-effect of the power of the tool(s) that we have surfaced areas where others have not been adhering to the procedures we already have in place for protecting this kind of information. I am hopeful we will find a way out of this quandary soon and will be better organized with respect to all our data as a result.

Rick