Thursday, 31 December 2009


KM road map



From the website of the Pennsylvania Office of Administration, a pretty good "KM roadmap" which summarises many of the principles we espouse in Knoco for KM implementation. I quote their list

KNOWLEDGE MANAGEMENT ROADMAP

If your organization is interested in
managing internal knowledge, the following items will help you get started on
your journey:

Review current business processes for efficiency and
effectiveness
Build a business case to secure Senior Management support that
identifies processes that can be shortened, timelines that can be decreased,
expected impact of retirements, etc
Conduct an assessment to determine your
organization's readiness
Identify knowledge that is critical to your
business
Define the scope of your knowledge management efforts where
capturing and reusing knowledge will yield the highest return; consider using a
pilot group
Align knowledge management efforts to the organization's
business strategy
Analyze knowledge that exists in your organization
To
the extent possible, leverage existing information technology investments
Focus on explicit and tacit knowledge
Develop a conceptual plan of your
knowledge management system
Build and deploy a results-driven system
Include cultural considerations to sustain knowledge management practices
Measure the success of your knowledge management initiatives against
established goals
Stay abreast of latest developments and trends,
incorporating best practices and success stories.

Wednesday, 30 December 2009


Jefferson quote




Thomas Jefferson
Originally uploaded by cliff1066™

“He who receives ideas from me, receives instruction himself without lessening mine; as he who lights his taper at mine receives light without darkening me” – Thomas Jefferson

(thanks Kevin Hayes)

Tuesday, 29 December 2009


Intellectual recycling – green thinking for the knowledge worker



We are all into recycling. Recycling conserves sparse resources. But what about intellectual recycling? Recycling of ideas, approaches, processes? Maybe this is what KM is all about?

Let’s follow this train of thought for a bit. Let’s think of a busy team with very constrained resources (people, time, energy, budget). Let’s suggest they apply some green principles to their knowledge work. Let’s suggest they consider Reduce, Reuse, Recycle.

Reduce. Maybe they don’t need to do this knowledge work at all. Maybe they can actually reduce the amount of work they need to do. There are various processes available, such as Rightscoping, Technical Limit, or customer interrogation, designed to reduce unnecessary work. This could save a lot of their resources

Re-use. If they do need to do the work, perhaps they can reuse solutions which already exist. Perhaps they can reuse something off-the-peg, which has been applied elsewhere in the business. This can save almost as much intellectual resource as reducing the work.

Recycle. If there is no solution they can use off-the-peg, perhaps they can recycle existing ideas. Perhaps they can take what has already been done, and adapt it for their own situation; re-craft it for their own context, and improve it to fit their need. This requires resource, but nowhere near as much as creating the solution from scratch. Peer Assist could be a powerful tool here.

If they can’t reduce, can’t reuse and can’t recycle, then they have to create or invent their own solution. This is the most costly approach (although as I have argued in this blog post, it’s often the solution that the teams find most fun).

I can imagine a rightscoping meeting, where a team divides their project into tasks, and asks, for each tasks, can we reduce? Can we reuse? Can we recycle? Or do we need to create and invent? This could be an excellent format for ensuring that innovation is focused only on those tasks and activities where innovation is needed. Think of the intellectual resources that could be conserved by such a recycling approach!!

Wednesday, 23 December 2009


Heirarchies of Knowledge






Podium
Originally uploaded by tandemracer

When you are building your store of explicit knowledge for the organisation, you need to make it clear how much validity your documentation has. Knowledge comes in different levels of trust, and you need to make it clear to the reader what level applies to all documentation. There are three main levels

1. Mandatory, or “Must Do”. This is the level of company standards, and everybody reading this particular process documentation needs to be very clear that they need to follow exactly what’s written. If there is a major problem, they need to get in touch with the process owner and discuss it with them, but that the default should be to follow this documentation exactly.

