Sharing Knowledge

This is indeed a succinct and useful introduction to knowledge management in the context of knowledge intensive organizations.

Sharing Knowledge.

Sharing Knowledge
(.pdf) has been receiving quite a bit of attention in various knowledge
management blogs. It’s essentially a case study of how to create a
knowledge sharing environment in smaller organizations. Most of the
suggestions are basic and should be familiar to those who have been
following KM developments. The document does provide a nice overview of
wikis, communities of practice, and general (physical) workspace design.

[elearnspace]

ESJ: A strategy for personal knowledge management

Jack Vinson provides a nice summary of what I had to say last week about personal knowledge management in his class on knowledge management. It’s a notion that I am continuing to explore. Another cut at finding an answer to the question that I find intriguing in my newest column at Enterprise Systems Journal. I try to build an argument that it is in each of our selfish, best, interests to develop and adhere to a strategy for personal knowledge managemment.

What is PKM, anyway?

As Jim McGee said, he was a guest speaker in my KM class Wednesday night, talking about personal knowledge management (PKM). He primarily gave us a framework on which he builds the idea of a PKM strategy, and he told a bunch of stories to help people get the idea. Jim’s framework consists of three components

  1. Portfolio. The portfolio serves as a record of work done, a backup brain, and as a sales tool (just as an artist’s portfolio is an advertising tool).
  2. Manage Learning. The portfolio also serves as a tool for reflection on how the work went last time and how it could be better. This is also an under-emphasized aspect of PKM.
  3. Master the Toolkit. Reflect on learning and reflect on how you use the tools of your trade.

Portfolios are critical to the concept of knowledge work as craft work. And though people frequently get lost in conversations about the technology, nearly everyone does some version of this. How many files, emails and pictures are archived on your computer? With the discussion of PKM, one goal is to be smarter about how we manage the portfolio.

Managing learning is an aspect of PKM that frequently gets overlooked. The knowledge worker needs to be aware of how she works and look for opportunities to work more effectively. (I almost said “continually look for opportunities,” but I realize that this begins to seem like a knowledge worker could get lost in constant navel-gazing. A couple students pushed on this issue in the discussion.) The point is that the knowledge worker’s regular process needs to include reflection. I believe this is the power behind the Carnegie program, Stephen Covey’s Seven Habits, David Allen’s Getting Things Done and similar processes: they offer a process by which people can think about what is important, act against that knowledge, and review both the action and the direction for the next time (sounds like “plan, do, check, act“).

Mastering the toolkit gets too much verbiage. It’s far too easy to get lost in playing with new tools, whether that is a circular saw or a wiki. PKM begins to look a lot like personal information management in these cases. At the same time, part of the reflection process can include a review of how I use the tools and whether there are better tools available. I can choose to seek out new tools when there is enough friction with the current tools (tool geek), or I can rely on my larger network of friends and colleagues and contacts to introduce me to tools that they find particularly helpful. In the class discussion we recognized that each knowledge worker will require a different set of tools because we have our own processes for doing things.

Yet, there is something that still doesn’t sit right for people. Denham Grey has argued that knowledge is socially constructed, so personal knowledge management doesn’t make sense. In a different twist, I would include understanding the skills and interests of my nearby networks to be at least as important as remembering where I filed that report. This would make my networks another part of my portfolio, including the fact that my network can be used to help sell my skills and services.

Comments

jackvinson (jackvinson@jackvinson.com) [Knowledge Jolt with Jack]

Some Knowledge Management Blogs from Bill Ives

A nice list of blogs that deal with KM topics from Bill Ives. I'm
flattered that Bill chose to include mine among the list. You should
definitely check out the rest of the list as well.

Some Knowledge Management Blogs.
When I was at Braintrust 2005 last week, someone asked me about good
blogs to read. Since it was a knowledge management conference I put
together the list of 17 below. Eight are cases in our own business blog
book… [Portals and KM]

Blogs as personal knowledge management tool

I'm in the midst of a similar project as a way to learn WordPress as a step toward converting McGee's Musings to WordPress in the not too distant future.

In the opening post, John Hesch quotes an observation from Paul Allen that struck home forcefully:

But like some other good habits I have developed over the years which
are hard to teach and harder yet to convince others to do (like taking
notes at every meeting you attend, and storing all your personal
knowledge in a searchable database), I have a very hard time convincing
anyone to start their own blog. Most think it would be a waste of time
[Paul Allen: Internet Entrepreneur]

Last weekend I did a seminar at DePaul University's School for New Learning on
the topic of personal knowledge management and I've been thinking on
this odd problem of technologies that need to be experienced to be
understood.

