Library clips

sharing ideas thoughts and feedback

August 25, 2008

A Facilitators responsibility in forums

It’s really important to get closure on communications and discussions when they are done out in the open.

Email

- Someone emails a question
- A person phones you with a solution

What you have here is an unanswered email, as the answer was via the phone

But who cares, you know the answer, and on-one else can see that email

Forum

This scenario changes when the interaction is out in the open

- Someone posts a forum topic
- A person phones you with a solution

What you have here is an unanswered forum topic, as the answer was via the phone

A who cares approach is unwise

- others may be interested in an answer
- they may think these forums don’t work every time as there are lots of unanswered topics
- someone searching the forum in the future will see a topic without an answer when indeed an answer did result, but they weren’t physically there to be part of it.

My word of good practice is always answer that forum topic if an answer exists
- even if all members of the forum know the answer as it was discussed in a meeting, still document an answer, so future people will also be informed (and also to remind ourselves, as we are often forgetful)

The forum or community Facilitator can convey this recommended behaviour to members, but in the end it’s up to them to pick up the pieces or reinforce the correct behaviour

What if no-one answers the forum topic?

Well, so be it. But it’s also good practice if the Facilitator tries to source an answer for their member, or at least contact them individually to let them know they are not being ignored.
- this is more for new communities as people are finding their feet…and wouldn’t be practical for communities with large numbers

What about forum topics that are off-topic?

Thankfully in the forums we use we can move a forum topic (with its replies) to the correct forum

What about forum replies that are off-topic?

Now this is something we can’t do anything about.
Often our forum topics are long threads and people do their best to rename the subject line when the topic veers off a little, but sometimes a reply becomes so off topic that I would like to move it or rather make it into a new topic.
That is, I would like the ability to convert a reply into a topic

In a past post I wrote about this as the gardening aspects of a Facilitators role.

Distilling Conversations

Another gardening task is to take the cream of the conversations and reference them elsewhere, otherwise they just fall off the radar, and you have to rely on search. I posted about this as distilling conversations, which kind of reminds me of those review type blog posts. Some might think that structuring this information in a MSWord document or a wiki, may lose it’s value or become too narrow and focused, but I think it’s important that you include the forum URL’s, the raw conversations that led to this document.

August 22, 2008

140 characters to knowledge share

Filed under: blogs, km, conversation, presence

In regards to a support team or customer service I’m thinking a micro-blogging network (like Twitter) behind the firewall is a good idea. Some options are ReVou, SocialCast, and other Open Source offerings.

Using wikis and blogs are a great idea for support staff to inform each other of findings, experiences, workarounds, solutions as they happen.
This is called social learning where we learn from each other, which is essential as whoever wrote the procedures is not going to know the context of every unique situation upfront (the procedures may sometimes be a “dead-end”, and errors occur anyway), so leveraging user captured informal nuggets in blogs and wikis enables you to go “through the wall”.

But from my experience, not everyone could be bothered sharing, or has time before they move onto their next task.

The idea is we use blogs and wikis rather than an email list, but what about those people who didn’t even share using the email list.

There are many times when colleagues at work discover something in our office, but are too busy to blog about it, this is when micro-blogs comes into the picture.
People may find blog posting takes up too much time because they treat it as formal publishing, and fair enough (I covered this in my KM 2.0 Culture post). We have tried to overcome this with posting to a blog by email, making it feel very informal, now you can “flick a blog post”, just like you “flick an email”.

Anyway I feel that people will indeed post to a micro-blog as the content is the length of an SMS, ie. a max of 140 characters. This is not hard at all, and the format encourages a type of informalness.
Another low barrier is posting via email or some sort of app that’s real easy to get to and post, perhaps via the browser or a desktop widget. Actually micro-blog posting via IM feels right, it feels more casual and something people may be inclined to do, unlike a blog they are not fearing that lot’s of people will see their published post, in fact micro-blog streams fall off the radar quite quickly.

This is not a mirror replacement for typical blog content, using micro-blogs we also tend to share stuff we wouldn’t blog, more akin to IM…so this makes blogs and micro-blogs (or presence networks) very complementary.

eg. word 2003 is giving me grief with editing documents in our DMS…arghh
eg. server 3 is down, hmmm
eg.@colleagueA what dates will you be away again?
eg. wondering why personA can’t create a project
eg. it seems we don’t communicate enough to groupA, they need to be in the loop
eg. does anyone know where pluginA lives?
eg. hmm, we need a new drop down menu reason for supporting CoP issues in our database
eg. @colleagueB how did you go with getting that a user an external login?

None of the above examples suit a regular blog post, some resemble quick emails and IM, but some don’t even suit IM eg. word 2003 is giving me grief with editing documents in our DMS…arghh
- this is not a blog post, it’s more what you are experiencing now, but still you are publishing like a blog post
- it’s not email or IM as you are not directing this at anyone, you are just thinking out loud

Some of the other examples could be an email or IM, but micro-blogging allows more of an open conversation, anyone listening could jump in.

Essentially micro-blogs are very effortless and more chatty and I feel the format and social experience we have will lend it to being used more, I elaborated on this in another post:

“…I think Twitter is more prone, easier, less commited than blogs to express tacit know-how, and to offer help which also shares tacit know-how. Actually conversation is where it’s at, and an internal Twitter marketed the right way will be the optimal example of what we want out of KM 2.0 (conversation exchange).”

I expressed this in my Tumblr a little while ago:

“Twitters value contribution to the knowledge flow-spontaneous, unpolished, work in progress, thinking out loud-lends itself to this type or quality of participation due to its brief, immediate, and intimate publishing format…let’s hope internal blogs generate the same calibre of tacit value without being hindered by their format.””

August 20, 2008

7 seconds to knowledge share

Filed under: blogs, wiki, km, conversation

Gordon from Inforvark has a piece on why KM didn’t work, due to it’s non-humanistic processes:

“Who was the guy we talked to about that thing?” Enterprise 1.0 tried to address this by mandating a central repository and hierarchical classification system. It forced employees to tell some computer system what they knew and how they knew it. Only after a lot of manual data entry would the system be able to tell them something in return.

This approach failed because knowledge workers couldn’t be bothered. There was too much up-front work to make the search results useful. Without useful search results, nobody wanted to use the system. It was a classic chicken-and-egg problem. Instead, knowledge workers would just ask someone who knew rather than working with a difficult computer and move on. You simply can’t turn your workforce into programmers, historians or archivists. There’s work to be done.”

The Diving Board blog in on the same plane:

“As we all know, collecting knowledge (if it happens at all) usually involves a person or organization monitoring knowledge as it is created, and then capturing and categorizing it after the fact. This could either be the knowledge worker as they create it or someone else charged with this mission. This process is both inefficient and inherently flawed. Typically, the expert or the users themselves know what the best knowledge is, not some third party who is one step removed from the actual work. However, the experts and users lack the tools, time and incentive to carry out this critical task.”

I’ve also got a quote along the same lines from Andrew Gent in an earlier blog post.

And this is what my posts, Adapting to change with enterprise 2.0, Why km 1.0 failed in a nutshell, KM : Round 2.0, and Conversations, Connections and Context are all about.

Gordon then goes on to ponder whether enterprise 2.0 will fix this. His idea of a contribution engine is, “a tool that automatically captures an employee’s output, indexes it for later retrieval, and shares it with others in the group

I think we need to define 2 types of knowledge sharing

1. knowledge sharing can take place as it happens as a result of doing work (capturing information as it happens)
eg. making your work visible on a wiki, using a forum to get answers, using a blog for directed communications
- others get the benefit of your participation
- you are sharing by default of doing your work

2. you may discover something, have some insight, have an experience…but then you have to choose whether you will let others know
eg. found a solution to a problem you were having, and if you share it others may benefit