2. Advisory, or “Should Do”. This is the level of best practices, and everybody reading this particular process documentation needs to be clear that this is the best way to approach this particular process, based on current company knowledge. However there is always the possibility to improve on best practice, and if somebody can find an even better way, then that’s great. So Advisory process is advised, but not compulsory. However if people ignore advisory knowledge and things go wrong, some awkward questions may be asked.

3. Suggested, or “Could Do”. This is the level of good ideas or good practices that others in the organisation have used, which the reader should feel free to reuse or re-adapt to his or her own context. These good ideas can still save the reader a lot of time and effort, but there is no real requirement to copy them.


In BP drilling in the late 1990s, corporate process documentation was divided into these three levels of validity, and these were labelled Principles, Processes and Practices. This labelling made it very clear to the reader how much scope they had to vary the process from what was in the documentation.

My colleague Tom, in his book Knowledge Management for Operations and Manufacturing, tells about the BP Operations Exzcellence toolkit, which illustrates this well.

The BP Operations Excellence toolkit is structured around the level of
validation that has been applied to the knowledge. At one level there is the
highly vetted, approved knowledge in the form of corporate standards and
required practices, which are referenced under the heading ‘The BP Way’. At the
opposite end of the spectrum is the knowledge in the Question and Response
system, eCLIPS, which is totally unvetted. BP went a step further and provided a
'health guide' to the advice you were receiving.

Captured knowledge is
presented in a hierarchy, as follows;

The "BP Way" These tools describe
the way BP does business (ie BP policy). This should be the first place to look
when identifying ways (the "what" and "how").

Good Practices These
describe good practices identified for the relevant elements by either
experience from operating assets (eg from OVP assessments, eCLIPS etc) or
subject matter experts.

People These are people you can contact for help
with closing your OVP score gaps for the relevant elements.

Communities
These are communities of practice skilled in the relevant element.

Community discussion forum This section links you to any questions (and
responses) that have been asked about the relevant OVP element and allows you to
ask the Community if you have been unable to find an answer in the toolkit. All
entries in eCLIPS are purely voluntary and are not validated by Subject Matter
Experts.

This hierarchy is very important as it gives the reader a sense
of how reliable the knowledge might be. Thus if the advice provided is in the
form of The "BP Way" then the reader knows that this is a fully validated and
approved policy or procedure and can be followed with confidence. At the bottom
end of the scale, advice provided via the eCLIPS system, which is not validated,
needs to be treated with a lot more caution.

Tuesday, 22 December 2009


Company Procedures are the corporate memory





Learning, implies memory. If there is no memory, there can’t be learning. A baby learns through stimuli and responses from the outside world, comparing these to existing mental models held in memory, and updated her mental models over time. But where is the memory of an organisation, that allows such learning?

You can’t rely on the memory of the employees to be the totality of the memory of the organisation, as employees come and go, and the human memory is, after all, a fragile and fickly thing.

In addition to this human organisational memory, we can make a strong case for organisational structures, operating procedures and processes also forming a core component of organisational memory. Processes and procedures are built up over time, and represent the company view of “how we do things”. Employees follow the processes, and repeat “how things are done”. The processes hold and propagate the patterns for behaviour, and for the way work is conducted. If the organisation is to learn, these processes must evolve over time.

The concept of evolving processes as part of the learning loop is recognised by many learning organisations. One of the learning professionals in the UK Military said to me “what is doctrine , if not the record of lessons learned?” Similarly the head of Common Process at BP explained BP Common Process as being the embedded knowledge of how to operate.

Monday, 21 December 2009


Ask the Audience, Phone a friend





When it comes to giving people access to tacit knowledge, organisations tend to fall into two camps. We can call these the “Expert” camp and the “egalitarian” camp.

In the Expert camp, the organisation figures that if people want access to tacit knowledge, this had better come from the Experts. So they set up experience directories, where you can find people with experience on specific topics. They set up “Ask the Expert” systems, where you can type in a query which goes to the relevant expert to be answered. They may also set up closed-membership communities of practice, where the experts can get together and discuss “best practices”.

