Showing posts with label problems. Show all posts
Showing posts with label problems. Show all posts

Thursday, 9 March 2017

The last 10 problems that clients have asked us to solve....

At Knoco, we get queries of all sorts, with clients seeking our help in providing knowledge management (KM) solutions to a wide range of problems. 

I thought readers of this blog might be interested in a quick run-down of what these problems are, and how we have helped (or might yet do so).

So, in reverse order, they are:
  • A global consultancy, introducing a technology platform to a Chinese client, want us to provide the KM roles, processes and governance to maximise the benefits available;
  • A global law firm seeks our help in getting teams from different geographical and functional areas to talk to one another; we'll be running a short workshop for them, which will include the Bird Island game;
  • A Chinese manufacturing firm has numerous problems of quality, cost over-runs and also its staff take a long time to become competent and generate value; we're currently helping them to develop a KM business case, to justify the investment needed for the project that will help address these issues;
  • A UK-based defence consultancy is looking to introduce KM but is concerned about employee engagement; we'll be running a workshop (again, with Bird Island) to show the value of KM and help them begin their journey;
  • A Middle Eastern utilities organisation has introduced KM but its take-up is patchy, with isolated examples of good practice; they've asked us to conduct a KM assessment and draft an implementation plan;
  • A global jewellery firm wants to introduce KM but doesn't know how or where to start; we've been asked to design and implement a KM pilot project for them;
  • Another global consultancy has many employees spread far and wide, all of whom seek the advice and support of one or two 'grey beard' experts, which continually diverts these high-value staff members from 'big picture' issues; they've asked us to design and plan a KM pilot project for them;
  • A UK regulator has isolated experts, pockets of good practice and virtually no learning from experience; we've designed a KM framework for them, edited their KM strategy and are about to start KM training;
  • A UK consultancy to the healthcare sector has a low 'bid win rate' and fails either to identify or learn lessons from its bids; we've been asked to look at ways of using KM elements to help it win more business, and learn from each new engagement;
  • A global consultancy to the oil/gas sector is introducing KM; we've conducted a KM assessment, designed a framework and trained their 'KM champions'; we've now been asked to provide ongoing support over the next 12 month.
If any of these sound familiar, or you have a different problem, and think we might be able to help, please contact me direct, or via the Knoco website.

Tuesday, 3 January 2017

Negotiating with a 4-year old (or, how knowledge assets can help us all)

Everyday knowledge assets

Regular readers of this blog will know that a 'knowledge asset' is a term used by those of us working in knowledge management (KM) to describe a tool containing key knowledge on a critical topic.  We create such assets using knowledge capture processes (i.e. Interviews, Retrospects etc.) and then display and structure the knowledge in as 'user-friendly' a way as possible.

The aim of a knowledge asset is not to create a record for posterity or for knowledge-holders to 'dump' everything they know into one place.  Rather, it is aimed at the 'knowledge customer' - i.e. the person who needs certain knowledge in a format that will help them when they need it.

The following are examples of everyday knowledge assets:
  • 'How to' guides
  • Assembly instructions for newly-purchased tools, toys, equipment etc.
  • Recipes
  • Etc.
We can all think of examples of when we have used such resources and found them to be unhelpful.  Often this is because they:
  • Lack sufficient detail
  • Contain only text where images would help, especially on key processes
  • Use terms that don't make sense to us, the user
In short, these issues all have the same root cause - namely, that the guidance material has not been produced with the end-user in mind.  Or at least, has not been proof-read by someone that knows nothing about the topic.  This 'ignorance' is helpful because it reveals any hidden assumptions on the part of either the person with the knowledge or the person creating the asset (they are often not the same person - did you think Gordon Ramsay wrote his own recipes?!).

You will recall that I described the main beneficiary of a knowledge asset as "the person who needs certain knowledge in a format that will help them when they need it".  This is a broad definition and rightly so - knowledge assets can be vast, complex, structured works that take a project team from a bare piece of land to a complete and full-functioning new airport, or they can simply save someone a bit of time and a bit of stress - it depends on the need, the value, and the resources and time available.

Below is a simple example of how a knowledge asset can be used to save a bit of time and quite a lot of stress....

'Pictures paint a thousand words'

Picture the scene - a family getting ready for a day out, to meet far-off relatives:

Mother: "Come and sit down and let me do your hair!  How shall we do it today?  Shall we do the fish-tail plait?"
Daughter (aged 4): "What's that?  Doesn't sound very nice..."
Mother: "It's lovely.  You like it.  It's where the plait has two sides to it that meet in the middle....come and sit down, we haven't got much time!"
Daughter: "What does it look like?"
Mother: "I've just told you.  Sit down!"
Daughter: "Show me...."
Mother: "I can't show you!  I can only do it and then show you in the mirror.  Sit down!"

And so on for far longer than one would want, with everyone getting frustrated....

It was at this point that I had a brainwave (he adds, modestly).  Once my wife had finally negotiated the finishing of
said fish-tail plait, I took a photo of it for future reference.  Since then, each variation of hairstyle (i.e. plaits, pony-tails, bunches etc.) has been photographed such that now, it takes only a few seconds for Mother and Daughter to agree on the style of the day, without the noise and commotion and disagreement that we all suffered before we used this very simple knowledge asset.

Of course, for the analogy to work 100%, we would need to add guidance notes, diagrams, FAQs, videos etc. all of which would help others perform this 'essential task'.

Now, remove hairdressing scenario with a four-year old daughter and replace with any high-pressure situation where details need to be communicated to a workforce lacking fluent English - diagrams, photos and other imagery can help convey methods, finished products and variants thereof.  It's not hard to see how a little bit of effort up-front can make things so much easier further down the line.

For a chat about how knowledge assets can help save you time, money and reduce stress, please contact me direct or via the Knoco website.

Friday, 21 October 2016

8 signs that you're not managing your knowledge


Ever said or heard these phrases at work? 

1. “Why do we keep having to re-learn this?”
2. “How do I know where to find this knowledge?”
3. “Someone must have done this before - but who?”
4. “When that guy left, he took all that knowledge with him.”
5. “It was a complete fluke that I met Kathy – she had just the answer I was looking for!”
6. “I’m sure I heard someone mention that to me the other day, now who was it?”
7. “That went very well – how can we keep doing it like that?”
8. “We made this mistake in our other office as well.”

If so, they're usually a sign that knowledge isn't being managed effectively, if at all.

This means they're also a sign of wasted time, money and effort.

Perhaps they're also a sign of unnecessary risk to our colleagues or vital equipment. 

Can you think of any more?

For a chat about knowledge management (KM), please contact me direct or via the Knoco website.