In a past post I have covered that the difference here is In-the-flow (Directed) vs Above-the-flow (Volunteered)

So perhaps Gordon is talking about this second aspect (Above-the-flow), as I believe an In-the-flow approach is submitting to the “contribution engine” as it’s happening…he says:

“When I was working in ECM, I used to joke about the “seven-second window.” That’s the period of time between a user finishing a piece of work and moving on to the next task. That window is the length of time users will devote to figuring out where to put content and how to share it. Do I send an email? What folder on the share drive do I use? If you can’t capture the necessary metadata within that seven seconds of “Hmmm. Where should I put this?” then you lose. The system won’t work. People are too busy.”

At work our support team use a support database where users log calls. You can see the progress trail of any given call, and the final solution…then you close the call, and it goes into the ether.

You may have closed a call before any other support worker knew it even existed. Being based in Perth, I only choose to look at calls in my location anyway, so I don’t see the calls from around the world.

At the moment if the call we just closed is unique we add it to our group blog….this is our “seven seconds”.

But this doesn’t always happen.

So an ultimate contribution engine would be if our written solution in the support database posted to the blog as we hit the close call button.

I really think blogs and the like need to be features of existing products.
(You would think our document management system would have an item comment stream (like Google Docs), instead for every document we have chosen to have a forum topic. This is one step better than using email, but the conversation is still separated from the actual document).

Blur the line of above and in the flow

The other day at a staff meeting our new Quality guy spoke about his new role and how his focus is on working with other teams to ensure workers adhere to processes, procedures, culture of working, etc…and that he is writing a plan and report.

If he wrote this report in a wiki, others with permissions, especially cross-unit leads could eavesdrop on this progress, and add insight that he doesn’t know about, because he cannot possibly know the politics, norms, and domestics of each business unit.

NOTE: Please don’t say a survey…the idea of KM 2.0 is no extra effort to share and mingle, it happens as part of doing work.

This report, I assume, would take months to write, why not blog about; progress, feedback, ideas, musings, snippets to showcase, as you go along. By doing this others are in the loop, and they may leave comments to give you ideas and answers. Especially for this type of report, other leads could leave comments on blog posts, or even a dedicated wikipage, on the blockages they have with their team using current procedures, etc..

I bet when the report is finished it would be more relevant, and not just another report about you must work like this for the sake of quality
Instead, the writing of the report has incorporated the existing attitudes, which has helped shape it, now the procedures and processes may work as we are accomodating for the reality of the culture of work.

In fact it would be more true to “quality” if the report was more realistic in its research, being flexible to how people naturally work rather than rigid…in fact it may be realised that the proceses and procedures themselves are the problem as they are not in tune with human behaviour.

Why do I think this blurs the line?

Using a blog to share your insights and musings along the way is “Above-the-flow”, but using the same blog for progress updates and communications could be “In-the-flow” (as you would use email for this anyway).
Whichever method it increases a chance for others to contribute their know how as comments. In a nutshell working in a visible way may encourage more “Above-the-flow” participation.

Using a wiki to draft your document is “In-the-flow” (I don’t really like the descriptor “knowledge sharing” here as it’s just doing work). The benefit of doing this in a visible way, is others can see your progress without you having to update them, and they can add value using the comments. So what is happening, depending on the nature of their comment, is they may be choosing to share some “Above-the-flow” (personal know-how) to your wiki.

The idea is that an “In-the-flow” approach using participative tools, will encourage “Above-the-flow” sharing. You would hope in the long run that people would not only share know-how in a reactionary way, like using comments, but would also initiate original content using blog posts, wiki pages, etc…

We know comments is where the conversation is, and this is where all the know-how exchanges happen, as people share what they know and they discuss to clarify, etc… The object is dynamic, perpetual, and as smart as a crowd.
The existence of comments itself is our first step in an “Above-the-flow” culture, as they are less effort than initiating original content, and they almost always share opinion…it’s an effective way to get people in the swing of working open (transparent) and socially.

Anyway…

The premise is to capture thoughts and interactions as they happen, email is good but closed, and physical conversations have all the know-how, but can only be documented after the fact (which loses all its richness). So the idea is to complement the offline world with online social tools that mimic how we work offline, but have the benefit of capturing (documenting) as we interact, and including others in the converation, that don’t have the privilege of being in the same location of a meeting or 1-to1 conversation.

Without blogs and wikis, this would be the approach:
- Meetings, emails, IM, phone, physical conversations.

The problem here is there is no sense of place, if I am a new comer, how do I catch up on the progress of this initiative and the progress of the report.

Meetings are essential, but you can only say so much in a alotted timeframe, social tools allow to extend the meeting discussions in an asynchronous way, and to lots more eyeballs, that is much more open and conversational than email…others not in the meeting may have something valuable to say.

The phone and physical conversations are also essential, but blogs and wikis allow others to interact without having to engage in 1-on-1 conversation.
Sometimes I don’t want to engage in a phone call, I may have an idea and quickly add it as a comment to someone’s blog. I could email my idea, but then this clogs up their inbox, and who do I put in the to: field so lots of people see it. Actually maybe I feel a bit “pushy” and shy disturbing everyone with an email about a flash of insight, so I won’t send it after all. Whereas a blog comment doesn’t feel “pushy” at all, and you have more confidence sharing your ideas as you haven’t pushed them into people faces, instead they choose to “pull” your comment to themselves (you’re not quite sure who is going to see it, but it’s there for all to see).

I could give a quick IM, which isn’t as committed as a phone call, but then that comment is not attached to the object and the receiver has to write it down somewhere so they don’t forget.

To extend this post it’s essential to organically permeate the right culture by creating conditions for knowledge sharing, such as socially connected and unstructured tools with low barriers to entry, trust circles, roles models, senior support, job evaluation, and facilitation.

Related
The context of blogs
KM 2.0 : doing your job or giving back to the organisation
Knowledge and its facilitators

August 6, 2008

YackTack will track comments about your content that happens at other places

Filed under: blogs, conversation

Just tested out YackTrack and find it a very useful tool. For a publisher (blogger) it seems to do for comments, what Technorati does for blog posts.

That is, Technorati can track blog posts that link to your blog posts, this way you know who is talking about you.

Comments to blog posts are also becoming of a distributed nature.

eg. If someone bookmarks your blog post at StumbleUpon or Digg and there is a few comments how would you know.

YackTack will track comments about your content that happens at other places.

I’ve even embedded the YackTrack link in the footer of my blog post template. You can also get this as a bookmarklet for blogs that don’t have this footer link, and it’s more convenient than entering a URL on their homepage.

They also have another feature called “Chatter” which has the beginnings of a comment search engine.

Question

On your results page it displays an RSS feed. This is like a comments feed for comments that don’t live at your blog.

What I would like to do is subscribe to just one RSS feed for my blog so I can be notified of comments that happen elsewhere about any post on my blog.

This is similar to Technorati…I don’t have to subscribe to an RSS feed for each of my posts, I only subscribe to one feed that takes care of all my posts.

Next I’m looking for a similar thing for the bookmarkosphere.
I want an RSS feed that will tell me when each of my posts have been bookmarked on any of the various social bookmark sites, and a chicklet counter. Perhaps a feature suggestion for aideRSS.

July 26, 2008

Conversations, Connections and Context

When I was thinking up the title for this post I was loving all the fabulous C words:
Conversations, Connections, Context, Communication, Collaboration, Community, Complexity, Collective

This post like others is focused on the first three, and mostly on conversations and context…but without connections and participation (visibility), none of these can eventuate, along with ultimately collaboration or even forming communities. I guess this post is also about communication, not directly, but more on the assumption that a message is understood once it’s transmitted.

Abstraction