In the Egalitarian camp, the organisation figures that if people want access to tacit knowledge, then this knowledge will be dispersed within the community of practitioners. So they set up expertise directories, where you can find all the people with esperience in specific topics. They may set up open-membership communities of practice, where practitioners all of the company can contact each other for help and advice. They set up “Q&A” systems, where you can type in a query which goes out to the community membership, and anyone with knowledge to offer can answer.

In the first model, knowledge is assumed to reside in the heads of the experts. In the second model, knowledge is assumed to be dispersed around the community. The first assumes that if you need knowledge, you will “phone a friend”. The second assumes that if you need knowledge, you will “ask the audience” (to use the analogy of the popular TV series, “Who wants to be a Millionaire”)

I can think of three cases where you might want to go down the Expert route, but in the majority of cases I am all in favour of Egalitarianism. I think that experts can become bottlenecks, that we can’t assume the experts can hold the totality of knowledge in their heads, and we can’t assume that the expert will remain up to speed with all the developments in the field. Consider a company with 1000 people working in a discipline, with an average of 5 years experience each. There are twenty company experts with 25 years experience each. If we sum up the years of experience, the experts hold 500 years, the community holds 5000 years. No expert can keep on top of what’s happening out there with the 1000 practitioners, and very often the REAL expert if the grizzled old foreman in a remote operating unit, who knows more about keeping the machinery running than the whole of head-office put together. And finally, you can’t build a community if the community never interacts, and all the interactions are between individuals and experts.

So what are the three cases where an Expert system is better?

The first case is where the demographics of the company is highly
skewed to junior people. We see this, for example, in the national oil companies of the far east, where there are a few experts who have been in the business for decades, plus thousands of people fresh out of graduate school. Here the bulk of the community is inexperienced, and there would be no point in asking the audience.

The second case is where the knowledge is very mature, and not changing much at all; where all the answers are known, and where innovation beings to look like tinkering. There would be no point in asking the audience, as anyone with any knowledge at all on the topic would know the answer. Here you are better off asking a single authority (or even better, just reading the manual).

The final case is where the knowledge is very abstruse, and only one or two people know about it. The company expert on Internet law, for example, or the one person in the company who knows about Environmental Impact Statements in the Gambia. Here there is no community – no audience to ask. You have to find the friend to phone.

And yet, even outside these three cases, I have found clients who really can’t see that “asking the audience” is valid. They are deeply culturally linked to the Expert model. And I don’t know why this is, other than potentially some deep cultural bias. I have seen this bias in South Africa and South America, and certainly in the latter area is may be linked to a hierarchical deference to intellectual authority. I wonder if there is some link to the Hofstede cultural dimension of Power/Distance Index – but linked to perceived intellectual status.

I suppose the answer is that you can use both lifelines. You can ask the audience (through community Q&A systems), and you can phone a friend, by using the company Yellow Pages to identify those few people with deep expertise in the area you need to learn about. And the great thing about KM In an organisation, compared to the TV game, is that you can use both lifelines at once, and you can use each of them as many times as you like.

Saturday, 19 December 2009


Learning, or being taught? (quote)




Sir Winston Churchill
Originally uploaded by
cliff1066™

Personally I'm always ready to learn, although I do not always like being taught.


- Sir Winston Churchill

Thursday, 17 December 2009

2-5-1 for AARs




five
Originally uploaded by woodleywonderworks

A great story via a Nancy Dixon session at KM world, and then retold by Robert Swanwick giving us an interestign approach to After Action review in quiet cultures


"Karuna is part of the military in Singapore. He starts out by setting the scene and explaining that military personnel in Singapore are very reluctant to share their opinions due to their culture. This can make for a very quiet after-action-review (AAR). In order to maximize the value of the program, they need to coax out the tacit knowledge. So, his team developed a framework they call 2-5-1. It goes like this:

