Library clips

sharing ideas thoughts and feedback

August 18, 2009

Design for adoption : Synchronous to Asynchronous interaction

The other day when I posted on social networks and ad-hoc groups, I mentioned these online tools need to mirror both our offline behaviour, and our online real-time behaviour.

I set the scenario that at work there may be a task or initiative which involves people from many departments.

What usually happens is everyone gets invited to a meeting: in a room, via a telecon, or something like webex (we now use MS Office Communicator).

After the meeting the coordinator will go back to their seat, document the minutes in MSword and send an email attachment.

Then various people use email to do their bit.

Then we reconvene in a new meeting to see where everyone is at.

This is hopeless; I say when we go back to our seats we can still assimilate the real-time room (meeting) environment in an asynchronous fashion.

This makes for better communication, coordination and awareness…and transparency by default.

After the meeting someone can create a group space and invite all members as quick as sending an email.

Here they will find the minutes in a wiki, each page has a comments stream.

Here they will find a question space (just like issues raised in the meeting)

Here they will find a blog to post updates about the part they are working on.

Well, look at that, we can do asynchronously, what we usually do when we are in the same room.

This online tool is a social network with ad-hoc groups, where you have your own “mypage” that lists all groups you are working in, even better if you can post to any of the groups from your page.

Integration

A good way for adopting new practices is in the design and integration with existing tools.

Just like Jon Mell describes less use of email by incorporating IM into email (placing it in the same spot where you create a new email)…what I would like to see at the end of an Office Communicator Live Meeting, is to be able to spin this real-time (synchronous) ad-hoc group into an asynchronous ad-hoc group using a social network and group tool. Somehow both tools would be integrated, making jumping from one to the other the obvious thing to do; rather than using email for asynchronous communication and coordination.

People often find email conversation frustrating so it’s decided we need another meeting…with the correct asynchronous tools you don’t need so many meetings as we can use blogs to communicate, forums to discuss and wikis to collaborate on a perpetual basis…I alluded to this use case for teams a while back.

BTW-Why is Outlook not an internal Facebook and MS Office Communicator an internal Twitter?

Like my last post, design is key to influencing new behaviours.

More from Jon Mell:

“…there is no reason why at the front end we cannot combine communication tools at the presentation layer so that people don’t have to think as much about how they are going to communicate and which tools they are going to use. There is a scale here in terms of how advanced people are in their adoption and usage of Enterprise 2.0. Once people are comfortable with the concept of Enterprise 2.0 then they will naturally and intuitively know which tools to use without thinking. At the initial adoption stage, however, putting guidance and pointers in the flow of existing tools can have a significant impact in terms of alleviating any fears of using a new system. Some users may always stay in this mode, where they need the system to do the thinking for them in terms of which tools to use, and others may move to a position where the thinking becomes more intuition.”

March 9, 2009

Team-based communities : Transparency and Crowdsourcing for a more cohesive workplace

Yesterday I posted on a team-based community using the space for the purpose of communicating to several groups.

NOTE: I left a comment on that post that an ideal space for teams to work is not one designed for learning and sharing (CoPs), but rather one designed for tasks. Although they use the same tools (blogs, wikis, forums), the task spaces are more designed to how humans do tasks. A great example is Traction’s case study on the ShoreBank. But since we don’t have a team/task 2.0 type tool our teams are making the best of our community tools.

In this community it was decided to use a blog, rather than several email lists; now all discussion is inclusive and people can visit the blog at anytime, rather then looking for that last email “about that thing I was supposed to do, or did I delete that email.”

I mentioned that the authors in the main communications blog were the people in the first two levels of the hierarchy. This makes it mostly a one party communication tool, besides the other parties being able to comment.

But that insightful comment may be too late, as the decision has already been made and now being communicated.

What I think is important is more transparency (more “good to know”, than “need to know”), which in this example can happen two ways:

1. I mentioned that the authors of the main communications blog will also have an admin blog

  • I’m not yet sure if this has reasons to be private, but if not, it could be open, so the other groups can listen in on what’s being talked about
  • In the end what’s being talked about will eventually become a decision and be communicated to them
  • In the end these decisions decided by people higher in the hierarchy will effect the way they work
  • People higher in the hierarchy don’t always know about contexts and how work is actually practiced at ground zero
  • So sometimes some of their decisions may be impractical or simply be better or more appropriate or useful, had the people who are impacted, had some input into the issue/task

2. I mentioned that all parties will be able to author in the main forum

  • The higher ranked teams can use this forum to crowdsource for input on an issue they are working on
  • This is a simple way to get impacted parties involved…decisions communicated by higher parties will be more relevant or practical as they have had dialogue
  • This forum can also be used to crowdsource ideas in general, where insight that the higher parties never thought of can become part of strategy.
  • It’s also a space where the impacted parties can ask questions

Transparency is such a key factor to a more effective workplace…decisions become more relevant as other groups are able to listen in and intervene or make suggestions before a decision is made.
We can easily see this saves time and money, is a more cooperative approach as related groups are more aware of future impacts (and can prepare or align), and promotes a more cohesive workplace.

Or we can look at the negative perspective; sometimes a decision is made in private, and the decision cannot be reversed, that is, it’s too late.

eg. parties high in the hierarchy buy some software, that is antiquated or not as useful as some cutting edge software…it’s tool late, the money has been spent

Had they been transparent and even crowdsourced some opinion, they would be amazed by the contexts and scenarios people would bring up that would actually make it easy to choose a product as there would be more relevant criteria.
They would also be surprised, that people may know a lot about this type of product, and suggest some more cutting edge choices.

This post has not been about the lack of ultimate communication, it’s about lack of transparency that goes into the path leading up to the eventual communication, and how that communication could be more relevant, and the gossip that seeps.

And from the workers point-of-view; the more included they are, the more they feel a part ownership of decisions, the more satisfied that they can have input into the way they work.
Often there is so much frustration, as in the end it may impact your work routines, and who knows best about ground zero, “you”. So being included somehow, or an opportunity to express your thoughts makes for a more happy and comfortable team, as well as more relevant decisions. Usually it’s the opposite, you hear rumors, or know of talks happening, but you feel so excluded…especially when someone at your level somehow knows more than you.

We know it’s not always going to be the case where others can listen in on some conversations, but it should be default “good to know”, and only be “need to know” when required.

Am I missing anything here?

Any thoughts on how transparency impacts on power, and people in the hierarchy that may feel threatened, disintermediated or usurped by the collective?

Team-based communities are about change, commitment and tasks

This is a follow up from my post, Team-based communities.

In that post I briefly described the dynamics in Teams using CoPs; basically same dynamics (just different space), the obstacles in participation, and how the lead is to be a role model for adoption and facilitation of the CoP.

This post is more of a prequel to my past post on team-based CoPs, as I want to share some of the questions I’m now beginning to ask Team leads who want to set up a CoP space for their team.

Online communities provide a new way of working; and are more about the people than the tools. They are a catalyst to changing behaviour, routines and habits in order to improve social productivity

But first here are some general questions I ask any type of new community.

Broad questions to consider for new communities (both team and shared interest)

When requesting a community there are a few things to be considered prior to set up:

  • Is the community about shared learning, or to help a team coordinate and communicate?
  • Is the community a public face for the rest of the firm to be aware and interact with that team?
  • Will the community content be for a private or public audience?
  • Will the community content be contributed by members only, and be visible to read by non-
    members?
  • Who will be leading, and running the community?
  • What are the existing community indicators? Eg. Email groups, telecon groups
  • Will your community be used more if it’s regional or topic based?

Key questions for team-based communities

  • Do you have a communication, coordination, and awareness issue, both within your team and with the organisation at large?
  • Do you want to really do something about it by dedicating time and passion to changing behaviours?
  • Are you prepared to change routines, facilitate, and role model this effort?
  • In the end our communities tools are a catalyst or an excuse to improve team dynamics, productivity, and a new way of working.