Having a high abstraction with the author of a blog post or codified document for that matter enables me to have more of a chance to derive the intended understanding or signal from the author.

NOTE: High abstraction refers to knowing that person well enough, having a shared background, having things in common, in-jokes, etc…

The stronger the relationship and commonalities you have with a bunch of people, the more you understand each others writings, the more chance their knowledge comes to be your knowledge.

So right off the bat, it’s essential we have this kind of ecosystem where people are connecting to each other and sharing nuggets of what they know as it happens, exactly like we do in the offline world.

Codification and Context

The whole idea here is to capture what we know so others can use it, captialising on the talent that sits in an organisation.

But since we can’t know everyone, it is no surprise that the intention of codification is an attempt to have a universally applicable object (re-use recipe) that will work in every context of the person that encounters it, or rather, that the person can use the document and mould it to their context.

Codification is OK for procedures, etc..and even for things like an IT support solutions database.
But the problem here even is that a codified solution is usually formal (stripped of context)
eg.when this happens this is the fix

This doesn’t contain the situational context of the occurrence.

What happens when that fix doesn’t solve the exact same error you are dealing with. Reasons for this may be your clients PC may be using a different version of Excel or they may be remotely logged in, etc…
Because a codified document is sanitised and generic it removes all the idiosyncrasies of the context of the situation, so this doesn’t really help your situation even though it’s the exact same error.

So rather than a sanitised solutions database, why not have support people blogging their experience, this way they are sharing the solution in the context of their experience and surroundings. And they can also tag (index) this solution with keywords. Now there can be various versions of this same solution, each caters for a context.

This solution has not been stripped of any context, it’s informal and casual, it has the personality of the author, and you don’t have to spend extra time remembering to add your solution to the database as the blog is the database.

Two extra things happen:
- people can subscribe to each other, and be aware of solutions as they happen, even though they do not have a need for the solution at this time, they are learning and aware of what others are experiencing.
- if you can’t find a solution to your problem you may know another support person to contact as some other solutions they have blogged may be similar.

We are aware of what’s happening through a filter of people we trust, we are able to tune into what matters to us, and our network brings quality information to our attention so we don’t always have to go looking for it (we just can’t read everything).

So…

Rather than having to write a formal and standardised solution after the fact, we can instead have a database (blog) of raw data (indexed by tags). Blog content is more colourful and establishes the situation (background and any other peripheral stuff that happened). This more humanistic (personal, informal) story-like and emotional type of language, is easier for the brain to absorb and remember (it contains triggers for recall).

A wiki could also be used. The original solution page could be edited to add other contexts that people experience with the same error. Or maybe you could edit the wiki by entering URL’s of blog posts that talk about this same error in other contexts.

To find a solution
- you may already know which support blogger to ask
- search the blogs and browse the tags

But is this enough, is it too messy, and not quick and handy?

Gardener/Facilitator

We need a gardener to make some rules on some tags to use, and naming conventions, I’m not talking about a taxonomy, I’m refering to ambiguous tags, etc…
eg. I see you tagged this post “check in/out” can use please tag it “edit” instead
eg. I see you tagged this post “MSoffice”, but “Excel” should also be another tag
eg. Can you also include the tag “Perth”, in this post because the error only happens on PC’s in the Perth office

The gardener could also create some lists from this raw content, and compile conversations.
The gardener could make some review pages of this content to tie in different blog posts that deal with specific issues part are part of a bigger issue.
eg. These 10 blogs posts refer to various issues, and these 2 blog posts refer to a bigger issue that is the cause of all these other issues experienced in the 10 blog posts.
Then they can go back to each blog post or wiki page and cross reference this review blog post (or perhaps it’s a review wiki page).
The gardener will also have to go back to the database to re-edit posts that are no longer current or relevant solutions. Remember this is a solutions database so we can’t have people acting on the wrong information. The gardener can re-edit these posts pointing to a newer post.

Maybe creating the conditions for this ecosystem, other social activities, and specifically the facilitating and gardening is what managing knowledge is all about…if this phrase makes sense.

Mathemagenic has a great post on not so much gardening, but on her thoughts on writing her dissertation when it’s all there in her blog.
If we one day read her dissertation, and then read her blog posts, which do you think we would be able to get more know-how from. I think the blog posts, as they are more initimate like conversations, but the corollary is that perhaps her dissertation would give us an overiew to be able to tie all these blog posts and see the big picture.

More from the post:

“While weblog provides a space to grow ideas, it’s also a mess of fragments. They are connected through links and tags, but in many cases the higher level reasons of why certain bits appear and how are the relevant to a bigger whole remain unarticulated. Mainly because at the moment of writing it’s not clear how the fragments connect.”

“It also takes extra work (e.g. a systematic data collection and analysis) to connect fragments in a story that provides stronger evidence than a collection of anecdotes.”

“Working on a dissertation provides a structure to address those issues: the need to connect fragments, push and discipline to collect evidence, time to work on converting all that into a bigger whole and a space to do it.”

Connections and Conversations

OK, back to our problem…earlier I said:

“The whole idea here is to capture what we know so others can use it, captialising on the talent that sits in an organisation.’

“But since we can’t know everyone, it is no surprise that the intention of codification is an attempt to have a universally applicable object (re-use recipe) that will work in every context of the person that encounters it, or rather, that the person can use the document and mould it to their context.”

So we understand this situation, but from my explanation above codification isn’t effective and practical.

By non-practical, I mean people don’t see the returns or worthwhileness in the effort of remembering and sharing a formal document into the database…it feels like extra work.

Using newtorked tools, this is no longer the case, as while we do our work (blogging and conversations) the sharing has happened by default. The gardner makes sure the web doesn’t get tangled.

By non-effective, I mean people have to cognitively write the document in a formal way, which will strip it of situational detail, and index it into a pre-set topic structure.
And people find these formal and static documents unusable most of the time, plus people like going to people, rather than searching databases.

Using networked tools, this is no longer the case, you don’t mind searching a blog database, because it’s like searching past and present discussions (this is similar to the offline way of doing work), tapping into a pool of raw conversations like radio waves out in space.
These are more informal fragments of contextual information, and when we are networked with people, and know the people behind the information, there is more chance we will actually understand the intended meaning in the information.

The value is in conversations, rather than secondhand degenerated information.

A downplay is that an addiction to a codified database creates a situation where we think we have all the answers to apply to any situation, but we don’t so we then find it hard to adapt. When in the first place rather than codifying we should just keep learning, publishing and subscribing to fragments as they happen, giving us more on the spot sensemaking abilities.

So it’s about bouncing, managing and arranging the fragments, rather than codifying.

More on context

Dave Snowden says in relation to past KM tools:

“They assume a common or constant context. So knowledge captured in one specific context can be generalised to apply in all contexts.”

Then he says:

“…blogs and the links between them are much better at passing on context than traditional KM tools. Mainly I think because they are fragmented, real time and emergent in their connectivity.”

So as we have covered, codification tries to be as objective and perhaps context free as possible, or put another way a “constant context” (oddly assuming every situation is the same).

So no wonder it doesn’t pass on context.

This is not the intention of a blog post, they are musings and publishings with no other motive than stream of consciousness (sorry I’m getting carried away), I mean more informal and as it happens.
They are rich, and more descriptive (like a story, you feel like you were there), and also more localised where we can assimilate with the context of the situation.

This means a blog post will have more of a defined context, it will be more personable.

Further to this, all this peripheral information may give clues or triggers to apply to other unrelated solutions, whereas a codified solution is so narrow that you won’t get anything else out of it.

This is great if the context of the blog post suits the need of your situation, but what if it doesn’t?

Is the arguement that blogs are not trying to be what they can’t be vs codified documents that have an intention they cannot meet (they are not achieving what they are intending to achieve)?

So, nothing can have a constant context, blog post or not.