2
■ Who you are
■ Summary of your experience

5 fingers
■ Little finger – what parts of the effort did not get enough attention
■ Ring finger – What relationships were formed, what you learned about relationship building
■ Middle finger – what you disliked, what/who made you frustrated
■ Pointer finger – what you would do better next time around, what you want to tell those who were “in charge” about what they could do better
■ Thumb (up) – what went well. What was good.

1 – the most important takeaway from the effort

This is a framework that everyone can relate to. It is also a framework that is easily remembered and easily walked through while standing up in front of a group. Those who are uncomfortable speaking in front of a group can use one hand to grasp the corresponding finger on the other hand for each section…adding to their comfort level by giving them a prop".

Good story - good method! I remember how we struggled with AARs in Japan, back in BP days. This methodology could have been very helpful.


another great Boston Square




I am sure I have said before, that Boston Squares are great for pulling apart a topic, and allowing you to untangle some thoughts which otherwise might get lumped together.

Here's one I used the other day, and it was useful to help an organisation realise how polarised it's KM thinking had become.

Here we pull apart the KM world on dimensions of Knowledge Push and Knowledge Pull (which you might call "Sharing" and "seeking"), and the dimensions of Explicit and Tacit. We get 4 quadrants, which we could call Ask, Tell, Search, Share

This helped the particular organisation see for themselves that their KM approach was predicated only on Share - the Push of Explicit material. 75% of KM space was not being addressed!*

How much of this diagram does YOUR KM program address?

*Part of the problem was that they had rebadged KM as "knowledge sharing", which led them down that particular track.

Wednesday, 16 December 2009


Knowledge is like money



Money 2
Originally uploaded by borman818
“Knowledge is like money: to be of value it must circulate, and in circulating it can increase in quantity and, hopefully, in value.” Louis L'Amour

Of course, knowledge differs from money in one key respect - you can give it away, and still keep it yourself

Monday, 14 December 2009


KM and flying geese



You know what geese fly in a V formation? It's all about efficiency. The lead goose flies as normal, and all the other geese make use of the trail he or she has created, to save energy. In fact, they reinforce the trail, for the sake of the others flying behind. The birds take turns being in the front, falling back when they get tired. They could save up to 50% of their energy if they flew wingtip to wingtip, but this would require some pretty clever flying. Generally they save more like 15% of their energy (see reference).

The second benefit to the V formation is that it is easy to keep track of every bird in the group. Fighter pilots often use this formation for the same reason.

This is a pretty good metaphor for KM. instead of lead goose, think of the lead learner. If they leave a trail of their knowledge that others can re-use, then the followers save energy (or save time and money). In fact, they reinforce the trail of knowledge, for the sake of the others following behind. We are not always learning leaders - we tend to take turns being in the front, so the learning is not always one way. We create efficiency savings for the company, and data from the oil sector suggests that learning from projects can give efficiency savings in the 10% - 15% range, with occasional savings in the 40% range (see here for example).

Maybe the visibility thing is part of the metaphor as well. KM not only allows efficiency savings, it allows us to keep track of every project in the group.

So let's make use of the knowledge of the leaders, let's fly in formation, let's save energy, let's avoid re-use, let's keep in touch with each other. Let's learn from the geese!

Saturday, 12 December 2009


Consistency quote



Clone troopers
Originally uploaded by adactio

Consistency requires you to be as ignorant today as you were a year ago.
- Bernard Berenson

Friday, 11 December 2009


Community roles - job titles




