What's wrong with Lessons Learned? Part 4.

Over the past two weeks, we’ve looked at three of the inherent weaknesses of “Lessons Learned” and the way the label is perceived:  Passiveness, Negativity and Ambiguity.We will move onto a more positive note soon, but before we do, I want to introduce one further weakness:  Bad Teachers.

At this point I want to make it clear that I have seen the Diaz/Timberlake/Segel film of the same name, and that they are 92 minutes of my life that I would like to have back! However, the image was too good not to use.

What do I mean by bad teaching?

In the educational sense of the word, a lesson is deliberately crafted and designed in order to teach.  I can say from experience of being married to a teacher, that every hour of teaching she delivers requires another hour to cover preparation, marking and feedback to the learners.

Lessons are carefully formulated to take account of learning styles, levels of capability and connections with other parts of the syllabus. They evaluate understanding, they build on prior knowledge, they include references to further exploration and they have measurable outcomes.

Our bullet point lessons look a bit lame now, don’t they?

“Ah, but we’re not in the business of education”, I hear you say. Well, perhaps we should make education more of our business!

There’s a George Bernard Shaw quote which teachers hate - my wife included.  You’ve probably heard it.

Those who can, do.  Those who can’t, teach.

But there’s a corollary to this, which I’d like to add:

Those who can do, often can’t teach.

And that’s often our problem.

A project team successfully learns something from a project review meeting.  A lot of their learning is internalized, and the “lesson” they write down on that flipchart makes sense to them.

But it doesn’t make sense to the next team who will be using it. Just because I’ve learned something doesn’t make it a lesson for everyone else when I write it down.

Imagine my wife visiting an Egyptology exhibition and giving the brochure to her class on Monday morning whilst announcing “Hey class 4, this is what I learned about the Egyptians over the weekend – why don’t you take a look!”It’s not what she learned that matters, it’s what she teaches.

So how do you prepare a lesson which becomes a good teacher?

  • Think about the customer for the knowledge.  Who will be reading this?  What questions would they have?

  • Consider the context.  In what situations would this lesson be relevant?  Is it specific or general recommendation?  A good practice? Something to bear in mind?  Something to avoid?

  • Provide the back-story. Help the reader to understand the circumstances which gave rise to your experience to help them make sense of what you learned and make a judgement on its applicability in their context.

  • Illustrate the lesson with artifacts, images, documents, quotes, videos, references and links to provide a richness to the learning experience.

  • Don't separate the lesson from it's source. Ensure that the person behind the story behind the lesson is clearly referenced.  Include a photo and full contact details.

  • Show where it fits with other lessons.  Signpost other relevant lessons and content by drawing together related content into a "knowledge asset".

  • Keep it fresh. Revisit the content periodically to ensure that it is still current, relevant, and illustrated with the best examples.

That way, we can be those who can do, can learn and can teach.

Follow @chris_collison

What did Einstein know about Knowledge Management?

Quite a lot, it appears! Here are my top ten favourite "Einstein on KM" quotes, which I have roughly curated into a journey from information to knowledge, through to learning and simplicity, experimentation, failure, curiosity and imagination...

  • Information is not knowledge.
  • The only source of knowledge is experience.
  • Make everything as simple as possible, but not simpler.
  • If you can't explain it simply, you don't understand it well enough.
  • We can't solve problems by using the same kind of thinking we used when we created them.
  • The only thing that interferes with my learning is my education.
  • Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning.
  • Knowledge of what is does not open the door directly to what should be.
  • Anyone who has never made a mistake has never tried anything new.
  • The true sign of intelligence is not knowledge but imagination.

And for any of us who have ever been asked to create an accountant-proof business case for KM, there is always the classic:

  • Not everything that counts can be counted, and not everything that can be counted, counts.

Far better than my quick top ten list is this  infographic (click to enlarge) created by IQMatrix on visual.ly, which does a brilliant job of mind-mapping most of the above quotes, and a number of others.

Albert-Einstein-mindmap-2000px

But one unexpected Einstein quote escaped the infographic - which has nothing to do with knowledge management,  demonstrates his humanity and humour and makes me smile...

Any man who can drive safely while kissing a pretty girl is simply not giving the kiss the attention it deserves.

Genius.

What's wrong with Lessons Learned? Part 3.