But what we can do is to be able to have more of a chance to at least understand the context of something (a blog post) we are reading as it’s not trying to be generic, it’s only useful if it has context…maybe not to my specific situation or need, but at least it’s rich and deep (like an impact a story has), and I can learn from their experience. Because blog fragments and stories are not trying to achieve an outcome, except just tell a story or expression, they are rich with lots of meaning, whereas a deliverable is trying to push a meaning to you. You can get so many different colours and feelings from a story, everyone can get different meanings from the same story, whereas in a deliverable everyone is just meant to see the one meaning.

This is why I think we are moving from knowledge management, and more into a learning organisation. There is no aim (to manage knowledge besides gardening), it just spreads by being (in a learning enviroment).

What I mean is I’m not avert to mixing and matching, and making lists, of self-organising and emergent data, in order to correlate and see it in other ways…or even to dampen the self-organised data as it’s heading in the wrong direction. Read Dave Snowden’s blog on complexity (boundaries, attractors, amplifying and dampening).

So all along KM has been about:
- content, when it should have been about context
- storing, rather than flowing
- static, rather than dynamic
- imposed, rather than emergent (self-organised within boundaries and manipulation)
- lacked all together connecting people (other than expert locators), but I mean relationships and networking

Summary

In the days before databases, like now, we used the phone and offline conversations to do our work, then these conversations were conducted in email. In these interactions is where people communicate and exchange their know-how, and it was thought how do we leverage this so people outside of the conversation can benefit from the talent pool…how do we capture this.

Not all were privy to these exchanges, so the idea was to conscript people to codify their talent, this is very confronting, not practical, and not effective when trying to remember what you know…hmmm, let’s see what I know…ummm…hmmm…this feels stupid…if you’re gonna be that way why don’t you hire me as a consultant instead so I can get a reward. It really has a big brother, police state feel to it, the extreme is to connect your brain to a computer so it can drain your know-how.
And when you go to seek answers it’s hard to find something that relates to your context, you perhaps find it hard to understand because it lacks back story, and you may not identify with the calibre of writing.

The interactions between people is where the know-how and the spreading of it lies, the new era is mimicing this experience in an online global village, so the richness is documented as it happens. The beauty of this is using platforms rather than closed channels opens up the conversation to a greater number of minds, to evolve know-how and connect with others you normally wouldn’t know, exchanging ideas. It’s self-rewarding in an ecosystem where you participate, people riff on your ideas, and you come to a better place using the wisdom of crowds.
And it’s people friendly as we socialise (social connectedness), get our work done, and learn (become smarter).

I think we have a sharing nature if the right conditions are there for it to happen, once we find like people we understand and trust, interdependencies build where sharing becomes a natural thing…from this comes communities, collaboration, emergence, and autonomomy…I call it the k-flow model.

Now we can achieve spreading know-how, at no extra effort, and it has changed the concept of work for the better as it’s more socially engaging. It’s a learning organisation concept where the individual is learning in a reciprocated environment, and the organisation as a whole learns and adapts…being able to respond to changes conditions.

What’s special about all this is it’s happening from the inside out, we want to work this way, even if some of us don’t know it yet.

This has come at the right time in the face of fast paced industries, and distributed teams, and it’s going to change the dynamics of the scientific management model to a more accomodating networked model (tribal).

Let’s finish off with a video clip by David Gurteen on conversations (referencing David Weinberger and Theodore Zeldin).

Here’s a great quote on learning via stimulation, rather than a bank of information:

“What is lacking now, I believe, is something which we cannot find anywhere, somewhere where you can reach, and get that stimulation - not information, but stimulation - where you can meet just that person, or find just that situation, which will give you the idea of invention, of carrying out some project which interests you, and show how it can become a project which is of interest to other people. “

Some great quotes from the video:

“conversation being a creative process”

“conversation doesn’t just shuffle the cards, it creates new cards”

“conversation where we emerge a slightly different person”

July 16, 2008

The tacitness of wikis

Filed under: wiki, km, conversation

Stewart Mader from Grow Your Wiki is guest posting on Wikinomics and his lastest post is on the effectiveness of wikis enabling tacit sharing.

Documents that are open and dynamic allow people to evolve the documents by direct editing or leaving comments…ie. people are sharing their experience and what they know can add to the richness of the document.

Right away I thought of the How-To Guides I’m writing for our Communities of Practice (CoP) at work.

If my guides are on a wiki rather than PDF, people who use the guides can leave comments, or people with permissions can edit the page itself or a new page to add what they know.

This way they can help me evolve the document, even though it’s finished. Well, that’s the idea, it’s never finished…I may miss a feature, and I can’t experience every context, so there’s stuff that happens when people use Communities that I may not know up front. eg. a new way to use blogs, a workaround (exception to procedure) page for Document Control as each client has different needs.

They may leave a comment about a feature of our CoPs where they have a workaround, or a use case.
eg. someone might say everyone in our team has a status blog, so when we go to a meeting we already know what everyone has been up to, our meetings are more about action.
Another person visiting the guide may see this and use this idea.
A simple comment box on a wiki has enabled the sharing and receiving of know-how by two people that don’t even know each other, plus this is perpetual as another person may come along and get value or an idea from reading the same comment. In fact another person may leave a comment back and say that they found it more manageable having one group blog for status. The original person my see this and comment back saying, that is a great idea, I didn’t know that was possible. Oops, that’s because I may have not put that fact in the guide, lucky that comments allow for others to help where the guide fails.
And as Stewart mentions I can go and refine the guide and leave a comment saying thanks.

In the end we have this explicit type deliverable that has to be formal and succinct as it has to cater to many audiences, and can’t be too explanatory (long), and try to cover every context possible, as people won’t bother reading it. But on top of this we have a layer of collective know-how and feedback via the comments which inturn we feed back into the document (via edit) some tacit know-how.

The point is having perpetually live documents (editing and comments) harnesses the collective wisdom, where people can share their know-how, and benefit the user experience as a whole. It’s a win win situation.

July 14, 2008

Moopz the self organising memetracker, and other Friendfeed friends

Moopz comes to the rescue for a concern I too have had about Friendfeed, and that is, fragmented conversations within Friendfeed itself.
The issue is that there may be conversations around multiples of the same item:

- just say my blog feed posts my latest item to Friendfeed (it’s a post about something I have on Slideshare)
- my latest Slideshare activity will post an item to Friendfeed as well
- and someone bookmarks that blog post or slidedeck URL on del.icio.us which then shows up on Friendfeed
- someone tweets about it, and that shows up on Friendfeed
- someone may even post directly into Friendfeed about the slidedeck

As you can see above there are 5 opportunities to initiate the same conversation about the same thing within Friendfeed, and the most thriving conversation may be around someone’s bookmarked item of your post, rather than around the feed item of your own post.

As Read Write Web point out, at the moment your re-syndicated blog post may not have any discussion in Friendfeed, but an A-lister who bookmarks your blog post will have lots of discussion around that item in Friendfeed.
This is a new dynamic as now people are becoming a hot spot, a community onto themselves, for not only their own content, but content of others.

Moopz plans to prevent this fragmentation from happening.

For starters it only displays content that has links, so you won’t see tweets saying “Good morning Twitter!”

If a new link that appears is already linked to in another Friendfeed item, then they will be merged (clustered together) preventing fragmented conversation from even happening.

Another good thing about this is that we don’t have to see duplicate items.

And each item is auto-tagged meaning you can browse conversations on a topic

I guess this is a memetracker of sorts based on clusterings, and what gets on the frontpage is decided as a result of people using the system. This makes it a more self organising version of Techmeme and Megite…and a more limited version as it’s only based on content that comes from the aggregate of user profiles.

