Creating a demand for knowledge?
“What we want is to see the child in pursuit of knowledge, and not knowledge in pursuit of the child.” – George Bernard Shaw
When Owen Barder spoke to UNICEF earlier this year he said something very intriguing about knowledge and development. His contention was that the biggest problem for aid workers was not that we didn’t have enough knowledge, or that the knowledge we have wasn’t well disseminated, but that aid workers weren’t motivated to use that knowledge in their work. When I look at what we are doing, what people said they want us to do for them, and then what they actually do with what we provide, I’m led to believe that he might be right. We often focus knowledge management work on either i) collecting more knowledge – more lessons, more stories, more research or ii) dissemination – trying to get out what knowledge we have through better promotion and dissemination (see Nick Milton’s 4 roles for the KM team).
But I wonder, if it’s true that many aid workers don’t actually look for or use knowledge more in doing their work – then maybe we need to do more to build the demand for knowledge rather than supporting improved supply. What are some of the reasons why the demand for knowledge might not be what we would expect it to be?
Below I look at some of the reasons people give, three of which can help guide your KM activities, and a fourth which is not what it seems, and a fifth reason people don’t admit at all.
Four main reasons people give for not using knowledge are:
1. The knowledge needed doesn’t exist, or isn’t sufficiently reliable to act upon – to which the answer is of course “more research needed”. But at the same time, this is a poor excuse not to use what knowledge is already out there. Another version of this is “the knowledge we have isn’t relevant”. Here it’s important to listen to what frontline users of knowledge need and try to support them to obtain it. In the longer term some sort of knowledge mapping comparing user needs with what is being provided, is useful here so that you can then also make a plan to address the gaps.
2. The knowledge is too difficult or time consuming to find when you need it – to which the answer appears to be to better organize knowledge to make it easier to find (especially using tools such as knowledge taxonomies, better search, social search, help-desks and communities). Another approach might be give people better skills in searching for the things they need themselves – i.e. personal knowledge management.
3. The knowledge is not in the format to be easily usable – I have a lot of sympathy for this one. Often knowledge products (especially research papers) are not written with the user in mind – in particular they might be overly long, unnecessarily laden with jargon, and lacking in a good summary of the key points. Packaging knowledge to met the needs of users – both so they find it interesting and readable in the first place, and then easy to navigate and act upon when it is needed – are important skills of the good knowledge manager. Getting feedback from users, and also asking and observing how they actually use knowledge is key.
4. Not enough time to read – This is the one answer that is not what it first appears. Of course we are all busy, trying to meet lots of competing demands, and identifying knowledge needs, filling them and then acting on them are time consuming. BUT if knowledge is important to doing the project well, then why is there not time? The underlying reason is not simply that there is not enough time, but rather than knowledge as an input to the project is not being prioritized.
There is an opportunity cost to the time taken to seeking and using knowledge which needs to be weighed up against other activities and if knowledge doesn’t make enough of a difference in the outcome compared to the time spent on other activities – then perhaps it’s not a problem. BUT I believe the equation in many project managers’ minds is not about outcomes as much as it is about incentives and risks. If you are an aid project manager under multiple pressures, then you will most likely respond to those which give you greatest obvious gain (the “low hanging fruit”), or which you need to mitigate to avoid the greatest risk.
In the world of frequent programe audits, donor reports, and complex planning and reporting procedures, possibly working in a country which has hmmm “governance issues” then some of the biggest risks are a bad audit, a bad media story or an unhappy donor. And if your knowledge tells you that to really get the impact you need, you have to rock the boat a little in country then your next risk is unhappy government counterparts (and in the worst case scenario a one-way plane ticket).
The funding and budgetary systems of aid organizations also hamper use of knowledge. There is intense pressure to spend money within fixed, often annual deadlines – and performance is often measured by “implementation rates”. It’s easier to spend the money if you don’t take the time to look for new knowledge, or try to do things you haven’t done before which are inevitably harder to budget accurately for and harder to get started or run without setbacks.
As a country office manager you are much more likely to get in trouble for not having our reports in on time, not spending your budget, sloppy administration, or getting into trouble with the government than you are for not using the best available knowledge to run your programmes – especially if the bet knowledge is telling you that you need to change the way you are doing things away from the programme you know how to run well which your counterparts are comfortable with. Especially when changing your programme might make it a bit harder to get your reports in on time, or make it more likely someone will criticize what you are doing in the media.
The answer to this challenge is a little more difficult than the others, and can really only be addressed by leadership. At an organizational level by making it clear that knowledge leadership is one of the benchmarks against which organizational performance and individual performance will be assessed, and putting in systems to make this a reality. By personal leadership – through top management walking the talk by holding the organization to account in reality, as well as modelling the types of behaviours they demand from others. By managers down the chain of command, but especially by country directors to hold themselves and their office accountable for using knowledge – and by making sensible trade offs between efficiency (spending your budget on time, filling out reports, keeping partners happy) and effectiveness (using the best available knowledge in your programmes to get the best possible outcomes – even when this takes time). It would also help if donors and beneficiaries were tougher on aid agencies to insist that they use the best available knowledge in their work.
The fifth reason why people don’t use knowledge, the one they won’t readily admit is the “not invented here” syndrome. This is where people prefer to find the solution themselves, rather than looking at and adapting what others have already done. This could be out of a sense of competition between rival individuals or organizations, or of overconfidence in one’s own knowledge and lack of confidence in others. It might be the sense of wanting to make one’s own mark. There are techniques that can be used to help address this – arguing the value of not reinventing the wheel every time might help, but since the reasons for “not invented here” are largely non-rational, a resort to rational argument is not likely to be that persuasive. Instead you can try peer-pressure methods to make learning and sharing more acceptable than not such as Collison and Parcell’s “steal with pride” award for copying the ideas of others.
But as with “I don’t have the time”, the real remedy to “Not invented here” is leadership – it needs to become an unacceptable practice in the organization based on the expectations and good example set by management.
So what is my conclusion with this? Demand for knowledge is at least as important as supply. If you want to stimulate demand, then you need to listen to users and find out and respond to what they need, and you also need to remove the barriers that exist to them using knowledge, some of which are KM related some of which are not. But lastly you need to pay attention to leadership. If your leadership doesn’t place value on the use of knowledge, model this by using knowledge themselves and make it clear that they will hold others accountable to do the same, then how can you expect your employees to do the same.