In the last few posts we've been exploring what's wrong with the way we position "lessons learned".  In part one, we looked at the passive problem of people's tendency to focus on the lessons rather than the activity of learning.  In part two, we looked at the negative associations of the term 'lessons', and the impact that this can have. In part three, I want to look at the problem of ambiguity.

The label "lessons learned" trips off the tongue easily, but that doesn't mean that everybody hears it in the same way. Learning appears in more than one place on an learning loop, so there is plenty of room here for confusion. It can be an output, an input, or an agent of change. Here is one, very simple question you can ask to check whats going on in your lessons learned process.

Who is learning?

Here are potential three recipients of the learning - let's imagine we give a badge of recognition in each case:

Image
Image

It could be person or team who had the experience, who completed the activity and then reflected upon it.

In this case, learning is an output.

Image
Image

It could be a function or department who learn from a team's experience and make a change to a process, policy, standard or working practice -  thereby reducing the risk or improving the prospects for everyone who follows. In this case, learning is an agent of change to the structural capital of the organisation. It becomes an embedded inheritance for all who follow.

Image
Image

It could be another team about to commence a new activity who are learning from the experience of a previous team. In this case, learning is an input. This input could proactively pushed to another team, or pulled by the new team, through a peer assist, for example.

It's important to recognise that all of of these are valid and desirable outcomes , or there's a danger that we allow learning from lessons to be a slightly self-indulgent team huddle.  Worse still, we focus on building the library of lessons rather than actioning the change that the learning should produce, see my earlier shaggy dog story about selling a BMW.

MAKE award winners ConocoPhillips and Syngenta both recognise the need to lubricate all parts of the learning and sharing cycle with appropriate senior recognition.