Megite allows you to enter your OPML, and displays most popular and recommended posts from people you care about (rather than all items ranked), but it’s not a conversation platform. It also displays memes by topic.

At the moment Moopz only has a public timeline, hopefully soon it can be personalised to have a friends timeline.

Like Megite and Techmeme, Moopz will display popular memes based on links, but it doesn’t scour the web for these links and cluster them, instead it scours content people have re-syndicate into it’s own system…the former Memetrackers also use other methods like concept analysis (as two items may be about the same exact thing yet they both don’t point to a common link).
Moopz also has another aspect to popular memes, and that’s based on the amount of conversation that happens within Moopz (Friendfeed) itself.

More

Also checkout how Read Write Web and Louis Gray are incorporating Friendfeed comments back to their blog (the original source)…Read Write Web also allow posting to Friendfeed from within their blog.

Louis Gray has some great Friendfeed tips every Friday, the first one on the hide funtion is a great way to reduce the noise, and same with advanced search.

NoiseRiver (via LG)

Another way to filter the flow by a feature called “My Interests”, enabling you to use a drop down menu to filter in or out items containing a certain keyword, the filter choices are:
I love it so much!, I love it, I like it, This is nice, It’s OK, I don’t care, It stinks, This is bad, I don’t like it, I hate it, I hate it so much
There’s also a feature called “My Neighbourhood” to filter items from people on a similar filtering menu.
I also noticed:
- you can re-share an item (this posts it as a FF post)
- there is a reply icon next to each item and comment so your comment is pre-pended with that person name eg. @louis
- each item has auto-keywords (not sure why you can add/delete them, you can also filter rate these keywords as explained above)
- “hide all entries with this URL” is a manual way of doing what Moopz already does.

FeedMachine (via LG)

This brings an element of an RSS reader because you can mark read/unread

Friends view - contact list where you can choose a contact and click on a source icon and a box displays latest content from that source…it lacks latest content from all a person’s sources

Good Friends View - When you click on a profile it allows you to tick that person as a good friend, this will add them to your Good Friends section

Stream View - latest items from all friends
When you click on the info icon it loads the original item on the right and the FF comments on the left, where you can post a comment
- sort by: newsest, oldest, unread, user, service, item text, comments, most liked, least liked
- hide duplicates

Just like NoiseRiver and Moopz you filter out entries by keyword, as well as user, service, hide read items, and hide “@” items

Mio News (via LG)

This turns Friendfeed into an RSS Reader, kind of reminds me of Spokeo.

On your subscription pane you have an icon to see your FF stream (mark as read).
You also have an icon for each friend, clicking this will stream the latest from a friend (mark as read).
You can group friends into folders, click on a folder will show you the latest from just those friends in that folder (mark as read).

But, you can’t filter your whole stream, a folder stream, or one friend by service.

This has an MS Outlook feel, as when you click on an item you see the full-text on the 3rd pane, from here you can:
- mark as read, share on FF (also share to your blog, twitter, and email), comment, like, hate, goto native item

There also a bookmarklet and blog and Twitter integration.

Lastly there is a “Topics” feature where you list keywords (also organise in folders)
- clicking on a keyword will display all items from your friends about that keyword (not sure if it’s “about” or just the appearance of the keyword)

At the moment you can’t view rooms, or share an item to a room.

This could be a replacement for Google Reader, it would be good if you could manually adds feeds from non-FF people so I don’t need two RSS Readers.

Related:
FriendFeed Rooms : Interactive topic streams
Friendfeed : social filter conversations

July 1, 2008

Knowledge Management…NOT!

This post continues on from my post, Knowledge as Interpreter - ASPE.

In that post I riffed off some bloggers on the concept of Data-Information-Knowledge-Wisdom (D-I-K-W) not being of a hierarchial nature, and rather a loop, where knowledge is required to turn data into information, and the sensemaking process turning information into knowledge…and if that knowledge created were to be exchanged (written down/conversation), it would be back to data or information, depending on who was looking at it.

I also prefered the verbs in the diagram, Analysing - Sensemaking - Pathfinding - Executing (ASPE).

NOTE: I just had a flash of physics then with my phrase, “…depending on who was looking at it”. In physics sometimes things exist only if you look at them, the same goes with information, where information only exists if the receiver has the current knowledge to see data as information.
In physics, if you don’t look at the thing it doesn’t exist…if you don’t have the knowledge to see the data as information, then the information doesn’t exist to you. Someone help me here…

Knowledge Management is an oxymoron?

An oxymoron is a phrase combining opposing or contradictory terms

I’m not going to define KM, but here are 43 knowledge management definitions - and counting… I like the idea that it’s not about a means to an end.

For me it’s a way to augment the way you work, which is in a more open networked environment, where your information is visible, creating more chance for connections (conversations), awareness, relationship and trust building, in turn creating more opportunity to develop shared context with others (which increases the chances of successful knowledge transfers, ie. the meaning in the message is transferred).
This way of working (leveraging the social capital), creates interdependencies between people which solidifies the success to keep working in this style.

Oops, did I just try to define it…perhaps describe it…

This is really information openess and connection, perhaps this practice is “knowledge sharing.”
I don’t say information sharing, as the intention is for your knowledge to be received as knowledge to someone else, rather than just information. So knowledge sharing is the intention, but sometimes information sharing may only occur, or worse.

Is someone who is in charge of this way of working, a Knowledge Manager or more a steward or facilitator who instills a culture of Knowledge sharing practices or style of working, where the aim is to create shared context?

If knowledge is not an object, and is more personal know-how and is used to make sense of signals we receive, then how is it possible to capture knowledge, or for that matter transfer knowledge?

Further to this, then there is no such thing as managing knowledge.

We can only manage information, whether you get intended or unintended meaning out of this information is up to the receiver.

If you get someone to store and tag a report into the repository, this is the role of information management.
If you get someone to write down their know-how and store and tag it into the repository, this is still information management.

Anecdote realise this and rather use the term “Better Information Managment”, and “Improved collaboration and learning”.

We have to admit we are stuck with the term “Knowledge Management”, and it will continue to be used even though it’s not exactly what happens…what’s in a name.

Information has no meaning

An Anecdote paper, Our take on how to talk about knowledge management, tells us:

“Knowledge is the stuff in people’s heads which enables them to do things.”, and:

“Information is certainly valuable, but it is inert; it does not cause things to happen.
As described by Polanyi and Prosch,[1] information (suchas a map), no matter how elaborate it is, cannot read itself; it requires the judgement of a skilled reader who will relate the map to the world through both cognitive and sensory means. Debra Amidon, in 1991,[2] asserted that information, in and of itself, is not useful until it is embodied in a person’s awareness and related to business imperatives.”

Oscar Berg has being talking about the nature of information, and how the value derived depends on who uses it.

This is the very message of the late Frank Miller’s seminal paper, I = 0 (Information has no intrinsic meaning), which I re-read lately.

Miller says:

“…we’ve been led to believe that information contains meaning - rather than just standing for, provoking or evoking meaning in others.”

“…knowledge is the uniquely human capability of making meaning from information…”

“…information is intrinsically meaningless on its own and remains so unless - and until - it is interpreted by human beings, within some context.”

“…information become knowledge? The answer: at the moment of its human interpretation (and not an instant before!)”

One of the best quotes is:

“But if we then take the step of ascribing intrinsic meaning to the information itself, we cross the boundary of rationality and enter a bizarre world where we assume that impersonal stimuli have minds of their own and can have their own meaning!”

He gets more esoteric by saying that if we didn’t have information, ie. no sensory input, then there is no knowledge to be created…without information (therefore no sensory input) how to we know we even exist. Let’s not get into this here, as we could discuss non-materials planes.

