Wednesday, 16 July 2014

10 reasons for not using knowledge management (KM)

1.      Creativity and innovation are two of our company’s values, so re-inventing the wheel is all the rage around here.
2.      We do KM; we’ve already got [insert name of random IT system here].
3.      We’re so incredibly busy doing things adequately, we simply haven’t got time to learn how to do them better.
4.      Teamwork is one of our values, so having only a few people know how to do stuff forces people to work together.  Clever, huh?
5.      We’re having a re-organisation at the moment.
6.      Finding out what works and what doesn’t might mean asking tricky questions and we might not like the answers so we’re not going to do that.
7.      Things are fine just as they are, thank you.
8.      The HR department are under-valued, so making people redundant, then re-hiring them as contractors when we realise we need the knowledge that went with them, gives them something worthwhile to do.
9.      Internal competition helps us identify the best people/managers/teams; what’s more, learning to keep good practice to themselves ensures that, by the time they’re moving from middle to senior management, our best leaders have this down to a fine art.
10.   We had to learn the hard way and find out for ourselves where everything was and who you needed to speak to and what you needed to know and it didn’t do us any harm.

For a conversation about the value of KM with one of the leading firms of knowledge management consultants, please contact us through the Knoco website.

10 things you need to know about project knowledge management (KM) plans

1.      A project team asks, “What knowledge do we need to manage this project?”
2.      Then, “What are the priority knowledge areas?”
3.      Then, crucially, “Where is that knowledge at the moment?”
4.      If it’s been written down, “Can we get access to it?”
5.      If it hasn’t, “Can we speak to the people who have it?”, “Where are they now?”, “Can they help us?”
6.      And then, “Who is responsible and accountable for KM on this project?”
7.      “What processes will we use to manage our knowledge on this project?”
8.      “What IT are we going to use to help us manage our knowledge on this project?”
9.      “How will we learn on this project?”
10.   “Who else can benefit from what we learn?” “Where are they now?” and so on….

For a conversation about KM plans with one of the leading firms of knowledge management consultants, please contact us through the Knoco website.

Tuesday, 15 July 2014

10 things you need to know about leadership and knowledge management (KM)

1.      Like any initiative, KM needs leadership support.
2.      Leaders can lead by what they say.
3.      Or even better, by what they do.
4.      For example, by resisting the desire to re-invent the wheel.
5.      And, instead, asking, “Who’s done this before?”
6.      “Where are they now?”
7.      “Can they help us?”
8.      Furthermore, honesty and self-criticism don’t harm leaders.
9.      Rather, they improve their standing.
10.   And show others that this is how to behave.

For a conversation about KM leadership and governance with one of the leading firms of knowledge management consultants, please contact us through the Knoco website.

Monday, 14 July 2014

10 things you need to know about Knowledge Management (KM)

1.      KM works best when designed and implemented as a framework.
2.      This means involving people.
3.      Developing processes.
4.      Using IT.
5.      And for leaders to measure, reward and support these efforts.
6.      KM is not an IT system.
7.      It’s not something for a small team to do on its own.
8.      However, you should have KM specialists.
9.      It’s just that everyone can benefit from KM.
10.   So everyone should be involved in KM.

For a conversation about KM frameworks, please contact us through the Knoco website.

Friday, 11 July 2014

10 things you need to know about lessons learned

1.      They can be drawn from both positive and negative experiences.
2.      Lessons can prepare us better next time round, like friendly advice.
3.      However, they can also ensure next time is different, if we use them to change things.
4.      Lessons require us to compare our expectation with what actually happened.
5.      The key is to explore the difference and ask, “Why?”
6.      We keep asking “Why?” until we get to a root cause.
7.      Or there may be a number of contributory factors.
8.      If our recommendations address these, things might change for the better.
9.      We also need to quantify the lessons’ potential impact (i.e. cost, time, safety, morale etc.).
10.   Otherwise all lessons become equally urgent, meaning they’re equally unimportant as well.

For a conversation about lessons learned or advice from the leading firm of knowledge management consultants, visit the Knoco website and get in touch.

Monday, 23 June 2014

Knowledge Assets (or, how to enjoy a pint in the sunshine a little bit quicker)