What we are used to hearing about in CoPs are: learning, sharing, social productivity, ask a question…

This too can happen in Team-based CoPs, but a good idea is to focus on solving a problem, coordinating an issue, communicating a message, which is what teams do.

It’s not about social computing (hopefully these tools will soon become boring), it’s deeper than this, it’s about a better way of working eg. using blogs and wikis in a CoP space to coordinate and communicate a task rather than scattered emails and attachments.

I’m finding that when I now workshop with teams I’m not just the web 2.0 guy, I’m feeling more like a change consultant in the way of getting deep into the existing information flows, and offering new ways to do it more effective.

Communication example

I did a workshop with some team leads the other day asking the above questions.

It turned out the team lead wanted to use the CoP to communicate a message down the hierarchy.

This was a good start, as I knew what they wanted to achieve.

Next I asked what typical email distribution emails she sends out.

She listed all the groups on the whiteboard.

Then I asked what is the frequency of emails you send to all these groups.

Once we had a visual of this we could identify what tools and how many of them we were going to use.

Most of her communication emails needed to go 4 levels deep in the hierarchy.
Her second most frequent type of communication is only 2 levels deep.

The answer was two blogs.

One is a more admin blog, and the other to reach ground zero.

We also worked out that people up to 2 levels directly below her could also author in the ground zero blog (so to speak), as well as the admin blog

This CoP will also have a forum for any of the sub-team groups to use.

Coordination example

This next example actually isn’t a team, but is still about solving a coordination issue that happens across teams (This CoP is made up of leads from different teams.)

We have several applications under the one suite and every month a coordination person that represents all these teams to the rest of the business, emails each of the 6 or 7 application leads to email her their monthly release document.

She then compiles them into one big monthly release document, and then emails the company.

Throughout this process she often gets requests for the latest before she sends out her broadcast email.

She also may get subsequent emails from each application lead to add bits that they forgot to include in their original email to her.

During this process she may be emailing back and forth with each lead to clarify.

Also during this process each lead doesn’t know the conversations she’s having with the other leads.

This is what I suggested:

  • the coordination person to use an admin blog to post an announcement to the leads to prepare their monthly release note
  • leads get an email as they are subscribed to the blog
  • at any stage they can reply to this email, which will leave a comment on that blog post (this is cross awareness and common discussion)
  • this blog post has a link to a wikipage for that month
  • the leads go to their respective wikipage and enter their notes
  • each lead or anyone else can visit the wiki at any time…maybe??…as long as they know it’s not official as of yet
    (or they can ask a question in the forum representing that application)
  • each lead can keep updating it at any time up to the deadline
    (then the coordinator can lock off those wikipages even to those leads…she can perhaps continue to make PDF versions as well)
  • she may then use another blog, or email to announce to the company at large

Intended result:

  • This process involves no original emails
  • The coordinator is no longer a bottleneck
  • The wiki process also becomes the end product
  • The coordinator is still coordinating the process, but it’s simply more streamlined and actually less work for her
  • All conversations are documented in the open, so more people can be aware, and quick to act
  • The release wiki can seem like a database compared to a heap of folders for each month each containing PDF’s
    (getting away from the filing cabinet, and moving to a more friendly interface)

[ADDED 10/03/09: Team-based communities : Transparency and Crowdsourcing for a more cohesive workplace]

September 24, 2008

My recent article on KM Review - When Two Worlds Collide

A couple of months ago I was asked by the editor at “KM Review” to write an opinion piece for their organisational learning issue.

This could not have come at a better time as my blogging has come to a convergence point where the read/write web has enabled KM and Learning to become one in the same in some respect.

It also got me recognition at work even though I have been internal blogging about this stuff for ages, it goes to show the power of authoritativeness.

twitstamp.com

This article was a challenge as I had a 700 word limit, my only other experience is an interview, so actually writing a piece was a developing a new skill set for me, very different from blogging.