Re-reading this paper was a very different experience from when I first read it a couple of years ago. Since then I have read and experienced more of life, especially in KM and related fields, and with all this knowledge I have amassed I got 10 times more meaning (and ideas) out of this paper.
There must be a term for this, my different experience in reading this paper demonstrated what the content of the paper is about.

The nonsense of ‘knowledge management’ is a paper, by T D Wilson, that is along this same line of thought:

“…’knowledge’ (what I know) and ‘information’ (what I am able to convey about what I know)”

You can’t capture knowledge, and there is no such thing as explicit knowledge

Miller says:

“…knowledge was only ever tacit. Once we attempt to make knowledge (i.e., what we ‘know’) explicit, it reverts immediately to an ‘information’ state again and requires human intervention anew for sense to be made of it.”

“Knowledge is, after all, what we know. And what we know cannot be commodified.”

“Knowledge (ie ‘what we know’) is only ever ‘tacit’ and can never be ‘explicit’. It must never be thought of as a commodity to be captured, processed, stored, transmitted, managed etc.”

Wilson says:

“‘Explicit knowledge’, of course, is simply a synonym for ‘information’.”

“…’tacit knowledge’ involves the process of comprehension, a process which is, itself, little understood. Consequently, tacit knowledge is an inexpressible process that enables an assessment of phenomena in the course of becoming knowledgeable about the world. In what sense, then, can it be captured? The answer, of course, is that it cannot be ‘captured’ - it can only be demonstrated through our expressible knowledge and through our acts.”

This nullifies the concept that you can capture knowledge, as it’s not possible to capture meaning, the meaning is derived by the person encountering it, all the capturing we do is simply information management.

This makes Nonaka’s SECI model (turning tacit into explicit then back again) a bad model of KM, which is a pity because it was “the” model that has defined KM for a decade.

Dave Snowden has more on KM sins, which includes, knowledge as more a flow, rather than an explicit asset:

“…put all their effort into knowledge as a thing; making tacit knowledge explicit…”, instead:

“…focus on creating connectivity between people to allow knowledge to flow, rather than worrying about the knowledge itself. Get the channels right and that is most of the battle. Generally if people have a working relationship, ideally a trusted one then in the context of need they will help each other without the need for direction, structure or technology.”

This leads to Dave Snowden’s three heuristics. Wilson seems to be in the same school of thought:

“The fact is that we often do not know what we know: that we know something may only emerge when we need to employ the knowledge to accomplish something. Much of what we have learnt is apparently forgotten, but can emerge unexpectedly when needed, or even when not needed. In other words we seem to have very little control over ‘what we know’.”

Shared Context creates more chance of the intended message being understood

As I mentioned earlier I think Shared Context is at the heart of KM, when you are in a conversation you hope what you are saying is understood, ie. the receiver has understood your intended meaning.

Frank Miller explains that the reality of information not possessing an intact meaning, can be felt in mis-communications or mis-interpretations.

Why do some people understand one thing, and others another, or nothing at all?

It’s because we use our current knowledge to derive the meaning, the information itself can’t do it for us.

He says:

“…although information certainly stands for meaning, it is never meaning itself. Meaning is a mental thing and is only ever tacit, that is to say, ‘in us’. Identical information almost invariably provokes (or evokes) different meanings in each of us.”

“…it is not what the message does to the audience but what the audience does with the message that really matters.”

This reminds me of a paper by Nancy Dixon, on the onus role of the knowledge receiver to tease out the desired exchange…I’ll get round to posting about this later on (it’s such as great paper).

Wilson has a similar thing to say:

“‘Knowledge’ is defined as what we know: knowledge involves the mental processes of comprehension, understanding and learning that go on in the mind and only in the mind, however much they involve interaction with the world outside the mind, and interaction with others. Whenever we wish to express what we know, we can only do so by uttering messages of one kind or another - oral, written, graphic, gestural or even through ‘body language’. Such messages do not carry ‘knowledge’, they constitute ‘information’, which a knowing mind may assimilate, understand, comprehend and incorporate into its own knowledge structures.”

Web 2.0 helps build abstraction with people in far places

Apart from information having no intrinsic meaning, Frank Miller goes on to talk about a very important point, in that the web has enabled people to get a message to a global audience.

These days you don’t really know much about the people you are working with or communicating.
This becomes a problem, because there already is the potential problem with people you know well mis-interpreting your message (information), when you work with people you don’t really know this is going to increase the chances.

Miller says:

“Our knowledge - that is to say what we knew from our direct experiences - was closely akin to the knowledge of others with whom we necessarily lived our lives in close proximity.”

“The “information age” changed all that.”

“We can send information and provoke a response in almost anyone we wish anywhere on the planet, but we can never be sure - unless we know these people personally - how they are likely to interpret (ie what meaning they are likely to make of) the information they receive from us.”

“Successful communications depends on knowing others well enough or caring about others deeply enough (the tacit dimension) to imagine how they are likely to interpret the (explicit) messages we exchange with them.”

Dave Snowden often refers to a level of high abstraction, the level of; intellect, shared experiences, style, character, that is known between a group of people, the more chance they will derive the intended meaning from information exchanges.

Along with this, as mentioned again and again, is a high level of Shared context. This is how much we both know about the context surrounding this information eg. are we familiar with the source, the background it’s based on, the topic, etc…this frame of reference helps in deriving the intended knowledge from the information.

You are having a conversation with a piping engineer:

1. in another company
2. in another office in your company
3. in your office
4. in your office and in your team
5. in your office, in your team, and your close colleague

Obviously number 5 is the person you will have a greater level of trust, inter-dependencies, abstraction and shared context.

These are the the necessary aspects of a relationship for not only successful information transfer, but collaborating, creating, evolving new information and knowledge.

The 5 point list above is based on the offline world, if we include the online world of networks, blogs, communities, etc…then geography really doesn’t make a difference.
In an offline world we can still get to know a colleague in another office using the phone, IM, email, etc…but in a community and network we get to know lots more.

To reprise Frank Miller’s paper I’d say that web 2.0 has evolved to enable us to retain and create close relationships like we have in the physical world…we are still able to know people (geographically distant) well enough that the information signals are no more misinterpreted than they are with people in the same office.

In fact the web now allows us to know a lot about people that we don’t even know, if anything we can connect to more like minds, form new relationships, get to really know other people well.

Social tools like blogs mimic the offline world:

- we can informally and casually talk about stuff
- others can subscribe (these people really get to know your character)
- these people can leave comments and talk about you in their own blog posts
- you subscribe to them
- this all happens on a daily basis

There is no doubt that face to face, audio/visual helps evoke more understanding, but casual and informal blog posts also have this effect, and according to the listed points above, blogs enable people to discover each other and connect into a close relationship where you develop trust, high abstraction and shared context.

So if anything, the Read/Write Web has taken us to the “Knowledge Age”, where we can connect and get to know people, without even having to have a relationship.
This certainly helps in the enterprise as we have to deal with all sorts of people from all sorts of departments. If we can visit their profile, see their network, see the contributions (blog posts, etc…), we can get to know their character, where they fit, etc…we know more about them, which helps a more successful interaction with them.

Miller says:

“Only human beings have the capacity to construct meaning from information and to sense ‘meaning’ evolving in themselves and in others. Only human beings can compare interpretations with a view to achieving a shared purpose.”

“Information, no matter how elegantly processed and presented, is incapable - on its own - of achieving anything!”

We need to increase the chances that when we confront information (read/conversations) we are able to get as much meaning as possible. Both what the sender is intending to transfer, and the stuff the receiver gets out of it, including the stuff that the sender didn’t think of.
This is what participation and collaboration (wisdom of crowds) is all about.