A very interesting list from the CP squared wikiof community leader job titles, submitted by members of the cp squared community and posted by John Smith.


  1. Community Content Director
  2. Community Content Expert
  3. Community Content Specialist
  4. Community convener
  5. Community coordinator
  6. Community facilitator
  7. Community Guru
  8. Community Knowledge Director
  9. Community Knowledge Expert
  10. Community Knowledge Specialist
  11. Community Knowledge/Content Guru
  12. Community leader
  13. Community manager
  14. Community steward
  15. Content facilitator
  16. Executive Community Specialist
  17. Executive Content Leader
  18. Executive Content/Knowledge Master
  19. Executive Knowledge Leader
  20. Executive Network Builder
  21. Executive Network Director
  22. Executive Network Specialist
  23. Executive Steward
  24. Executive Thought Leader
  25. Key Domain Expert
  26. Key Opinion Leader
  27. Knowledge steward
  28. Lead Domain Director
  29. Leading Domain Director
  30. Network Guru
  31. Network leader
  32. Principal Domain Director


The list was initiated by Lauren Klein based on input from her network and members of com-prac


Winter 09 newsletter - metrics issue




Winter Meal
Originally uploaded by Jan Tik

You can find our Winter 09 newsletter here

This issue is all about KM metrics

Compliments of the season to you

Thursday, 10 December 2009


KMAS


I think all of us who worked in the BP KM team in the 1990s would agree that the KM program was terminated too early. We had tested the tools, we had piloted the framework, and we were poised to roll out KM. We had a vision of "99 in 99" - 99 knowledge managers in place across the organisation by the end of 1999.

Then, as history records, BP became embroiled in what was then the largest industrial merger in history - the merger with Amoco - and the KM program (together with very many other programs) was terminated early.

One thing I really regret about this early termination was that we never got to experiment with what we termed "KMAS" - the Knowledge Management Assurance System. This was very much conceptual, and we hadn't really progressed far beyond the name, but the parallel was with PMAS, the people management assurance system.

An assurance system is the system you put in place, to make sure something works. PMAS was the system BP put in place to make sure its People Management system worked. KMAS would have been the system BP put in place to make sure its Knowledge Managament system worked. KMAS is not KM, it was the assurance system for KM. Without the assurance system, there is nothing to sustain KM, and that's just what happened in BP. After the early termination of the team, KM faded away, with the exception of a few hotspots like Drilling. It took another 6 years for KM to be re-established, and for assurance systems to be put in place which would sustain it.

In Knoco, we refer to assurance systems as Governance, and you can find a few posts on governance in this blog, by using the search bar. We feel we've got a pretty goood handle on governance now. Having seen it fail in many places and succeed in a few, we think we know what the sustaining factors are. But if we had had that extra year in BP to put KMAS in place, we might have had that knowledge 6 years earlier.

For more details on effective governance, drop me an email and I will send you a reprint of my article "Masterclass - Sustaining the Knowledge Management Culture". Nick Milton from Inside Knowledge, March 2007

Wednesday, 9 December 2009


Einstein quote




Einstein
Originally uploaded by Tábata - Happy Artes
“Knowledge is experience; everything else is information.” Albert Einstein


KM - battle of the acronyms





Seven
Originally uploaded by thrig

There are some great Acronyms in KM. Some of my favourites are below. Please share your favourites!

ROCK, the Shell acronym for Retention Of Critical Knowledge

KAMP, not as butch as ROCK, the Rolls Royce acronym for their Knowledge Acquisition and Modelling Process

KISS LIPS, perhaps more of a mnemonic than an acronym from Darius Bara, published in the School Business managers publication just4SBMs, to remind you what needs to be covered in Knowledge Retention (Knowledge, Impressions, Solutions, Stuff, Lessons, Information, People, Status)

BLESSINGS, my current favourite, from Henky Chahyadi at PT Sinar Mas Agro, which stands for the Backbone of Learning- and Experience-Sharing System for INcoming GenerationS



Friday, 4 December 2009


Pull together please, not apart



Tug-of-war
Originally uploaded by UNC - CFC - USFK

Knowledge management is at a crossroads.

