As an occasional Subject-Matter Expert (or “smee”) myself, I hate to deprecate the category. I’m not sure what’s happening to expertise, but it’s not what it used to be.

Maybe expertise is very situational: you’re an expert because of a confluence of factors in a given moment, but if several of those factors change, it turns out your expertise isn’t so portable. Or maybe expertise is just fleeting. We just can’t keep up. Or maybe we misapply the term “Expert” to people who have qualifications and some broad knowledge of their domain, but their understanding doesn’t go much deeper. I’m channeling a little of The Black Swan here, which really reset my perception of experts.

One positive thing that’s happening to expertise is that we’re starting to realize that it’s social. If you can get the right few people to talk together about a situation, sharing their perspectives and insights, you might just get some good advice. In that spirit, my friend Mark Oehlert recently coined the phrase “Subject-Matter Networks,” which I really like.

There’s a more radical position fleshed out in The Wisdom of Crowds that large, diverse groups of uncorrelated individuals can arrive at better answers than any individuals in the crowd. While I believe Surowiecki’s examples, I find the situations under which we get “wise” crowds are narrow enough that they don’t exclude networks brought together at the right time.

The notion of Subject-Matter Networks seems to indicate that a thriving community of practice, in which members have a good understanding of one another’s interests and capabilities, will beat big databases of case studies and packaged “wisdom” any time. Fortunately, this is the way much of Knowledge Management is going, after a long time out in the deserts of databaseland.

To be sure, there are many of these but this is from a remarkable person – danah boyd.  Boyd’s a long time observer of all things social/technological as well as (currently) a Senior Research Fellow at Microsoft.  Her blog posting “Social Media is Here to Stay” offers a brief  history of where new media came from as well as how — and why — it works so well.  Highly recommended.

In days of yore, Knowledge Management proceeded pretty much along these lines: really smart people at headquarters figured out how best to organize valuable business information typically carried around in employees’ heads, and those same employees were asked to stay after work to download (into appropriate knowledge-boxes) what they knew … for The Greater Good of your company.

A nagging problems with this model was that it never satisfactorily answered the line-workers’ question: what’s in this for me?

Social media tools may have an answer. We share our observations and insights about business problems with a readership (or, viewership) that goes far beyond company walls. If we’re good at sharing we develop a reputation – our small claim to notoriety.  And the measure of our fame?  What’s in this for us is the number of our Facebook friends, YouTube viewers or comments made on a public wiki. Our fame — quantified…

Ten years ago Knowlege Managers were right in talking about sharing for the Greater Good. What they couldn’t have seen, of course, was that social media would allow us to stretch the boundaries of just who that Greater Good included.

KnowledgeBoard, a thoughtful knowledge management hub, describes a new Forrester report in an article with a dismaying title:  “Knowledge workers behind times with collaboration.”

After reporting that collaboration is being held back by poor tools, the Forrester report advises a very cautious approach. Companies should stick to their decade-old standby, email with attachments, for the near future. Web 2.0 adoption (blogs and wikis, mainly) is still very low.

What if the process of jumping to 2.0 was fun? What if it engaged your crew in activities that built capacity even as they entertained? That’s what creating a meaningful video and posting it on YouTube can do. Or puzzling through together whether Twitter is important, and why. And expressing that in a way that the rest of their peers can experience.

Fun is underrated. Besides, sometimes the best way to achieve a goal (say, adoption of some KM software or practices) isn’t the direct route (learn this! use this!). It’s the indirect route of working on something that isn’t on the critical path.

KM is complicated. We’ll be revisiting it often.

Tags:

One of the fun early moments in a DIY project is which tool to use. (If this moment lasts more than an hour or so, the fun can quickly turn to irritation.) Should I use video? Text in a blog post? Something like PowerPoint? A slide show of still images? Unadorned audio? Each has its virtues.