So rather than Knowledge Management (mandating/capturing/storing) we need to be focusing on connecting people, so we can increase the chances of collaboration and sharing what they know, and within this create a culture where this sharing and collaboration is successful in transfering and receiving intended signals, ie. by creating opportunities to create informal communities, networking, develop high trust, inter-dependencies, shared context and high abstraction…most of this is from Dave Snowden.

What is the role of a Knowledge Manager?

For starters, we have discussed that “Knowledge Manager” is an inaccurate job description, and what they currently do is more inline with information management, and people management.

This is a quick list:

NOTE: collaboration tools and the like means not just setting up, but facilitating and coaching…knowing human behaviour

- smooth out bottlenecks in processes
- online storage and search (re-use)
- openness and visibility
- collaboration tools (do work)
- communities (share/learn)
- networks (connect/discover)
- communication and awareness (esp. cooperation across business units)
- autonomy (being able to hook up with the right people and tasks)
- techniques (AAR, Peer Review, Open Space, World Cafe, Narrative, AI, SNA, etc…)

As a result you get more self organisation, learning, innovation, transparency, autonomy and emergence.

There is nothing about managing knowledge in this list, it’s all about connecting people, creating conditions for conversation, enabling more sharing and collaboration to occur, people leveraging each others talent.

The role of a person responsible for all this seems more like a facilitator, coach, and Corporate Anthropologist.

This type of person needs to have a handle on more humanistic fields like: Cognitive science, Learning, Psychology, and social behaviour.

Corporate anthropologist (enabler/facilitator)

- observe the processes and people
- create conditions for smoother processes
- create conditions to be able to find people and content
- create conditions for people to tune into each other
- create conditions for people to have conversations
- create conditions for serendipity
- create conditions for people to successfully understand other people and their content
ie. information signal conveyed is easily understood, and the receiver interprets the intended meaning from the sender.

Perhaps the name “Knowledge Manager” seems more appropriate when seen as a person who manages and is responsible for instilling and sustaining effective knowledge sharing activies. This way they are not managing knowledge per se, instead managing the activities. This could also be seen as the role of the Chief Learning Officer, or a practice of the Organisational Performance unit.

Karl Sveiby’s thoughts are more on the activity:

“Knowledge Focus” or “Knowledge Creation” (Nonaka) are better terms, because they describe a mindset, which sees knowledge as activity not an object. A is a human vision, not a technological one.”

Mike Gotta’s thoughts on the KM activity:

“Not that KM is dead – but KM is additive to other endeavors and not and end in and of itself. If we anchor the discussion around improving a process or ensuring that we have the right competencies and skills within the workforce (e.g., as part of succession planning) or improving group interaction around R&D activities, then we are speaking the language of business and that will lead to the business case and metrics.”

Dennis Pearce (AOK) mentions leadership is less required when things learn from networks (p44. anecdote):

“I have been looking at organisational learning from a process, connectionist perspective. Other “things that learn” (brains and neural networks) don’t require leadership — they just learn as a result of their networked structure and processes. So if I can embed KM activities into the existing processes of an organisational network, people aren’t “doing KM,” they’re just doing their jobs, but the organisation is learning.”

Joe Firestone says that using or processing knowledge does not mean you are doing “knowledge management”:

“Knowledge use occurs whenever any agent makes a decision. It is part
of every business process.
§ Knowledge processing is knowledge production and knowledge
integration [1] [2], two distinct knowledge processes constituting the
Knowledge Life Cycle (KLC) [1][2].
§ Knowledge management is knowledge process management, that is,
the management of knowledge production, knowledge integration, he
KLC, and their immediate outcomes [3].”

Joes excellent paper includes theory on the 3 worlds of knowledge types, and lots more.

Wilson says:

“‘…knowledge management’ is an umbrella term for a variety of organizational activities, none of which are concerned with the management of knowledge. Those activities that are not concerned with the management of information are concerned with the management of work practices, in the expectation that changes in such areas as communication practice will enable information sharing.”

Anecdote have a set of objectives on KM activities or knowledge strategy, and more.

Dave Pollard stresses the importance of direct experience in the learning.

Visions of KM 2 is a great paper by Miguel Cornejo Castro, it describes the 3 KM activity components:

Process execution
- Repetitive methods
- Smoothing out bottlenecks
- I see blogs used as communications, wikis for workarounds

Project development (essentially a special type of process)
- Since projects are unique, finding people and conversation (tacit) are more helpful than generic explicit stuff (which mostly works fine for Process execution)
- I see blog fragments, conversation, and expert locators

Capability building
- Spans the knowledge of tools, processes (methodologies), and practice (experience with tasks)
- Learning and building know-how to increase effectiveness in processes and practice (projects/tasks)
- The whole social computing and enterprise 2.0 concept (a networked conversation enterprise, emergence, platforms)

This notion is described in Knowledge and Talent in a People-Ready Business.

Stan Garfield from HP covers a lot of the KM pulse on his blog, here are some posts on KM elements:

Benefits of KM
- Avoid redundant effort
- Avoid repeating mistakes
- Take advantage of existing expertise and experience
“If only HP knew what HP knows, we would be three times more productive.”

Key Activities of KM
- Share, Innovate, Re-use, Collaborate, Learn

The Role of Management and Knowledge Management

KM Tips and Myths

Stan points to the brilliant insight and realism of Andrew Gents, The four paradoxes of KM:
- Tacit vs. Explicit
- Local vs. Global
- Open vs. Closed
- Quantity vs. Quality

End thoughts

Frank finishes by saying:

“…the importance increasingly being placed on accessibility to information is seriously out of balance with the importance that needs to be placed on interpretation and sharing of information, and that this imbalance needs urgent action to redress.”

Wilson finishes with:

“…these latter practices are predicated upon a Utopian idea of organizational culture in which the benefits of information exchange are shared by all, where individuals are given autonomy in the development of their expertise, and where ‘communities’ within the organization can determine how that expertise will be used.”

Now to catch up on complexity, narrative inquiry, sensemaking (situational awareness), self organisation….a good start is unblocking streams so knowledge can flow, a bit like acupuncture.

Related

K-flow
Tap into the social capital
Knowledge Sharing in the new KM
More on the new knowledge diffusion
Participation is the currency of the knowledge economy
KM 2.0 model

June 26, 2008

Knowledge as Interpreter - ASPE

I came across a post on Knowledge Futures quoting Dave Snowden, about knowledge as an interpreter in the abililty to turn data into information. And then using a sensemaking process (making sense of this information/understanding it) which can create new knowledge to you.

This throws the hierarchy view of Data-Information-Knowledge-Wisdom as separate steps or levels, into more of a flux environment.

From the post on the role knowledge plays in data and information:

“…knowledge enables me to interpret information. If I acquire knowledge of management accounting then a chart of accounts informs me, if I have no such knowledge then it is data. Knowledge management this has, as one of its primary tasks the creation of sufficient shared knowledge to enable the use of information.”

From the post on Information Management and Knowledge Management:

“I do see utility in understanding the different between what it means to manage knowledge and what it means to manage information. I normally do that with a metaphor of the difference between using a london taxi (knowledge) and a map (information) to get around London. The map is data which has been structured to inform and if I share sufficient context with the map maker then it informs me and I can take action on it. I can also get a taxi where not only has the taxi driver internalised the map, but lots of other things as well. There is for example evidence of significant changes in the Hippocampus in London Taxi Drivers as a result of the two plus years of training they go through. Compete with a taxi driver (as a map user with a hire car) and you will loose. The map may get you there, but the assumption of shared context can be dangerous. I once used a map in New York and almost got mugged for exactly that reason. Its like the point on french cuisine - you may have the recipe but that is just a starting point it is not complete of itself.”

An object like a map is more static (unless it’s a wiki or a blog) so it only has set information, and depending on your know-how of maps, you will be able to read the map, and create new know-how and use it to get around town…the map is only information, it’s up to you to create the know-how (meaning).
The taxi driver is a dynamic information base that continually learns about the area the map represents. She contains lots of informal information that is not normally represented in maps, as that’s not really a maps job or purpose.