Not only has KM spending been slashed in many enterprises as a short-term reaction to the recession, but also the core identity of the topic is becoming blurred as competing factions bid for ownership of the term. KM is a fuzzy term to start with, and is also a term that can be looked at through many lenses – the lenses of people, of process, of technology; the lenses of tacit and of explicit; the lenses of Connect and Collect, of Push and Pull. The risk of a fuzzy field which can be viewed in many ways, is that people can assume that their view is the commanding view, if not the only view.

So there is a view that KM is now about the management of content and information; a new term for librarianship for example (I note that the KM section of the International Federation of Library Associations call themselves “the voice of global KM”). This is a view of KM through the “Collecting" and "Explicit" lenses, focused on Collections of Explicit knowledge.

Or there’s another view that KM is dead, and that social networking is doing what KM was supposed to do - “social computing is the new KM”. Someone passed me a business card the other day that said “Web 2.0 = KM”. This is a view through the “Connect” and “Technology” lenses. Yes, it involves people, but the solutions to people issues are claimed to be technology solutions, and the view focuses on Connection technology.

Or there’s still a very strong feeling that KM is a content-technology field, whether it’s SharePoint or KM platforms or some new version of user-populated portals. This is a view through the “Collect” and “Technology “ lenses.

Or there is a view, coming from the training field, that KM is a component of blended learning, and therefore an offshoot of L&OD. Taking this to its limit, the government sees Knowledge as the province of the Universities; for them Knowledge Transfer is about university partnerships and spinoffs, and about smart people with smart ideas which can be commercialised. This is a view through the “Connect” and “People” lenses.

Or there is the view that KM is a mindset, that knowledge cannot be divorced from the knower, and that KM is all about people and about behaviors and culture. This is a “People” “Tacit” view.

Or there is a view that KM is linked to performance improvement, and to learning from experience, and to disciplines such as 6 Sigma, Kaizen, BPR and After Action review. This is the “Process” view, sometimes taken into a "Process, Technology" view by those who offer workflow technology under a KM banner.

At best some of these viewpoints overlap, but at worst they pull in opposite directions. At very worst, people start to claim their viewpoint as the only viewpoint for KM – “Web 2.0 is KM”, “Content ownership is KM”, “KM is culture” and so on. This is where the reported “Wars” come from (see here for example).

There are no one-size-fits-all solutions in KM; we all know that. But there is a set of principles around which KM can consolidate, and around which it needs to consolidate if the field is to survive. One of the most basic of those principles is that KM is a holistic field rather than a polarised field. It’s a field of “both/and” rather than “either/or”. It’s a field where we need to address both connect and collect - connection of people, and collection of content. We need to address people as well as technology as well as process as well as culture. We need to look at push as well as pull, and tacit as well as explicit.

You cannot take one aspect of KM and claim that it's the whole field. That's like saying "Building houses is all about roof tiles". "No it's not, it's all about retaining walls". "No it's not, it's all about foundations". Building a house is about all of these things, fitting together, to provide a secure and stable structure which is fit for the inhabitants' purpose.

By the same token, KM is about all of these things, fitting together, to provide an effective and efficient structure (or system, or climate, or ecosystem - call it what you will) which is fit for the inhabitants' purpose.

KM is simple but not easy, and it becomes impossible if connect and collect, technology and people, tacit and explicit, pull in opposite directions. I look forward to a future where the social computers, librarians, trainers and technologists will come together to develop the whole field, working as a team in a holistic approach to knowledge. We have to ensure that all elements are addressed in a coherent approach to delivering value through knowledge, if it is to deliver its real value.

The forces that pull KM together are the forces driven by business need. Rather than starting from solution-focused questions like “how can I introduce SharePoint” or “What is my Social Computing/Content management/eLearning strategy”, KM will need to start from outcome-focused questions like “how do we spread our sales knowledge from the old markets to the sales-teams in emerging markets”, or “how do we ensure our projects never repeat a mistake or inefficiency”? In almost every case, the answer to that question will involve a blend of technologies, a focus on people as well as content, new processes, push and pull of both tacit and explicit knowledge, and a hefty dose of culture. It will require us all to pull together, rather than to pull apart.