I particularly like screencasts, which are like videos, except the video you capture is limited to what is on your computer screen. The accompanying audio is your voiceover. Here’s a screencast I made about one of the ways that social media apps like Twitter and Facebook are affecting the way we work.

Screencasts are a terrific way to show someone else how to do something on their computer, or to make a point that requires some visual backup. They also avoid some of the complications of video, like how to arrange your hair or what to wear. Or whether anyone wants to see your mug. Screencasts require little expertise and produce useful results.

I created the screencast I linked to above with Jing, a simple, free and elegant tool from TechSmith, the company that makes the all-singing, all-dancing (and $300) screencasting app Camtasia Studio. It’s handy.

Tags:

You’ve heard the term and if you think it sounds a little touchy-feely, consider the following story:

March 2003A day out of home port, the captain of freighter en route from South China to the Philippines radios his shipping office to say 6 of the 13 man crew are sick with fevers and severe coughing.

picture-3

The context of that month, that year, is important. Between the previous November and June of 2003, 744 people – from a total of over 8200 known cases – died of Severe Acute Respiratory Syndrome (SARS). The world watched what was feared to be a global pandemic originating from Guangdong Province. Guangdong was the last port of call for the freighter.

Urgent calls from the shipping company headquarters in Manila connected with an impressive range of experts: Atlanta’s Center for Disease Control, the US Department of Homeland Security, the US State Department, and London’s Tropical Disease Infirmary.

Meanwhile, the ship’s First Mate condition had worsened and the captain was certain he was about to die.

CDC, Epidemiologists at the Infirmary, the US State Department, and the Government of the Philippines agreed – the ship was to stopped, and adjacent shipping lanes were to be quarantined until someone could figure out what was happening.

And then something quite remarkable happened. Almost as an afterthought, the ship’s builders in Northern Ireland had been contacted and in the middle of the Belfast night a junior manager at the shipyard sent out the word “get me anyone, now, at 3 in the morning – employees, friends, neighbors, anyone who worked the docks, who knows anyone who might know _something_ about this 60 year old ship and have them come to our company hall. Now!”

Within an hour there was a conference telephone call between experts from 3 continents – and what must have sounded like a rabble-y crowd at a shipyard in Northern Ireland.

At one point, someone in the Irish crowd made an offhand mention of how hard is was to keep the officer’s quarters clean because the ductwork always got in the way of your mops.

“Ductwork?” repeated the CDC.

The short of it was — in the late 80s, new HVAC regulations came into effect and it was tough to retro-fit the oldest vessels with the new ductwork. At least, hard to do ‘according to plans.’

That hint, made from some anonymous person who remembered some odd little fact from a generation before, was all that was needed. CDC and the London Tropical Disease center made a hypothesis that non-code ductwork was an ideal place to grow deadly spores.

Within two hours, a British Royal Navy Jump-Jet was lowering Haz-Mat equipped sailors down to the deck of the freighter.

No one died.

—————

So?

The point is – a critical problem was attacked by using the smarts of a community that would otherwise never be tapped. In addition to the experts one imagines would be called in, there were friends, and friend of friends, and people with no other qualification for being in the Belfast meeting hall that night other than they knew *something* about the ship.

It was the smart thing for that unheralded junior manager to do. It was a good idea then, and it’s a good idea today.

Using the terms of today, it was a dramatic example of crowdsourcing, a demonstration of how a collection of people can assemble themselves to come up with insight that might not otherwise see the light of day.

In 2003, they used the telephone as the supporting technology platform.

Six years later, we have other tools — but the importance is being able to tap the collective smarts of a lot of people.

We can help your organization learn how.

Tags:

Why DIY?

We’ve spent so many years buying produced media from others. It’s handy. It’s pretty good. Why not continue doing that?

Media now is participatory. It’s social. It’s linked and interwoven. The act of creating and sharing it is the lesson, the gift, the big aha!

You can’t learn that by going through someone else’s nicely produced video show and quizzes.