Blogs, wikis, and social software all suffer from this need to
spend time with them on their own terms. In organizational settings,
this makes them hard to introduce. Decision makers want a clear story
about investment and return (and they'd prefer hard numbers). I'm still
working out how to best formulate one. I suspect it will depend on the
unique characteristics of each organization.

The series continues with Part 2, Part 3, Part 4, and Part 5.

Creating My Personal Information Manager Using WordPress. Creating My Personal Information Manager Using WordPress:
A very interesting step by step series of instructions (in three parts
so far) of creating a PIM using WordPress. John runs Blogging Pro and
is by no means new to WordPress. [Weblog Tools Collection]

Pro metadata will lose to folksonomy

Not only does Shirky nail it, but Cory hones in on the money graf s for
us. This is clearly one of a class of problems where scaling issues
overwhelm other factors and force solutions to be somehow distributed.

These are much like the situation in the early days of long-distance
telephone service that needed operators to complete all calls. Analyses
at the time predicted that the services would fail because your clearly
were going to need to hire so many operators that the system would
collapse. The solution, in that case, was to effectively make everyone
an operator by inventing direct-dial long distance and area codes. Of
course, we've now reached the point where area codes are an anachronism
and have little predictive value about where the phone in question
exists in the physical universe.

Shirky: Pro metadata will lose to folksonomy. Cory Doctorow:
Clay Shirky continues to just totally nail the questions of metadata,
authority, and user-created content. Today's installment: why crappy,
cheap, user-generated, uncontrolled metadata will win out over
expensive, controlled, useful, professionally generated metadata:

Furthermore, users pollute
controlled vocabularies, either because they misapply the words, or
stretch them to uses the designers never imagined, or because the
designers say “Oh, let's throw in an 'Other' category, as a fail-safe”
which then balloons so far out of control that most of what gets filed
gets filed in the junk drawer. Usenet blew up in exactly this fashion,
where the 7 top-level controlled categories were extended to include an
8th, the 'alt.' hierarchy, which exploded and came to dwarf the entire,
sanctioned corpus of groups.

The cost of finding your way through 60K photos tagged 'summer',
when you can use other latent characteristics like 'who posted it?' and
'when did they post it?', is nothing compared to the cost of trying to
design a controlled vocabulary and then force users to apply it evenly
and universally.

This is something the 'well-designed metadata' crowd has never
understood — just because it's better to have well-designed metadata
along one axis does not mean that it is better along all axes, and the
axis of cost, in particular, will trump any other advantage as it grows
larger. And the cost of tagging large systems rigorously is crippling,
so fantasies of using controlled metadata in environments like Flickr
are really fantasies of users suddenly deciding to become disciples of
information architecture.

If you want to trace back to some of the items that launched this most recent disscussion, here are some of the key links:

Snowden’s rules for knowledge exchange

I don’t know how I’ve missed Snowden’s rules for knowledge exchange. Now, I can find them here.. Thank you Judith.

knowledge conversion as a social process….

Today I was reading an article in EContentMag.com titled–Knowledge Management Involves neither Knowledge nor Management–by Martin White.

Among other things, Martin writes about Dave Snowden‘s three rules for knowledge exchange:

“Knowledge can only be volunteered; it can’t be conscripted.”
“People always know more than they can tell, and can tell more than they can write.”
“People only know what they need to know when they need to know it.”

[judith meskill’s knowledge notes…]

BlogWalk 6 in Chicago

Definitely looking forward to having this come to Chicago. And to finally getting to meet Lilia face-to-face. Glad to see that Jack Vinson is able to take a lead role. Jack, you know where to find me for help.

BlogWalk 6 in Chicago

As Ton has announced, “It is our pleasure to announce a new edition of BlogWalk, the salon-like get togethers Sebastian Fiedler, Lilia Efimova and I are organizing.” I will have the pleasure of being the local host, but I will be getting lots of help from everyone who attends. We’re planning on the 21st or 22nd of January up in Evanston (just north of Chicago) – very convenient for me. For more information have a look at the BlogWalk wiki.

jackvinson (jackvinson@jackvinson.com) [Knowledge Jolt with Jack]

Tuning in to the whispers

Another little gem from Jack Vinson.

Apropos of this thought is the item next to it in my aggregator from Evelyn Rodriguez, A Loud Voice Cannot Compete With a Clear Voice. In addition to both of these being excellent food for thought, they also illustrate the notion that RSS plus newsreaders like Radio are your window into a distributed network of intelligent agents all applying their idiosyncratic eyes and minds toward filtering useful information in your direction.

Data, Information, Clarity?

While listening to WBEZ, the Chicago NPR affiliate, begin their non-pledge-drive-pledge-drive, I was surprised to hear a new version of the data-information-knowledge discussion. It went something like this:

It’s about clarity. You are overwhelmed with data from 24-hour news networks and the internet, but there is too much. At WBEZ, we analyze all this information to bring you clarity about the news of the world.

And they aren’t too far off. Clarity is one of those components of knowledge that makes knowledge so difficult to quantify. Other components include context, understanding, attention (thanks Tom Davenport), history… Interesting.

jackvinson (jackvinson@jackvinson.com) [Knowledge Jolt with Jack]

KMPro panel on Blogs in Business

It was a lot of fun riffing with Scoble, Ian, and John about blogs in the organization. I’ve got some notes and reflections I’ll want to post later, but wanted to get this nice summary from Jack posted while I had a moment.

KMPro panel on Blogs in Business

KMPro Chicago hosted an excellent discussion of Blogs in Business with Jim McGee, Robert Scoble, Ian Kennedy and Jon Powell. We covered a lot of ground with a focus on how blogs could be valuable both for marketing to the outside world and for building conversations within the company.

One very interesting thread throughout the evening of conversation was the idea of how blogs can be used to extend the socialization framework that we get when smart people gather around the cube, board table or in the lunchroom. In those situations, people are sharing and learning from one another, but it happens only within a small group of people who happen to be near each other. With blogs (and admittedly other social software) people can extend that reach out to larger and larger groups of people. This was the area where Jon Powell, invited as a skeptic about blogging, saw the most value in what blogging could bring to Hewitt and other corporate environments. Humans seem naturally inclined to share and help one another, and the capabilities being developed with blogging give people more opportunities to do so.

An example of how blogs might work within an organization: Rather than having status reports sent on email, ask those people to post their status reports to a blog. With email, only the recipient knows what is happening and they can provide feedback only when they understand the matter in question. With a blog and with people subscribing to that blog’s web feed, there are many more eyes viewing the reports and many more eyes that can provide feedback or connect the author the help they might need. It’s useful to note that while most readers may just skim, the small minority that do take an interest in the material are exactly the ones that you want taking an interest. They have the background, interest and time to do so, where the immediate supervisor may not.

In describing blogs, Robert Scoble drew from his Five Pillars of Conversational Software: 1. Easy to publish; 2. Discoverable; 3. Social behaviors become visible; 4. Permalinks to a specific item; 5. Syndication. These items were referred back to a number of times throughout the conversation as people asked about other examples and technologies that seemed to be similar. For example, e-mail is neither discoverable, permanent nor syndicated. Similarly, Sharepoint, while ‘easy’ to post and permalink, is not easily discoverable. Discussion groups have a number of the pillars, but they seem to lose in the arena of social behavior in that individuals cannot build their own presence, other than through being known as the expert within the given discussion group.

The idea of easy publishing was discussed by a few people. Rather than needing to “create a website” or “write a paper,” the only thing a blog posting requires is a few cogent thoughts and/or maybe a reference to someone else’s cogent thoughts to which you want to add more. Along this vein there was also conversation around the difficulty of doing this within a corporate environment. Traditionally, corporations have not encouraged people to write what they think – my last company had a policy that more-or-less said this for fear of the legal discovery process. In addition, “people are a lot more worried about making fools of themselves” in corporate settings than in their personal space. The corporate culture will clearly need to change if blogging is to take root.

McGee suggested that blogging in the business – and in society – is going to go through a similar adoption curve as has e-mail: everyone has an address today as a matter of course, but not so many years ago people were trying to figure out what value email might bring to the organization. Blogging – or the ideas behind blogging – will become familiar over time.

Powell mentioned that Hewitt has over 10,000 internal Lotus Notes databases. In post-meeting conversation, a former Anderson person mentioned that they had over 17,000 Notes databases. The question was raised, how will “giving everyone a blog” change the issue that this information is written down and forgotten? How will blogs change the fact that we are drowning in information (or data)? For one, the auxiliary tools that read web feeds (syndication) or that search across weblogs are critical to the difference. In addition, it is the whole nature of how blogs are used and how they operate. A blog is generally written and owned by an individual; it is where they develop their voice and develop reputation: online discussion groups and databases don’t provide this level of ownership to the material.

How does one get started with all of this? People. Passionate, smart people. Give them the conversational tools and they will expand their over-the-cubicle conversations out into their wider sphere of contacts and sources, creating more potential for innovation and flexibility within the organization.

Other notes
McGee made an almost throwaway comment: Within a few years, knowledge workers will probably be taking their own technology into the workplace and negotiating connectivity with their employer. Why? The knowledge worker is going to be relying on that technology to operate in any space, whether it is home or work or consulting or the next job. Why should she be locked into an environment in which she is not familiar or effective?

Scoble has mentioned many times that he monitors nearly 1,000 blogs. He claimed this evening that he could see getting upwards of 10,000 blogs as the capabilities of web feed readers continually grows and improves.

While trying to find Robert’s Five Pillars, I discovered Sylloge’s Five Pillars of Social Software (http://www.sylloge.com/personal/2003_03_01_s.html#91273866): Identity, Presence, Relationships, Conversations, Groups. A nice parallel with Robert’s pillars above.

jackvinson (jackvinson@jackvinson.com) [Knowledge Jolt with Jack]

My worst technology mistake

Ben Bradley of Growingco.com interviewed me about Knowledge Management that ran over at Darwin magazine a few weeks back. It was an interesting exercise reflecting on my worst technology mistake. It probably won’t surprise anyone here, but I concluded that

In particular, I ve become a lot more skeptical about top-down approaches to knowledge management. And I ve become much more cautious about the importance of pushing the technology envelope. We were doing a lot of good things to improve internal communications and interactions among our experts. We started paying more attention to that to good effect. Not as sexy, but a lot more impact.

My current thinking is that organizations that want to make progress on KM will need to blend top-down and bottoms-up approaches. It’s not a question of which approach is right, but of how to blend both approaches.