Blogging is easy as I choose the topics and I can blab on for as long as I want…having a word limit and a different audience changes all this.

Rather than my affordances of space and casualness to allow stream of consciousness, personal, and informal writings; the different audience, format and word limit, meant I had to pack a punch with each paragraph, and try to fill out my statements without the luxury of pointing to examples, experience, and explanations.

I found this very hard, and have since come to know that blogging is a very different beast than traditional publishing (the good thing about KM Review is they let me say what I want, so there is no inhouse bias or anything like that). Even though a blog can be used to publish professional articles, I think traditionally it’s more sharing, opinion and a learning soapbox, a way to express and develop…a conversation.

In a blog I’m expressing my thoughts and ideas as it happens in an informal fashion, whereas in an article I am codifying what I know.
NOTE: Basically I looked over all my blog posts and condensed them into the article.
I also looked in delicious for stuff that has come across my radar in the past that I bookmarked for a rainy day, and I also searched my Google Reader. Just this research process alone (come to me web) typifies exactly what this article is about, very zen…checkout Lee Bryant’s post for more on network productivity/social filtering/actionable collective intelligence, I’ve quoted it in my k-flow post.

From reading the article I’m not sure if all the information will holistically be understood by the reader, as there is not much room to explain in 700 words. But if you were then to read my blog posts, you would get to know my character, as a blog allows it to come through; you would get to know my style and wavelength, and you can leave comments to clarify points, contexts and examples with me. Also with each point I make I have the liberty to expand on contexts, and examples.

In the end there is going to be more of a chance that the information is transferred to the reader and internalised as knowledge, as the reader has more of a scope and familiarity (abstraction) with me to understand my message (signal).

These two formats complement each other, and I’ve spoken before about the power of blogs being used as “thinking out loud” and “work in progress” in writing a deliverable. Firstly this is a crowdsourcing technique to evolve the deliverable itself, and secondly when reading the deliverable a reader can refer to various blog posts for more peripheral information on the “workings out” of what took place.

Why is this important?

Deliverables and best practices are not always going to suit your situation, and when applied like a recipe can have a distasterous effect as they can leave out peripheral content, and your context is different. A best practice is not always going to be the best practice (pardon the pun) as there are so many different variables that can be different with your situation…see my post on on anticipatory awareness for more.

Alternate methods, like blogs, wikis and social networking really fit in with the promotion of knowledge sharing, and this is captured nicely by Ron Young’s article in the same issue of KM Review called “Reap the rewards from combining learning and KM”.

The virtuous KM circle is made up of: Trust, Communicate, Learn, Share

If you don’t have trust, then people are less likely to share or communicate, and less learning results.

Also there must be a personal benefit, like a learning feedback loop or reputation as a publisher, to motivate you to share (What’s in it for me?)

…you can become a subject matter expert when you make your know-how visible (and people can subscribe to your thoughts)

Again, once you have trust and simple tools, and a way to connect to people, we are more prone to share. We receive feedback and a reputation in this conversation network, in the end, as Dave Snowden says, we may form interdependencies with our trust circle which ultimately means our most effective way to get work done is by leveraging the social capital (ie. we come to rely on each other to share what we know to get things done). So by creating the conditions for “knowledge sharing”, we have enabled it to happen using a naturalistic approach.

Ron sums this up by saying:

“Capturing new learning and ideas as they occur…transforms an organization from an environment of episodic learning and innovation to one of continual learning and innovation.

Giving people an ecosystem where they can: improve, learn, self develop, and connect to like people, is a way to achieve the aims of KM. Not only can we re-use and apply knowledge to given situations but we become smarter and agile, so there is a mutual benefit at both the individual and organisational level

Related
Social learning and social computing
Flexible uses of web 2.0 tools



When two worlds collide: KM + social networking = competitive advantage - Upload a Document to Scribd

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

Get free blog up and running in minutes with Blogsome | Theme designs available here