Archives for posts with tag: Knowledge Management

When addressing the idea of tacit knowledge in respect to knowledge management, most descriptions focus on the tacit knowledge IN organizations – that is, the tacit knowledge of the individual members of the organization – and how to capture and share that tacit knowledge. While I believe it is important to understand this tacit knowledge, I’ve always been more attracted to an understanding of the tacit knowledge OF an organization, what it is the organization as a whole ‘knows.’

As with individuals, organizations operate based on the tacit knowledge they possess and their ability to act on that knowledge when needed. In the human brain it is the connections between neurons – and the ability of the brain to reorganize those connections to meet the situation – that makes up the intelligence and tacit knowledge of the individual. In organizations, it is the connections between people. (see this post of mine from 2006 for a bit more on this.)

Many years ago, in one of my first ever blog posts, I wrote that “KM is the neuroscience of an organization.” After reading Is Enterprise 2.0 the neuro-organization? a couple of days ago, and a brief discussion with Harold Jarche (@hjarche), I was once again curious.

Here’s a start. (Definitions from Wikipedia)

Neurology: a medical specialty dealing with disorders of the nervous system. Specifically, it deals with the diagnosis and treatment of all categories of disease involving the central, peripheral, and autonomic nervous systems, including their coverings, blood vessels, and all effector tissue, such as muscle.  –>OD ?

Neuroscience: the scientific study of the nervous system, the scope of neuroscience has broadened to include different approaches used to study the molecular, developmental, structural, functional, evolutionary, computational, and medical aspects of the nervous system. –> KM?  IT?

Psychology: the scientific study of human or animal mental functions and behaviors, psychologists attempt to understand the role of mental functions in individual and social behavior, while also exploring underlying physiological and neurological processes.  –> OD? Training/Learning?

Psychiatry: the medical specialty devoted to the study and treatment of mental disorders—which include various affective, behavioural, cognitive and perceptual disorders; mental disorders are currently conceptualized as disorders of brain circuits likely caused by developmental processes shaped by a complex interplay of genetics and experience.  –> HR?

Way off base? On the right track?

Yesterday’s #kmers chat focused on the topic Retaining the Knowledge of People Leaving your Organization.  Quite a bit of discussion around the topic, including questions about whether you should try to capture knowledge from those leaving, how you should do it, etc. etc.  Personally, I agree with V Mary Abraham (@vmaryabraham) when she says:

Ideally, move to system of #observable work. Then people disclose info & connections as they work & before they leave.

That way, the knowledge that is shared is in the context of a current action and not just information sitting in a repository somewhere.

This is a question that I – and many others – have wrestled with for many years now. Here is something I originally posted in Sep 2004 on the question. This is an unedited copy of that original post; I may come back later and give it a fresh coat.

- – — — —– ——–

For many years now I’ve read about and been involved in discussions about the impending retirement of baby boomers, the effect this will have on institutional memory, and what can be done about it. Most of my interest in this at the time concerned the impact on the federal government workforce, which will be very hard hit since the retirement age is a bit lower than the populace in general.

Though I’ve not yet read it, the book Lost Knowledge by Dave DeLong addresses this problem in great detail (more on the book can be found here, here, and here). A snippet from the book’s website:

Dr. David DeLong, a research fellow at MIT’s AgeLab, has just created the first comprehensive framework to help leaders retain critical organizational knowledge despite an aging workforce and increased turnover among mid-career employees.

Like most discussions of the topic I’ve been involved in, the book seems to focus on the negative aspects of people leaving, and taking their knowledge with them. However, I have been reading James Surowiecki’s The Wisdom of Crowds and think that we may be missing out on an opportunity to actively reinvent the corporate knowledge as we try, probably in vain, to keep the old knowledge around.

Granted, there is some information and there are many processes that must be recorded and retained. This the basic infrastructure of how an organization functions. But if you simply take the knowledge of people who are leaving and transfer that to the people that are replacing them, you are effectively eliminating the value of the “new blood” coming into the organization. Or, in the words of Surowiecki, you are maintaining homogeneity at the expense of diversity.

Organizational memory, like human memory, can be a stubborn thing to change and often results in the this is how we’ve always done it syndrome. An excellent description of memory formation can be found in Tony Buzan’s The Mind Map Book (sorry for the lengthy quote, but it bears repeating in whole):

Every time you have a thought, the biochemical/electromagnetic resistance along the pathway carrying that thought is reduced. It is like trying to clear a path through a forest. The first time is a struggle because you have to fight your way through the undergrowth. The second time you travel that way will be easier because of the clearing you did on your first journey. The more times you travel that path, the less resistance ther will be, until, after many repetitions, you have a wide, smooth track which requires little or no clearing. A similar function occurs in your brain: the more you repeat patterns or maps of thought, the less resistance there is to them. Therefore, and of greater significance, repetition in itself increases the probability of repetition (original emphasis). In other words, the more times a ‘mental event’ happens, the more likely it is to happen again.

When you are trying to learn something, this is obviously a good thing. However, the very nature of this learning process makes it more difficult to learn something new, especially if it is very different (“off the beaten path”). By pointing new people down the paths of the people that are retiring, you are ensuring that the well known paths will continue to thrive and that it will be harder to create new paths through the forest.

