e-wot?

I went to two workshops today at KM Singapore to find out as much as I could about Social Network Analysis. The first by Prof Lee Chu Keong from Nanyang Technological University. The second, in the afternoon, was on Business Network Analysis Techniques in Project Management by Graham Durant-Law.

Off the top of my head I can say that I learnt two great words:

Homophily: the tendency for individuals to associate with similar others: ‘Birds of a feather, flock together’.
Propinquity: nearness in place, relation, nature or time.

Some interesting stuff, but a lot to absorb. The data gathering part of SNA seems too labour intensive for my liking. Maybe tools will evolve to help simplify this process. When they do, I’ll have a go.

At the end of all this, the person who’d been sitting next to me leant over and said, ‘very cheem, what?’. Yeah, it was. 

Great conference today. In the morning, keynotes from Graham Higgins, Manager of Organisational Development and Learning, Cathay Pacific and Tony Sheehan Director of Learning Services, Ashridge Business School… great presentations.

In the afternoon a knowledge cafe with 14 KM practitioners from different companies showing and sharing their projects and experience. Awesome. Lots of opportunity to talk to other practitioners. Not like a normal conference - much better.

I drank far too much coffee at the conference, so before the caffeine buzz subsides…

One thing that made me cheer (on the inside) is that in every conversation I had, there was someone saying that Knowledge Management is a term that should not be used outside of the KM community. And this time it wasn’t just me saying it. O.O

In other words, don’t mention KM when talking to rank and file staff. One reason is that it’s unnecessary jargon that requires layers of workshops and communication to ‘get the KM message across’. But the main reason is that most staff will think that ‘KM’ equals ‘more work’. Many times I’ve heard “so now you expect me to do KM in addition to my usual job?”.

Over the past 4 years I’ve explained this particular problem to management, who’ve nodded sagely. We commissioned a report which found the same issues raised in staff interviews. Message loud and clear, but somehow always sidelined. I suggested that we try ‘Ninja KM’ or ‘KM by stealth’, but nobody was listening (or they didn’t get it). So now I’m delighted, because now I can say that I’m not alone when I recommend to others something along the lines of: “Think ‘KM’, but say ‘problem solving’ (better still use terms which talk directly to your audience’s context)”.

Instead of saying ‘Knowledge Management’, try ‘resource management’, ‘risk management’, ‘asset management’… or whatever makes immediate sense to whoever you’re talking to.

[edit: James Robertson owes credit for being the first to articulate this idea, here's his post in Column Two that made me slap my forehead and go 'yes, that's it'. It's from 2004, so it's not a new idea at all. It's funny how ideas take a while catch on and hit a tipping point like this one did today.]

At last night’s IKMS evening talk, Bonnie Cheuk gave a great presentation on ‘Unwrapping the potential of Enterprise 2.0′. Bonnie is the Global Head of Knowledge and Information at Environmental Resources Management (ERM). She showed us how ERM has taken to using blogs, wikis and discussion forums in Sharepoint. I liked the fact that her focus was on the people, the tasks and the communication - not so much focus on the tool.

Her talk really brightened up my normally gloomy view of Sharepoint. And she shared her secret KM recipe, here it is (sshhh):

Here are some other points she made about leadership 2.0:

• Employee-centric
• Listen and value every staff’s input
• Ready to be surprised
• Tolerate mistakes
• Hear what you may not like to hear (and value it)
• Genuine dialogue with employees
• Willingness to let go the leader’s authority / power
• Leaders have to participate (not delegate!)

We had a chat while she was setting up before her talk. Bonnie and I had worked together before on an earlier Sharepoint project in Singapore, so we had some stuff to catch up on. The thing that makes me giggle gleefully is how she described Sharepoint’s blog and wiki tools - She called them ‘Fake Blogs’ and ‘Fake Wikis’, meaning that they don’t quite have the features and functions most of us have come to expect. And yes, that’s exactly how I’ve been feeling about them for a long time… In fact, ever since I tried to embed media into them. Thanks Bonnie, I’ll be calling them fake from now on too, thanks to you.

I’m a bit disappointed. Jotspot was great. Google’s replacement for it, Google Sites, is not so hot. Here’s why I think so.

Jotspot was more than a wiki. It was a platform on which developers could build applications. For example, the Jotspot site we use has a blog, an app called a ‘bug reporter’, a discussion forum, a ‘knowledge base’ app and a project management tool. There were many other apps you could choose to add. I was hoping that Google Sites would continue to deliver this great functionality. Sadly, it does not. Read More…