Shared Context

What Dave Snowden hones in on is that the shared context with the map is assumed. Shared context is one of the most important aspects of successful information transfer, it’s assumed that you know the context of your activity eg. an understanding of the topic, an understanding of how your team deals with this topic, establishing aspects of the topic. The more existing know-how you have on the information and its context, the more chance you have of successfully acquiring new knowledge and taking action accordingly.

Knowledge as interpreter

I really like knowledge as the interpreter, similar to what was said on Anecdote a couple of years ago, including this amazing diagram.

“Knowledge acts as an interpretant to turn data into information. The information we notice (we don’t notice all information channelled toward us), might create some level of dissonance (its surprises us or we ask ourselves, “What’s the story here?”) and if we care about resolving this dissonance we create knowledge. Knowledge is created through a sensemaking process.

But data to one person is someone else’s information. A commodities trader might stare at a computer screen of numbers which would look to most people as raw data. To the commodity trader, however, slight changes in the numbers conveys messages which act as information they might convert to knowledge (via sensemaking) and take action. Consequently, context is a key ingredient acting as an underlay to all three concepts of data, information and knowledge.”

Dave Snowden also has a similar diagram.

[ADDED 1/7/08: Joe Firestone’s paper, Key Issues in Knowledge Management, also deconstructs the Knowledge pyramid. This paper goes into a lot of theory related to this blog post.]

My stream of consciousness

You use your current knowledge or understanding to see data as information (not sure if you are actually turning data into information)

If you don’t possess the knowledge then all you see is data.

If you do possess the knowledge, you then make sense of this information in the sensemaking process where you may gain new knowledge (understanding).

I like how Anecdote say that the information you see may create a “dissonance” (kind of like you understand the information, but how does it relate to the whole), this is done by a sensemaking process, and “if successful” you have gained some knowledge…and perhaps take some action.

In theory, next time you are in this same exact situation (ceteris paribus), the level of dissonance would be non-existent, meaning there is no need for the sensmaking process and no new knowledge is created.
If this happened all the time you may feel you need a new job that is more stimulating and challenging.

Where there’s dissonance, there’s learning to be done…and knowledge gained.

Is it possible to never experience dissonance because you have reached nirvana?
I personally don’t think a highly evolved spiritual person, living in the now, means you have finished learning.

Experience as Interpreter

The above describes that you need knowledge in order to have the opportunity to create (discover/acquire) new knowledge.

But this can’t be right.

As a baby I may burn myself by touching a flame, as I have no knowledge that the flame will harm me.

How does this work, was the flame data to me, as I didn’t have the knowledge to be informed that it will burn me if I touch it?

And have I created new knowledge (not to put my hand near a flame again), all this without having knowledge to act as an interpreter to turn data into informatiom.

Since I could not turn data into information, then how could I possibly go forward in the cycle to use sensemaking to create new knowledge.

In this example rather than requiring knowledge to interpret data to information, an “experience” has become the interpreter.

I’d like to read about knowledge from an infant psychology perspective (if there is such a thing). Because if you have knowledge of nothing how do you ever start?

Etienne Wenger briefly mentions the need for social learning theory to connect with developmental theory.

[ADDED 1/7/08: Joe Firestone’s paper helps out here, on page 16 he says:

“…we are born with genetically encoded knowledge that enables us to interact with the external world and to learn…”

He desribes this as world 1 knowledge:

“…encoded structures in physical systems (such as genetic encoding in DNA) that allow those objects to adapt to an environment”]

Dissonance?

If a piece of data on a screen is flashing, “anyone” can notice that something has just happened to the data, it’s flashing, and if you possess the knowledge about what this signal means then it informs you, ie, it’s information to you…I guess it becomes knowledge if you can successfully interpret the meaning of the information.

Even though you know what this information means there is still a level of dissonance as you don’t yet know why it occured, you try to make sense of it and work out what’s going on, once you work it out, you have created new knowledge.

Structured to inform

Dave Snowden says “The map is data which has been structured to inform…”

He says:

“We have a mess of unstructured data to which we apply structure or interpretation in order to inform others, we put the data in context”

“If I structure data through process of abstraction and possibly codification then I create messages with which I seek to inform someone else. If that person understands the message they are informed; however if there is no shared context between message creator and message receiver then we are left with data, no information is created.”

A whole heap of random names means not much, but if the list is titled “customers aged 12-20″, then this becomes a structured message intended to inform.
If a person has shared context they will receive the message signal as information, ie. that these random names are people in an age bracket.

This does not imply that structured data equals information.

The data is structured or in an organised format, and whoever understands this organised data receives it as information.

Knowledge is the tool to achieve understanding and interpreting this process, but not only that, your knowledge has to have a shared context to receive the intending meaning.

Without the title these random names are just data, more precisely unstructured data.

According to the model in Dave Snowden’s post once you go through the sensemaking process, ie. you understand what the information means, eg. making inferences from comparing two lists you may work out that, “customers aged 12-20 tend to have more overdue books than customers aged 21-35″, then you can go through a path-finding process and take action.

The action you choose from your path-finding process could be sending a reminder out more often to customers aged 12-20.

Another Example

If someone gave me a project management schedule (eg. MS Project) it would be data to me as I don’t understand the technique and the symbols.

But if I was proficient in MS Project then it would be information as I can understand (interpret) this software.

But if I don’t share context with the author (know the person, history of the project, etc) I may have a hard time understanding (sensemaking) this information completely in order for it to become knowledge for me.

Conclusion

Knowledge is not a thing or object, it is what a person uses and creates.

Dave mentions that the knowledge management is about providing or creating conditions for shared context.
Shared context enables you to get to first base, which is being informed…to be able to use information, so we can take it to the second base in the sensemaking process.

I’m using a step process to explain, but really this happens more fluid or in a flux…all the steps mentioned could be happening at the same time.

Rather than the loop of Data - Information - Knowledge - Options - Actions being the main components, I’d rather think of what happens (based on Dave Snowdens diagram) as Analysing - Sensemaking - Pathfinding - Executing (ASPE)

To be continued…

June 6, 2008

KM 2.0 model

KM 2.0 in writing

If you read this blog (and others) it’s clear that knowledge flow is the competitive edge.
The more we share know-how and collaborate, the more we are aware, and the more we can hook up with the right people.
The more open and transparent an environment, the more a range of voices can be heard and ideas evolve.

We are capitalising on opportunies by leveraging the social capital (connecting human assets), using the wisdom of crowds.

Connecting and conversing with people is how we work in the physical world and KM 2.0 is extending this to the online world.
People get things done by talking and learning with others, therefore the concept of codify and store isn’t really in tune with human nature.

If we get things done in the physical work by participating, connecting and conversing, it seems logical the this approach works in the online world…especially so for the current climate of remote working and virtual teams.
People already get work done using email, but this doesn’t quite mimic the benefits of the physical world (it lacks visibility and discovery). Rather, an ecosystem with online profiles, social networking, group conversations is similar to how we congregate, network, and discover in the physical world.

KM 2.0 in talking

Sometimes I feel explaining the concept is hard to absorb for some (it really has to be experienced), so perhaps weaving together some quotes is more articulate and succinct.

Some of my favourite excerpts on this concept are by Chris Fletcher, Rachel Happe, Larry Prusak, Ross Dawson, Michael Idinopulos, Don Tapscott, Jay Cross, JP Rangaswami, and Chuck Hollis.

KM 2.0 in pictures

Another idea is trying to capsulate the essence of a concept in a diagram.

NOTE: I’ve missed out some pieces in this picture, such as: bookmarks, rss, attention, personalisation.