Thursday, 3 December 2009


Quantified KM Success Case Study 12


Here you can read about Cisco systems use of collaboration to save US$691 million and to increase productivity 4.9 percent in a single fiscal year (2008), representing a 900% ROI.

"Specifically, research from the Cisco Internet Business Solutions Group (IBSG) shows that in fiscal year 2008 Cisco used collaboration technologies to reduce costs by $251 million, to increase profit margin by $142 million, and to generate time savings for employees worth US$380 million. The total cost to achieve these benefits was just $82 million, resulting in overall net savings of $691 million".

I was struck, in this study, by the focus they applied (prioritising what they called "impact zones"), their staged implementation approach (very similar to the Knoco staged implementation approach, with its assessment and trialling stages), and by the clarity of leadership expectation that they developed, especially the accountabilities associated with this.

New behavioral expectations need to be clearly defined, developed, and
incorporated into an organization’s culture. Leadership and management systems
need to align with hew collaboration efforts for the proper behavior expectations
to be set, operationalized, and measured (that is, made accountable).



So - well done Cisco


Rejection of Authority quote



Thomas Henry Huxley
Originally uploaded by Simon Harriyott
Every great advance in natural knowledge has involved the absolute rejection of authority.
- Thomas H. Huxley

Wednesday, 2 December 2009


More on stories



"Story Road"
Originally uploaded by umjanedoan

I am a great believer in the power of stories in Knowledge Management, as a key tool in the KM toolbox. However I have seen some pretty awful use of storytelling as well, where the stories were used as pretty much the only KM tool, with limited results.

I saw an application of KM this week, where the approach was to create case studies, and then invite the learning to read these, and to draw out their own learning. Not a bad idea, but the case study library now runs at 100 case studies, and that's a lot to read! You are making it very hard for the learner.


Thats why I was pleased to read this post from Donna Fitzgerald in the Gartner Blog Network, where she says

"I think the trick is having the right stories and knowing when to use them to illuminate or contextualize advice. Stories that are quick and illustrative without sounding preachy. The trick is also having the right forum to tell the stories in, because part of the value of the stories is the fact that they really are personal".

This quote encapsualtes what I feel about the use of stories. There are several key words here

"Illuminate or Contextualise". The stories are there to give context to the knowledge, rather than to be the sole conduit of the knowledge.

"Quick and Illustrative". The stories should not outlive their welcome

"Personal". The best stories are those told in person, by the people involved, by the people who have the knowledge.

All of these are key to success in the use of storytelling in KM.

Tuesday, 1 December 2009


Knowledge Assets



Knowledge Asset is a common term, but one with a variety of meanings. Sometimes people talk of documents as “knowledge assets” (Google), seeing a document as containing explicit knowledge, and therefore being an asset.

I would look at it slightly differently. I would see an asset as something that brings value, and therefore a knowledge asset should provide valuable knowledge. A document may not be knowledge – it may just be a document – but some documents do provide valuable knowledge. A document is a knowledge asset, if it can provide you with valuable knowledge. If you can read it, and know what to do, then it is a knowledge asset.

A cookery book is a knowledge asset, if you can read it, and know how to cook a dish you never made before. A Haynes car manual is a knowledge asset if you can read it, and know how to change the cylinder head on your Nissan Micra. A company Wiki is a collection of knowledge assets, if your staff can read it and know how to perform new tasks.

So a knowledge asset needs to be not just a document or record, but a document or record that others can interact with to gain new knowledge which will be of value to them.

". (Knowledge) … becomes an asset when some useful order is created out of free-flowing brain-power … " Thomas A. Stewart

Blog Archive