That’s fine if your goal is to continue on the path you are on, but it brings to mind an old proverb I saw somewhere: If you don’t change the path you are on, you’ll end up where it takes you.

——– —– — — – -

“Keep me in the loop.”

This all too common expression is – or should be – the bane of anyone trying to implement, or just use, a social media approach to collaboration and communication. What it really means is…

“I want to know what’s going on with your project, but I don’t care enough to actually spend my own time keeping up with what’s going, so please take time out of your own busy schedule and figure out what information I need to know and then make sure you get it to me. I may or may not bother to read it once you’ve sent it to me.”

The next time someone asks you to “keep me in the loop”, let them know where the conversation is happening and offer to grant them access. If they don’t take you up on it, then they don’t really care. If they do take you up on it, they may never join in. But they might, and their participation will be that much more valuable because they are there intentionally, not accidentally.

Of course, this goes both ways. Next time someone talks to you about a project that you are interested in, don’t ask them to keep you in the loop. Instead, ask them, “How can I join the conversation?”

The concept of “knowledge curator” has been creeping slowly from the back of my mind to the front over the past couple of years, and received a couple of jolts over the weekend that resulted in one of those elusive “aha moments”.

What we need are curators of knowledge,
not managers of knowledge.

First, I noticed the blurb “curated content from Flickr” when I used the Flickr module on a Squidoo lens.

Second was a quote from Liz Danzico (that I found via Signal vs. Noise blog).

A portfolio of work is a curated experience. … but oftentimes, a portfolio only contains final pieces, as applicants are overly concerned about presenting perfection. Polish doesn’t communicate process though, and therefore I’m left with only part of the story. Messy problems — and how applicants work through them — can show a great deal more in a portfolio than one finished, airtight solution.

I didn’t know it at the time,but this all started back in November 2005 with an article titled Technology makes it easy to ‘remember,’ the trick is learning how to forget, in which I wrote:

My early days in Knowledge Management included a lot of time developing, deploying, and getting people to use “knowledge repositories.” (At least trying to get people to use them.) … I finally realized one day that the problem has become not, “How do we remember all this knowledge that we’ve learned?” but rather, “How do we forget all this knowledge we’ve accumulated that we no longer need so we can focus on what we do need?”

I also noted a quote from the book The Trouble with Tom by Paul Collins related to the need to “eliminate” memories:

Memory is a toxin, and its overretention – the constant replaying of the past – is the hallmark of stress disorders and clinical depression. The elimination of memory is a bodily function, like the elimination of urine. Stop urinating and you have renal failure: stop forgetting and you go mad.

It was this latter quote that was in my mind last summer when, in The importance of forgetting,  I wrote about John Medina’s thoughts on the question of memory and forgetting in Brain Rules:

The last step in declarative processing is forgetting. The reason forgetting plays a vital role in our ability to function is deceptively simple. Forgetting allows us to prioritize events. Those events that are irrelevant to our survival will take up wasteful cognitive space if we assign them the same priority as events critical to our survival.

As I noted then, this is no less true in the organizational context of knowledge/concept work.

Simply capturing everything in document repositories and best practices, without the ability to forget – or supercede – any of it, takes up a lot of “cognitive space” that organizations could be putting to other wise good use.

The trick is figuring out how to forget, and how to figure out what to forget.

When I first discovered the Cynefin framework, I remember thinking, “Exactly.” It is one of those things that once I saw it I realized how obvious it was, at least in hindsight after someone had pointed it out. Of course, I’ve been trying to actually figure it out ever since.

Dave Snowden blogged recently that he is putting together a history of Cynefin, and provides a brief timeline of its origins and where it is now. He also includes a diagram showing the diagram as it was in 2000 compared to what it is now:

My most recent post that included Cynefin looked at it in the context of  concept work and the role of deliberate practice in achieving mastery. The basic premise of that post was that success in the chaotic domain requires mastery, which is the result of a lot (10,000 + hours) of deliberate practice. Even though originally developed with a focus on knowledge management and communities of practice, the origins of the model, as shown above, seem to lend some validity to my understanding.

An added bonus to Dave’s blog post is the comment from Steve Barth (the emphasis is mine):

Something I’ve been thinking about lately relates to the original knowledge-training axis in the early drawings. It comes up working with clients to differentiate and merge knowledge management and organizational learning programs. Increasingly, I believe that knowledge and learning are often polar opposites, and the order/unorder sides of the model make this clear. Simple and complicated emphasize what we already know—or at least believe to be true—and further investigations and analysis must either accept or falsify these premises. We assume that our assumptions are correct. On the other hand, learning is largely about what we don’t know. That is, we must assume that our assumptions could be wrong.

I’m looking forward to the full history.

Creative Commons License
Brett's Waste Blog by G. Brett Miller is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License. Based on a work at blog.gbrettmiller.com.

legally blondes dvd In the Loop earthsea dvd justice league movie fly movie online madison square movie velveteen rabbit music watch swordfish movie freedom writers movie short circuit 2 1988 movie watch max manus movie madame bovary movie wet hot american summer dvd satan 's little helper cast buffalo soldiers movie danny glover Frankenstein Unbound man in the chair christopher plummer next 3 day weekend hellraiser deader trailer monster house movie reviews