Edington is a lovely Wiltshire village tucked into the northern edge of Salisbury Plain.  It’s famed for its old and beautiful Priory Church and now has a very popular pub and farm shop, frequented by locals and visitors alike.
Two weeks ago, Edington held its annual summer fair and I helped with some of the setting up on the night before the fair.  There were 5 or 6 marquees of varying sizes that needed to be put up and about 16 of us grappling with them with varying levels of success.  The plan had been to get them erected as soon as possible and then enjoy a pint or two in the warm evening sunshine.
Unfortunately, it soon became clear that few of us were familiar with the marquees and those that were clearly hadn’t struggled with them since the last summer fair.  On asking if anyone really knew what they were doing, I was told, “No, unfortunately the people that really know how to do this are away on holiday.”
‘Long’ and ‘short’ poles differed only by a few centimetres in length and were not marked in any way help us tell which belonged in the ‘spine’ of the marquee (the short ones) and which were the supports (the long!).
Consequently, we had several unsuccessful attempts, with canvas being stretched almost to breaking point and a good old pointless thwack here and there, to try and make things fit in ways for which they weren’t designed – all the time observed by a happy few sitting in the sunshine, supping their drinks and occasionally calling out ‘suggestions’ of dubious relevance.
Still, we got there in the end and, before putting the canvas on, I took a few photos of the marquee frame and its component parts.  My plan is to use the photos in a one-page ‘how to’ guide, which we can laminate and pop into each of the marquee boxes, ready for next year.
Such a document would be a form of 'Knowledge Asset', the purpose of which is to provide the means by which one team or person can transfer their knowledge to many teams or people, separated in time and distance.  At Knoco, we help clients produce Knowledge Assets, which minimise the risk of the critical knowledge being stuck in the heads of one or two vital people who might resign, retire or fall under a bus at any time – or, in our case, simply go away on holiday at an inconvenient moment.
Knowledge Assets help clients to work more safely, more quickly and more cheaply – or, in our case, will help us get to the pub a bit quicker next year.  Nice one.

Friday, 13 June 2014

Life of a lesson #10: post-closure assurance - did we do it right? Any loose ends?


As part of a wider discussion about knowledge management (KM), we’ve recently been looking at the following ten steps in the life of a lesson:


1.       Event takes place – an experience, idea, incident or accident

2.       Analysis and capture – through interview, AAR, workshop, report-writing etc.

3.       Packaging – write-up of lessons

4.       Review for accuracy – editing and improvement by person who identified the lesson

5.       Validation – quality check, ownership assigned and upload into a management system

6.       Review for accountability – periodic checks on progress

7.       Implement recommendations – to avoid/ensure recurrence of bad/good alike

8.       Review for effectiveness – ensure that changes have taken place and/or had desired effect

9.       Closure – lesson status updated but retained in system for reference and to aid analysis

10.    Assurance – as part of risk management, periodic review to ensure closed status remains justified

Last time we examined lesson closure – we’ll now finish this discussion by looking at post-closure assurance.

In any organisation with an embedded lessons learned system, it doesn’t take too long for closed lessons to become so many in number for people to lose track of them.  Therefore it makes sense to develop some form of periodic review, whereby closed lessons are checked to ensure that they have sufficiently robust audit trails (i.e. the comments from those that managed the lesson and implemented its recommendation(s)).  Furthermore, the status of the lesson should also be validated – i.e. do we have sufficient evidence to demonstrate that no further work is required?  Does the issue from which the lesson was originally drawn no longer occur?


If lessons are found to have incomplete audit trails or the implemented changes did not address the original issue sufficiently well, the lesson should be re-opened and managed to completion.  If lessons are found to have been closed correctly, then the audit trail should be updated to show that the assurance review has taken place.

That’s it

I began this look at the different stages in the life of a lesson because I come across many people that persist with the view that lessons are things written down from which others might learn if they can be bothered to read them. 

I’ve run meetings for clients where people express frustration that they’re discussing the same issues again and again and that “we never seem to learn from our lessons”.  Without engaging in discussion with those experiencing this angst, there is the risk that lessons as a concept lose credibility and people don’t bother anymore.


I have set out by views on what we should do to and with lessons to ensure that we learn them; you will have your own views.  Let’s hear them…


For more information on lessons, lessons management systems, knowledge management (KM) and organisational learning, please visit the Knoco website.