ConocoPhillips have their 4G awards:  Give (sharing knowledge), Grab (applying someone else's knowledge), Gather (consolidating knowledge), Guts (sharing learning from failure).

Agri-business Syngenta loved this, and created their own TREE awards along very similar lines:  Transfer, Re-use, Embed and [share a difficult] Experience.

In each case, senior leaders are involved in judging and celebrating the best examples of these essential behaviours, and the teams or individuals concerned receive a physical recognition award.  It's very clear who is learning, who is sharing, what is improving and where the value is - all of which is the best antidote for ambiguity.

Syngenta TREE award
Syngenta TREE award

Downton Abbey, what you know, and what you're known for.

Earlier this month I took my family to visit Highclere Castle in Berkshire.  It is beautiful Victorian Castle set in 1000 acres of parkland, and is home to the Earl and Countess of Carnarvon. It is best known though, for its role in the TV period drama Downton Abbey which has gripped not just the British viewing audience, but audiences around the world, and particularly in the US.  It’s become quite a phenomenon, nominated for four Golden Globes.

Image

As we took the tour of the inside of Highclere Castle, we were expecting to see merchandise and references to the TV series wherever we looked, given the worldwide acclaim for Downton Abbey. “This is the room where Mr Pamuk died…”  “This is the spot where Lord Grantham kissed Jane…” We couldn’t have been more wrong!   It would be quite possible to tour the entire castle and completely miss its starring role in the TV series!  Surely a missed opportunity by the owners, the Earl and Countess of Carnarvon?

What they did have on display in the huge basement was a large Egyptology exhibition which told the story of their great grandfather, Lord Carnarvon who, together with Howard Carter, discovered the tomb of Tutankhamun in 1922.  That momentous discovery in the Valley of the Kings is the real story of Highclere Castle, and we got the feeling that the current Earl and Countess of Carnarvon were a little indignant that the vast majority of visitors to Highclere Castle are only there because of a piece of engaging TV fiction!

It’s a perfect illustration of the difference between “what you know” and “what you are known for”.

Throughout our organisations, there are hundreds and thousands of people who have real stories to tell from their past knowledge, experiences and roles – yet they are only known for their current job title.  How do we enable this past experience and know-how, which often lies as buried as Tutankhamun’s tomb, to be rediscovered?

As knowledge professionals, this should be one of our priorities.

  • One way is to enable the creation of internal profiles which encourage employees to describe the interests and past experiences as well as their current position – and to embed their use in the habits of the workforce. Many organisations do this very well, notably MAKE award winners BG Group and Schlumberger.

  • Another approach, often complimentary, is to draw out the experience of others through a collective response to a business issue for example via a “jam” session.  I was speaking with Deloitte in the UK last week, and they described the success of their “Yamjam” sessions which often surface knowledge from surprising locations.

  • The creation of open networks, and the provision of easy mechanisms for staff to join networks of their interest also makes it easy to mobilise knowledge and experience from wherever it lies.

  • Finally, the use of knowledge cafes, world cafes and other free-flowing conversational processes will set the stage for connections and contributions which might otherwise never surface.

These approaches all enable knowledge and experience from the present (what you are known for) and the past (what you know)  to be shared and reused.

Not only would the fictitious butler Carson approve, but also the very real Earl and Countess of Carnarvon.

Is this Knowledge Management's most effective tool?

There are a lot of KM-related words beginning with the letter C.

Connection, Collection, Collaboration, Curation, Conversation, Communities, Culture…

There’s one which you might not have thought of, but which I think is pretty important.

Here’s a clue.

Department of Coffee and Social Affairs, Leather Lane

That's right, Coffee.  One of knowledge management’s most powerful tools.

Not so sure?  Let me share with you a couple of quotes from middle managers in a smart, knowledgeable organization which can spend over £1bn annually on major programmes and projects.  I was interviewing a range of staff to help them create an Organisational Learning Strategy, and the C-word kept coming up:

"Coffee conversations happen all the time – our networking keeps us alive.  People say we’re a process-driven organization, I just do not agree.  We’re relationship-driven."

"Do people regularly go into a Lessons database  - ”I’m just about to start a project, I wonder what’s there?”.  I can tell you that they absolutely won’t!  They might have a coffee conversation, but the learning won’t come from the document – it’ll come from “Blimey, someone told me you did this before, is there anything you can give me tips on?”

We're talking here about a conversation in an area around the coffee machine or in-company Starbucks, rather than coffee taken back to a desk. So why does a conversation over coffee work where formal KM tools and techniques fail?

  1. It's neutral. It feels like you're not working! 


    Coffee is a social activity.  It's something we would chose to do for enjoyment.  Asking to talk something over with a coffee is a sugar-coated request which most people accept without another thought. Especially if they're not buying.


  2. You get to talk and you get to listen. It's not often you see people balancing coffee on the edge of laptops and communicating with each other through PowerPoint.  Far more common is a straightforward conversation, complete with the eye contact which PowerPoint and flipcharts often rob us of...

  3. It's transparent. Others see you talk. Having a coffee with someone is  a pretty visible way to share knowledge.  Many of our interactions are semi-private email, telephone or instant message exchanges. Whilst that's not a problem as such, an e-mail-only exchange takes away the serendipitous "Oh, I saw you having a coffee with Jean  yesterday, I didn't know you knew her - we used to work together..." connections which might follow.

  4. It makes you pause, and go slow. "Warning, contents may be hot." You can't drink a coffee quickly.  There's a forced slow-down of the exchange and time between sips for the conversation to bounce between the participants.  It prevents "drinking from a fire-hydrant syndrome!"

  5. Others stop and talk whilst you're in the queue. Double serendipity!  Not only might you be seen having the conversation, but it's very common for  one of both of a pair of knowledge-sharers waiting the coffee line to connect with others  whilst they wait. You don't get that in emails!

  6. It's a culture-spanner. Coffee is the second most used product in the world after oil, and it is the world's second most popular drink, after water. That makes it pretty much a universal currency for buying knowledge-sharing time in any country and any culture.

  7. It stimulates your brain. Coffee doesn't just keep you awake, it may literally make you smarter as well. Caffeine's primary mechanism in the brain is blocking the effects of an inhibitory neurotransmitter called Adenosine. By doing this, it actually increases neuronal firing in the brain and the release of other neurotransmitters like dopamine and norepinephrine. Many controlled trials have examined the effects of caffeine on the brain, demonstrating that caffeine can improve mood, reaction time, memory, vigilance and general cognitive function.

  8. It's very cost effective! Set-up costs might extend to some cafe-style tables, but the ongoing operational costs are unlikely to be  a problem.


So there we have it.  The humble, but very effective cup of coffee.

What other KM tool or technique spans all cultures, balances speaking and listening, slows the world down enough for sharing to soak in, encourages serendipity and openness, makes you smarter and more receptive, costs a pittance and doesn't even feel like working?

Mine's a caramel macchiato...

caramel_apple_spice_thumb

Knowledge Management's Fried Egg moments...

Number 20, Fenchurch Street, London has always been a controversial building.  It has become better known as the “Walkie Talkie”, and was rechristened this week as the “Walkie Scorchie”, because the combination of the curved design, mirrored windows and some bright sunlight created a focus of solar energy which was sufficient to melt parts of an expensive Jaguar XJ parked nearby, and in a non-scientific experiment, to fry an egg! Unwittingly, the architect had designed a building which worked as a scaled-down version of the solar furnace in Odeillo, France. I remember visiting this whilst on a childhood holiday, and was blown away by the lumps of melted rock on display.  I applied my sunscreen more carefully for the rest of my vacation.

Anyway, I say the architect unwittingly designed a building, but perhaps that’s being generous, because the same Architect (Rafeel Vinoly) designed the Vdara Hotel on the Las Vegas Strip, 3 years earlier.  The tall, sleek, curved Vdara Hotel, according to the  Las Vegas Review,

…is a thing of beauty.

But the south-facing tower is also a collector and bouncer of sun rays, which -- if you're at the hotel's swimming pool at the wrong time of day and season -- can singe your hair and melt your plastic drink cups and shopping bags.

Hotel pool employees call the phenomenon the "Vdara death ray."

A spokesman for MGM Resorts International, which owns Vdara, said he prefers the term "hot spot" or "solar convergence" to describe it. He went on to say that designers are already working with resort staff to come up with solutions.”

So the same architect has designed two tall, curved, mirrored buildings which have both manifested the same unwelcome side-effect.

Not only that, but the Disney Concert Hall (not designed by Rafael Vinoly) had similar issues back in 2003.

You have to ask yourself, surely lessons learned from the Vdara Hotel should have been applied by the same firm as they designed the Walkie Talkie?  Surely the Death Ray experience would have burned itself into the memory of the firm concerned?

And would it be unreasonable to expect the Architectural profession to be aware of the Disney Concert Hall case, and consequently have prevented the flawed Vdara design sizzling tourists like ants under a magnifying glass?

Is it easier to learn from the failures and flaws of others, of from our own internal failures?  Well, it depends on whether the power of "Not Invented here", disguised as "It'll never happen here", is greater than the professional defensive reasoning and displacement of failure Chris Argyris described in his brilliant HBR paper, “Teaching Smart People How to Learn.” If you haven’t read it, and you work in the field of knowledge management, organizational learning, improvement or in any medium-large consultancy, then please do.  It’s 22 years old but it could have been written yesterday.

Here’s a taster to wet your appetite:

 "Any company that aspires to succeed in the tougher business environment of [today] must first resolve a basic dilemma: success in the marketplace increasingly depends on learning, yet most people don’t know how to learn. What’s more, those members of the organization that many assume to be the best at learning are, in fact, not very good at it. I am talking about the well-educated, high-powered, high-commitment professionals who occupy key leadership positions in the modern corporation.

Most companies not only have tremendous difficulty addressing this learning dilemma; they aren’t even aware that it exists. The reason: they misunderstand what learning is and how to bring it about."

Argyris goes on to distinguish between the single loop learning approach of problem-solving and error correction, and the double-loop learning which addresses how organisations identify, discuss and enact change, and the dynamics, performance measurement systems and behavioural filters which can prevent even the most brilliant (often the most brilliant!) professional from seeing their role in something less than brilliant.

The case of the non-learning professional is not reserved for architects, of course - it's just that their oversights can be so tangible.  The financial sector, energy sector and public sector have all had their own versions of the "walkie scorchie".  It's just that you can't fry eggs on them.

As knowledge and learning professionals, we need to make sure that we're visible, helpful  and active for these fried egg moments.

They are the moments when mistakes are too visible to be missed, and when even defensive reasoning is no defence.   We can help our organisations not just to learn from the specifics of one design error (we can certainly start there, and get our foot in the door), but we also need to have the courage and the influence (and partnership with OD and other functions) to look beneath to the structural and organisational factors which will ultimately determine how many times the organisation gets its fingers burnt.

Oh, and on a related matter, and if you're thinking of buying one of these - be careful which wall you put it on!

Learning on a Rollercoaster

One of my current clients needs to conduct a learning review from a 2-year IT project which, by her own admission, has had its fair share of ups and downs. The project is at its mid-point, so the main customer for the learning is the team itself. They don't have much time to conduct the review (sadly just 90 minutes), so she asked me for some ideas for pre-work  for the team. Sometimes you don't have the luxury of a full day to conduct an exhaustive review, so you have to work with what you have and help the team to quickly connect their hearts and minds to the review process.  It's the heart bit which interests me here.

When we're under time pressure, we tend to focus on the facts, the timeline, the plan, the process, contract, technology, scope and the deviations. Intellectual recall. In fact, most project review documents contain little more than this kind of intellectual recall. It usually takes a bit longer to get a team to talk about how they felt, and to draw out some the more people-oriented learning - let's call that a kind of "emotional recall".

I combined some ideas from Retrospects, After Action Reviews, Baton-passing and Future Backwards (Heaven and Hell) exercises into this approach. Enjoy the ride!

With thanks to Navcon
With thanks to Navcon

Part 1 - the pre-work:

Before the meeting, ask each member of the team to think back over the project timeline and to focus on their emotions at each stage. You can provide them with a template like this, with key dates or milestones marked to give a sense of orientation.

1. Ask them to sketch out their own "emotional rollercoaster", paying attention to the highs and lows.

2. For the high spots, write down what went well, and why you think it went well.

3. Do the same for the low spots. What was difficult, and why do you think that was?

4. How do you think the rollercoaster is most likely to continue?  Draw the continuing journey.  Bring this to the meeting with your notes on the reasons for the highs and lows.

Part 2 - during the meeting.

Sharing the Past and Present.

  • Collectively, in the meeting, create a large version of the rollercoaster timeline on the wall.
  • Each participant draws their journey up to the present day, pausing to describe the lows and highs, and the reasons for these.   A facilitator should probe these reasons using the "5-whys"  technique to get to the underlying reason.
  • For each high and low, ask the group to express the reason as a recommendation - something that someone else should do to repeat the delight, or avoid the despair - or an action which should be taken in order to change a process such that the good practice becomes embedded.
  • Capture these recommendations on post-its and place on the rollercoaster.
  • Repeat for each member of the project team (towards the end, they can "pass" if someone has already identified a high or low. )
  • This should create a shared view of the past, and "how we got to where we are today", with some useful recommendations captured. Consider who you might share these with beyond the team.

Creating the Future together.

  • Now ask each member to sketch how they think the project will go from now to the end date. You will probably get a range of options!
  • Focus on the best projected outcome and ask "based on all we've learned to date, what actions could we take to make this happen, rather than the less positive options?". You can take feedback from the entire group, or get them to discuss in pairs or sub-groups first.
  • Capture these actions (with names!).

Thank you ladies and gentlemen, this is the end of the ride. Please be sure to collect your belongings as you leave and don't forget to check your photo on the way out.

10 options for implementing a KM strategy

Last week I had the pleasure of providing my final virtual webinar for the first of the UN's KM Online blended learning programme.  Geoff Parcell and I have taken turns over the past 6 weeks.  Last week the focus was on KM Strategy and Implementation, and we had an excellent interactive discussion about different options for implementation.Here's a shot of our discussion in action...

So with particular thanks to Eric, Harald, Svetlana and Miguel who added some great ideas  - here are ten different options for KM Strategy implementation.

1. Top Down, Big Bang.

This is the traditional "someone at the top has said this needs to happen" approach, usually accompanied by a cascade, a change initiative, communications and engagement plan, brown-bag presentations, training programmes, mugs and mouse mats. We've all seen these initiatives in action - and in some organisations they can be the only way to get people's attention.  The challenge, of course is to find ways to keep people's attention -  particularly when the board or senior sponsors have moved onto their next big bang.  You might consider setting up a programme board with some of the senior players, which will keep them collectively on-the-hook for your programme.  It's much more difficult for the whole group to shift their energy away than it is for a single sponsor to become distracted by the next big idea.

So it's the challenge of sustainability, which leads us neatly to the second approach - Top Down, Bottom Up.

2. Top Down, Bottom Up

This approach is a sophistication of the Big Bang approach, using the same level of visible senior support to send a clear message across the organisation. The critical difference is that there is a deliberate effort to harness the energy and passion of workers at the front line, and to involve them in the programme, perhaps as group of advisors or a community of practice. These people are key in helping to translate the messages from the top and set them in the right context locally.  BP had a two-year programme with a team of 10 with a brief to define and demonstrate the value of KM.  But it was KM Community of practice - around 200 enthusiasts who recognised the value that it brought to their day-to-day roles - this was the group who helped KM to be more sustainable.  They were also an excellent source of anecdotes and credible stories of where KM had made a difference at the sharp-end.

3. Slipstream.

In most organisations, you can guarantee that there will be a number of organisational initiatives in flight at any one time.  Rather than wait for a gap in the traffic which will never come, or to launch a competing campaign to capture the attention of an already saturated workforce, there is a third way!  Slipstreaming is about working in partnership with other initiatives or "transformation projects" (don't you just love that phrase?), looking for ways in which you can feed of each others' momentum. The beauty of KM is that it's such a broad discipline that it is easy to find ways to complement and support other programmes and functions.  I have seen KM effectively slipstream behind business improvement and Six Sigma projects; operational excellence, new project management methodologies, SharePoint deployments, acquisition integration activities, customer management and asset management initiatives, culture change movements and the roll-out of new corporate values. [You might question whether you can change culture with an initiative, or roll-out values - we'll leave that for a future post - but you get the idea...]

One thing to be wary of, which affects competitive cyclists and athletes who slipstream - is the danger of getting "boxed in".  If you're slipstreaming the roll-out of SharePoint with a view to sharing a broader set of knowledge-sharing behaviours and methods, then watch out that the technology doesn't grab all the headlines and rob you of impact.  It's always best to agree these things up-front as part of the partnership, rather than "pop out" unexpectedly and assume that you can push KM to the forefront!

4. Outside In.

This approach is a little higher risk, but does come with its own in-built parachute. Sometimes things just sound better when they are heard from the outside.   People who would treat an internal newsletter or intranet article with a degree of scepticism will pay attention to  the same story when it appears in a journal or arrives via their RSS feed – or when a friend of customer mentions that it just arrived in their RSS feed.  It’s the power of outside-in.  Geoff Parcell and I found that when we published the first edition of Learning to Fly in 2001, it gave reach, awareness and credibility to the KM programme way beyond anything we could have achieved ourselves.  Rio Tinto experienced a similar unexpected impact when they published their video on Communities of Practice on YouTube.  It just works, and it creates momentum inside the company to fill in any gaps between what is said externally and what happens internally.

And if you do over-reach?  Well, all that publicity should help you to find a soft landing somewhere else!

5. Viral

This is a variant of the pilot approach and usually involves technology.  BT experienced it with the  launch of their BTPedia internal wiki back in 2007, Russian financial services giant Sberbank encountered it with the launch of their ideas management system in 2011, and the roll-out of many micro-blogging environments  like Deloitte's Yammer have taken on a life of their own this year. With a viral approach, you need to be prepared for it to be messy - it's a case of let a thousand flowers bloom, pick the best ones and do the weeding and gardening later.   However, it's hard to imagine "lessons learned", "knowledge retention" or the creation of knowledge products spreading like wildfire.  You'll need to make the most of the extra momentum and have a plan up your sleeve to connect the parts of KM which spread virally with the other techniques and methods which require more effort to adopt.

6. Stealth

Sometimes labels get in the way.

Sometimes  you have to find ways to build  up  your organization's capability to manage and share knowledge without them realising what your master plan actually is.  You get smart at making small adjustments to processes, spotting political opportunities and allies, tweaking the configuration of information-sharing platforms and the wording of competency frameworks and values;  encouraging networks and facilitating conversations which improve performance and learning.  After a few years, you'll be able to look back and say to yourself  "you know what, we're pretty good at managing and sharing knowledge. - but you probably won't get a plaudit or bonus - just the satisfaction of having helped to build a knowledge-friendly environment which is probably more sustainable than any managed programme would have achieved.

If you like the sound of that, and can live with the lack of recognition, then perhaps a career as an independent KM consultant awaits you!

7. Copycat

This is more of a tactic than an implementation strategy per se - but it's often successful to point to examples of successful KM from other organisations (competitors and customers are particular impactful) to create some "me too" or "me better" demand.  Find a good example and invite them in to tell their story.  Check whether your board members have non-executive directorships or recent prior experience of other companies.  They might be good ones to pursue! Copycat can work well internally too, encouraging business units to out-do each other in successful knowledge sharing, but make sure that the measures you use to compare and celebrate don't create a new set of competing silos.   ConocoPhillips' '4G' awards (Give, Grab, Gather, Guts) and Syngenta's TREE awards (Transfer, Reuse, Embed, Experience) both focus on giving and receiving - hence they compete to out-share each other - which has to be a good thing!

8. Pilot

A Pilot approach will often take a subset of KM methods and apply them locally - in contrast to the big bang, which usually takes KM as a whole and attempts to apply it globally.  It's all about lighting a number of fires to see what spreads.  A pilot enables you to try the aspects of KM most likely to make a difference quickly, to build credibility locally, and to learn from each implementation.  That could mean launching a community of practice for one part of the organisation whilst closing the learning loop on major projects and working on knowledge retention for retiring experts. Criteria for a successful pilot?

  • capable of showing results (measurable value would be good) within 6 months;

  • strategic;

  • repeatable elsewhere;

  • close to the heart of any key sponsor or stakeholder, and

  • ideally a recognisable part of the organisation (not too esoteric) which will make their story easy to understand.

9. The Buffet Menu

The success of a buffet approach depends on a high level of demand for knowledge. Rather than investing effort in creating an appetite, or a willingness to experiment - this approach works with the demand already present, and provides an array of tools and techniques which the organisation chooses from at will, once their "palate" is sufficiently educated.

The International Olympic Committee is a great example of this.  They set out a veritable smorgasbord of learning processes, observation visits, secondments, extranet platforms, access to experts, databases, distilled recommendations and lessons learned.  A knowledge feast for a future organising committee, who enter the 7-year process with a tremendous appetite for knowledge. On a smaller scale (and let's face it, everything looks small compared to the Olympics!), management consultancies operate their KM programmes using the demand for knowledge which accompanies each new assignment.

Demand-led programmes are more likely to be sustainable - no need to persuade people to change their behaviour - adrenaline drives them to it!

10. Phoenix from the ashes

For a lot of organisations, KM is not a new idea.  For many of them, there have been several historical big bangs, pilots and copycat initiatives. Talk with people about what has happened in the past and learn from it.  Corporate KM started in the mid '90s, so you'll be looking for people with grey hair (working in KM does that to people). Sometimes just having these conversations can rekindle enthusiasm, tinged with nostalgia.  Why didn't we make more of that?  What did we lose momentum then?  Perhaps now the timing is better?  Perhaps now, with a new sponsor, or now that we've addressed that particular barrier? It is quite possible for KM to rise, phoenix-like from the ashes and fly higher than it did before.

So whether you're a viral copycat or a phoenix stealthily approaching a buffet from the outside in, here's ten options to consider, with a little help from the inaugural UN KMOL class of 2013.

How the stiff upper lip is the enemy of knowledge sharing

Here’s a quote from a BBC news article yesterday:

Keep Calm and Stiff Upper Lip

The UK's "stiff upper lip" culture may explain why it lags behind other countries when it comes to beating cancer, say experts.

Researchers, who surveyed nearly 20,000 adults in six high-income countries, said they found embarrassment often stopped Britons visiting the doctor. Respondents in the UK were as aware of cancer symptoms as those in Australia, Canada, Denmark, Norway and Sweden, but more reluctant to seek help, they said.

When you drill down to the underlying reason behind “embarrassment” or “reluctance to ask for help”, you usually end up with “pride”.

This reminds me of one of my “seven deadly syndromes of knowledge-sharing”.   I called it “Real men don’t ask directions”, or “TomTom syndrome”

Imagine the scene: You’re on your way to a dinner party at a friend’s house; you left home a little late, so now you’re in a hurry and the quality of your driving is deteriorating.  Your partner is unsettled and tells you that “she’d prefer to get there in one piece than not at all”.  Now, just to add to the tension, you have a nagging thought that you might have taken a wrong turn. You carry on though, hoping that you’ll happen upon a road-sign or a landmark, but none appear. Finally, your partner breaks the silence and tells you what you already know.  You’re lost!    “No problem”, she says triumphantly pronouncing the solution; “pull over by that man over there and we’ll ask for directions”.

Of course, it’s not exclusively a male problem, but it does seem to be the case that men suffer from this syndrome more than women.  It’s hard to ask for help.

We have all had times when we have that nagging sense that “there might be a better way to do this”, or “perhaps someone else has already figured this one out”.  What stops us from asking around for solutions and ideas for improvement?  Sometimes it’s a sense that we’re supposed to know the answers.

Why would I want to show everyone else that I’m incompetent? That doesn't seem like a route to promotion.  However, once I've solved my problem, I’ll be happy to share my solution.

The truth is, the biggest challenge to organisations who want to get more from what they know, isn't that they have a knowledge sharing problem.  It’s that they have an asking problem.

It’s also true to say that we often turn to technology for help when a conversation would be more timely, more accurate and more helpful – whether that’s with a doctor, a local resident or a knowledgeable colleague who would be only too willing to help.