6 potential KM implementation approaches

There are a number of strategic approaches that you can apply when implementing Knowledge Management. All have their failings – we recommend a combination of two of them. 

There are many and varied ways to introduce KM to a company, and a lot of these fail. The main 6 strategies are listed below, with their arguments for and against; probably the worst approach (and one of the most commonly applied) is number 5.

Strategic Approach
What is it
Arguments for
Arguments against
  1. Grass-roots revolution (Guerilla strategy)
Knowledge Management starts low in the organisation, without management support An attractive concept; that people do KM because they recognise its importance.
Unlikely to work when KM is up against urgent work, and management deprioritise KM efforts. Multiple diverse KM approaches are likely to emerge. Often fails to reach the tipping point. Can be used to generate evidence to gain senior support in order to kick off a different strategic approach.
  1. Management directive (top down)
Management tell people to do Knowledge Management

    Quick. May appeal to autocratic managers.
    May create a “tick in the box” ethic. Multiple diverse KM approaches are likely as each unit guesses what the managers want. Will stop as soon as management changes.
    1. Opportunistic
    KM is introduced by looking for business issues which the KM team will help address.

      A low energy approach – go where the appeal is. KM focused on problem solving. This is a good approach to identifying KM Pilots (see approach 6).
      KM team can be rapidly swamped with some KM activities, while other components of the KM system are not addressed. KM continues to be “done” by the KM team rather than being embedded in the business.
      1. Move the whole business at once
      Design a KM framework and roll it out to the entire organisation
      Fast. An approach often advocated by large consultancies.
      There is no reliable “one size fits all” KM approach, and if you get it wrong you get it wrong for everyone. Risky one-shot approach, akin to the IT “Waterfall” methodology. 
      1. Modular roll out 
      Roll out components of the framework one by one (eg CoPs, search engine, etc)

        Allows testing of each component of the KM system
        Individual KM components are unlikely to deliver value on their own. The organization will need to take the value proposition on faith until roll-out is complete. One exception here is communities of practice, which deliver enough value as a standalone component to be a good place to start. Starting with technology modules on the other hand is usually a recipe for failure.
        1. Trials and pilots
        Pilot an entire (MVP) KM Framework  in one or more business areas. Review, improve, repeat.

          Secure, robust, allows advancement by discrete steps and decisions. Akin to the IT “Agile” methodology. 
          Slow. Management may become impatient. Risk of being scuppered by organisational changes, unless you deliver Opportunistic quick wins as well.

          Our recommendation, for almost all clients, is a two-pronged strategy of piloting and trials, plus opportunistic quick wins (a combination of numbers 3 and 6).

          For more guidance on KM strategy and implementation, contact us, or get my strategy book or implementation book.

          View Original Source (nickmilton.com) Here.

          The benefits and limitations of KM change and maturity models

          This is a reprise and rewrite of a post from 5 years ago about KM change models vs KM maturity models. AKA “why KM change is more like spread of a forest fire than the growth of a tree”.

          Photo from the US National Parks Service

          The use of a maturity model allows an organization to have its methods and processes assessed according to management best practice, against a clear set of external benchmarks. Maturity is indicated by the award of a particular “Maturity Level”. The majority of KM maturity models (and ours is no exception) have a series of descriptors of various levels of KM maturity, and the implication is than an organisation can progress from one level to the next in a smooth maturation process.

          The analogy, if you like, is that of a tree. As a tree matures, it passes from a seedling to a sapling to a mature tree, but this is a continuous progression. You can describe, using metrics such as the number of branches, size of trunk, number of fruit, where the tree is on its maturation journey. If you won an orchard, you can describe the average maturation level of the trees as (for example) 2.5 on the maturation scale.

          Knowledge Management is more like a forest fire than a tree.


          A forest fire does not mature slowly. It catches in one small place, then sweeps across the landscape.  In a forest fire, change is not top-down nor bottom-up, but side to side (see my blog post http://www.nickmilton.com/2019/07/km-change-is-not-top-down-or-bottom-up.html for more detyails. A forest fire is not a maturation process, it is a phase-change, from unlit to lit. There are various measures of readiness for forest fires – they can be enabled by hot weather, strong winds and a build-up of combustible material, or disables by fire-breaks and rain – but it still is not a process of maturation.

          I am aware as I write this that a forest fire is also a highly dangerous life- and property-threatening phenomenon and a lethal consequence of global warming. If you find this metaphor too negative, please use another, such as kindling a bonfire, or adoption of a virally-marketed product.

          Knowledge Management is a forest fire rather than a tree, because implementing KM is a culture change process. It involves changing hearts and minds, and hearts and minds are changed one at a time. We have all seen the moment when a heart/mind changes and someone “gets lit”. It’s that lightbulb moment, like “catching fire”. There is no maturation for a process, only the question “has it caught fire”. Once it has, the question becomes “how much is burning”.

          I describe here a change model for hearts and minds which you can apply to your key stakeholders, that takes them up to a commitment threshold, beyond which KM can be adopted. Below this threshold they are unlit kindling. Above this threshold they are alight.

          KM then works only if all the conditions are sufficiently right to change the hearts and minds. Once the conditions are right, you light the KM fire in a small part of the organisation (a KM pilot), and once this is burning, adjacent areas will also catch fire, until finally the whole area has caught the KM habit.

          That’s the change model – what’s the problem with maturity models?

          Maturity models are popular, and give the organisation a chance to compare themselves against a standard, and to identify room for improvement. This can be a useful check, but maturity models have a number of drawbacks (for a deeper discussion, see chapter 27 in the new edition of the Knowledge Manager’s Handbook).

          • The first is that the model may have gaps or be based on inaccurate assumptions. There are many maturity models, for example, which ignore the issue of governance, and others that include content as a key component (thereby assuming that Knowledge Management is basically Content Management). Choose your model wisely, or (better) use more than one.
          • Most maturity models make assumptions about the sequence in which things have to happen, and these assumptions do not hold true universally. 
          • I large and complex organizations, where the organizational landscape is heterogeneous, a maturity model tends to gloss over or average out significant differences in portions of the landscape, removing them from visibility and opportunity for action. The maturity model may say “the forest is cool” when in fact the fire is already blazing somewhere local.
          • Finally, as discussed above, KM implementation is not one of gradual maturation across the organization at large, but of spreading the adoption of a new paradigm, and thus the idea that the organisation matures in a stepwise process is inappropriate.

          Take Leadership, for example.

          Senior management support is the biggest enabler (and lack of senior management support is the biggest barrier) to KM. Leadership is vital. Imagine a leadership scale from 0 to 4. Imagine you have moved leadership from level 1 to level 2. Is this progress?  If level 4 is “whole–hearted support from senior management”, what is level 2? Half-hearted support? That’s as bad as no support at all. Until you get to level 4, you don’t have what you need for sustained KM.

          Rather then trying to move the whole organisation to level 2, why not find the one leader who you can help reach level 4? Leave  the rest at level 1 for the moment, and find the early adopter. Gain their whole-hearted support to pilot Knowledge Management in their part of the business, deliver success, and use this to change the next Heart and the next Mind.

          The indicator of progress is therefore not the average level of KM leadership maturity, but the presence or absence of the “first sponsor” in the organisation.

          What is the conclusion regarding maturity models?

          For all these reasons, maturity models are much better used:

          (a) not for assessment and objective benchmarking, but as part of an internally driven diagnostic and planning mechanism along with a lot of independently gathered data, where the question is not “how mature are we against external assumptions?” but “what can this external model suggest to us about our strengths and weaknesses, and which of these areas should we prioritise based on known needs?”; or  

          (b) in homogeneous, well defined contexts such as communities of practice, knowledge-base development, or expertise transfer, where there are specific, well-known good practices and reliable precursors that hold true in most cases.

          In Knoco, we actually do offer a maturity model, which we offer as a free online survey (choose Maturity Survey in the box at the top of the page). It is of some use, but treat it with caution for all the reasons mentioned above.

          In addition we suggest you measure a number of other things;

          The real message behind all of this is that KM is a change program, and needs to be measured using change models.

          KM does not mature like a tree; it catches hold like a flame, and that is how it should be measured.

          View Original Source (nickmilton.com) Here.

          Engaging leaders through a KM "proof of concept" demonstration at De Beers

          The story here is taken from the book “Performance through Learning”, and tells of a crucial “proof of concept” exercise at De Beers, the global diamond company, which was instrumental in demonstrating the value of Knowledge Management to senior management, and gaining their support and buy-in.

          De Beers Headquarters, Johannesburg;
          Image from wikimedia commons

           One of the earliest stages of the De Beers Knowledge Management strategy was to try some simple KM processes on some of the key activities or projects within the organization; to see if they worked, to see if they generated value, to come up with some early wins, and to create some success stories which could be used for marketing. 

          Ian Corbett, the De Beers Knowledge Management lead, had already identified one or two possibilities, and more had come up during the strategy workshop. There was one very interesting and challenging possibility though, which would be a real test of the power of Knowledge Management; the !Gariep project. 

           !Gariep had been a blue-sky technology project for De Beers Marine. The De Beers Marine team had planned to build a piece of mining technology beyond anything that currently existed. The project had been an ambitious challenge, and many many learnings had been generated; so many learnings that the organisation had been unsure how to harvest them for reuse. Some of the key players were still in the organisation, others had left. 

          Ian saw the possibility of using the Retrospect process as a powerful and non-confrontational way of harnessing some of that knowledge. 

           The !Gariep retrospect took place over two days in Cape Town, involving 25 members of the project team, with up to four years history with the project. We divided the project into four stages, and spent half a day on each stage. With the benefit of hindsight, we can see that we invited too many managers and not enough “workers” to the retrospect, because many of the most valuable insights came from some of the more junior members of the project team. 

           However some very interesting and powerful lessons were captured, and we took the opportunity to record some video advice from the participants, as well as some feedback on the retrospect process itself. Although the lessons from !Gariep were extremely valuable, and have already been carried forward to future projects to great effect, those video clips were an even more powerful demonstration of the value of Knowledge Management. 

           Shortly after the retrospect had been completed, Ian attended a meeting of the senior management team of the De Beers group to talk to them about KM. He had recorded one of the engineers at the retrospect, a young credible and eloquent contributor with some excellent knowledge and advice to offer, and he embedded the video in his presentations. 

          This was the turning point for some of the senior managers; it transformed the whole presentation and got them on the edge of their seats. It was a real-life, highly relevant demonstration of what KM within the De Beers context, and from a complex and high-profile project as well. And then, when the senior managers asked “and how did the participants feel about the Retrospect process?” Ian was able to show them a second video clip of enthusiastic feedback.

          Turning the “proof of concept” into high level support

          Ian later reported the following;

          “The embedded video was the best way to market how powerful this approach is. I recorded one of the engineers talking. He is young, credible and eloquent, and I put his video in a presentation for the senior management team. I gave the talks, and I showed Steve, and it transformed the presentation and got people on the edge of their seat. This was the turning point for the Director of operations, who became the high-level sponsor for Knowledge Management in De Beers”

          This approach for engaging key leaders can be replicated by any courageous knowledge manager.

          • Find a big business issues
          • Apply Knowledge Management as a “proof of concept” exercise to solve, address, or learn from that issue
          • Ask the people involved in the KM exercise to tell the story, in their own words, on video
          • Use that video to engage your senior managers

          View Original Source (nickmilton.com) Here.

          10 signs your KM strategy is in trouble

          In a post from 2009 (no longer available) Lucas McDonnell provided 6 signs that your Knowledge Management strategy could be in trouble. I have added 4 more.

          Image from wikimedia commons

          Lucas’ 6 signs are as follows, with my comments in brackets, and then I add a few more trouble signs of my own.

          1. People outside your group don’t understand what you’re doing (a failure in communication);

          2. You keep changing vendors/technologies/products (often a symptom that technology alone is not working, which also means that changing technology won’t help);

          3. You keep layering vendors/technologies/products on top of each other (this seems like a “sweetshop” approach to KM, rather than a strategic view of what technology is needed, as modelled by Schlumberger);

          4. You find it difficult to explain what you’re trying to accomplish (because you do not have a business-led strategy);

          5. You’re prescribing organizational change (by which Lucas means that change is prescribed, rather than delivered through solving a series of business problems);

          6. You’re making big promises (I struggle with this one a bit – but Lucas means “don’t overpromise”).

          I think we can add a few more signs to this

          7. All you are focusing on is vendors/technologies/products, rather than on a balanced framework of roles, processes, technologies and governance;

          8. You are  selling KM on its own merits, not on value to the business; 

          9. You still haven’t an case studies of KM adding value; 

          10. Nobody outside your group has started doing KM yet.

          Some of these warning signs (2, 3 and 7) show that you are operating a model where vendors, technologies and products take centre stage. Others that you are not communicating, and in particular not communicating value) (1,4, 8). Than there is a third group, which suggests you are going for a top-down prescribed approach, rather than an agile approach (5, 8, 10).

          The solution to this is simple.

          1. Introduce KM as a holistic framework
          2. Communicate, and sell KM on the value it will bring to the business and the individual
          3. Use an agile approach, deploying proofs of concept and pilots.

          Watch out for these warning signs, and avoid the crash

          View Original Source (nickmilton.com) Here.

          A twin-strategy approach to implementing KM

          Implementing Knowledge Management requires two parallel strategies, like the two prongs of a fork.

          There was a very interesting article by Ron Bascue in the 2011 Fall edition of the US Army KM newsletter (now no longer available online), about a twin-strategy approach to delivering a Knowledge Management strategy.

          Ron makes the point that Knowledge Management needs to be a strategic long term program of change, based on thorough assessment and analysis,  while at the same time people need to be able to see short term progress, see KM in action, and understand the value it brings. As Ron says;

          “Getting to a fully developed KM strategy takes significant time. And while the assessment and strategy development process is going on, the parent organization is moving forward while the clock is ticking on the KM organisation to show its value.”

          So Ron recommends a two-pronged strategy to address this issue.

          “Our approach incorporates two lines of effort; one a strategic development effort and the other focused on providing immediate tangible results – a series of quick wins”.

          Ron recommends Kaizen events as a way to deliver the quick wins, each of which should solve a business problem or improve an internal process. However a number of Knowledge Management processes could be used, depending on the nature of the problem to be solved;

          Ron’s two-pronged approach is also what Knoco recommends.

          We refer to the Quick Wins as “Proof of concept” events; small interventions with a Knowledge Management tool or process during the Strategy Creation phase, just so that people can see KM in action, and realise that “Yes, it can work here. No, it’s not all smoke and mirrors. Now I understand”.

          However even after the strategy is complete, the KM team needs to continue to solve business problems. However rather than small proof of concept exercises, you move on to larger scale Pilot Projects as part of the Implementation program.

          By solving business problems, the KM team continue to show the value, and engage people in the process without requiring them to buy in at strategic level.

          Follow Ron’s advice (and ours) – make pilots and “proofs of concept” part of your twin-strategy Knowledge Management implementation.

          View Original Source (nickmilton.com) Here.

          7 lessons for KM change; case study from the early days of KM at the World Bank

          In a great blog postSeth Kahan shares 7 lessons on KM change programs 

          In the post from 2009, Seth talks about leading KM change at World Bank, and contrasts his first KM initiative (which failed) with his second (which succeeded).

          The first initiative was “was comprised of a few select, world-class thought leaders who drew on a dedicated budget to design and implement a powerful new tool they hoped would revolutionize the way business was done. We met in closed meetings, witnessed remarkable demonstrations, and marveled at the power of the Internet to spread knowledge.”

          In other words, KM was being pushed by a closed group, who were “preaching only to the choir“. Unsurprisingly, nothing came of it.

          The second initiative, with no budget and no resources, “told everybody what we were up to. In fact, we spent a good deal of time in the beginning figuring out how to tell as many people as we could, as fast as possible. We even met regularly with our detractors, as their input was sometimes needed the most”.

          The second initiative was being run as a change program, with communication extending beyond the closed group of supporters, and engaging with everyone.  And within 2 years, it had changed the organisation.

          Seth’s seven lessons for Change

          Seth identifies seven lessons for KM change based on his experience

          1. Communicate so people get it and spread it. As he says though, this is not one-way communication, but a conversation that spreads

          2. Identify and energize your most valuable players.
          These are your supporters, your early adopters, who can be used to drive KM forward.

          3. Understand the territory of change.
          Seth had a method for mapping stakeholder support, and a similar stakeholder mapping will be valuable for you (see here for a possible method).

          4. Accelerate evolution through communities.
          This one, I think, may be specific to the World Bank. Communities of Practice worked well there, because of the large dispersed nature of the work. Smaller co-located organisations may find other ways to introduce and implement Knowledge Management; perhaps through After Action reviews, or focus groups. You need to work within your own Knowledge Management Strategy and Knowledge Management Framework.

          5. Blow through bottlenecks and logjams.
          Seth suggests a “SWAT Team” mentality.  But please don’t bulldoze people!

          6. Create dramatic surges in progress. Seth suggests special events to drive progress. Another way is to create energy around early successes; those Proof of Concept  exercises where Knowledge Management first adds real value to the business.

          7. Keep your focus when change comes fast.
          When KM is successful, it can accelerate alarmingly. Stay cool – it’s all good!

          Contact us for more details on leading change management as part of Knowledge Management implementation

          View Original Source (nickmilton.com) Here.

          Implementing KM through 6 decisions

          Implementing Knowledge Management into an organisation will not happen accidentally. It happens by a deliberate decision. Or rather, it happens by a series of decisions.

          Very few CEOs will wake up one morning and announce that the organisation will now be adopting Knowledge Management. Instead, like any other change, implementation is a series of investigations and decisions, and each decision rests on a basis of necessary evidence.

          The chain of decisions is as follows.

          1. The decision to investigate whether Knowledge Management would be something worth pursuing for your organisation. This is a decision to commission a task force, or some studies to gain some idea of whether KM is something the company needs to invest in. The task force will need to do some investigation, and see whether a business case can be made for KM.

          2. The decision (based on evidence from the task force) that the organization needs improved Knowledge Management, and to proceed to find out how much investment is required. The task force will need to assess the current state of KM in the organisation. If the assessment shows that improvement in KM is needed, then further work is needed to scope out the scale of the implementation, to set the strategy, and to do a first-pass costing of what the implementation exercise might cost.

          3. The decision (based on evidence from the assessment) to set up a KM implementation program, with a full-time team and budget. Once the organisation understands the scope of the KM implementation exercise, they fund a team and get going. At this stage they will have a KM strategy and implementation plan, and can conduct some proof of concept exercises as a trial of KM in the organisation.

          4. The decision (based on the strategy) to pilot KM in high profile areas. If the small scale trials are successful, and KM has not fallen flat on it’s face or run into political road blocks, then the company may decide to scale up, and run some full scale pilots to fully road-test an integrated KM framework. By this time, KM is becoming quite high profile, and quite high cost.

          5. The decision (based on evidence from the pilot) to roll out KM as a required discipline to the whole organisation. The pilots were successful, the value of KM to the business and to the employees is proven, and the integrated KM framework is robust. Now is the decision – not to be taken lightly! – whether to roll out a KM framework to the whole organisation, as a part of the company management framework. This is the point of no return.

          6. Once KM is embedded, the decision to stand down the implementation team and hand over to management within the business. Once roll-out is over, the company has to decide when to stand down the implementation team, and hand responsibility for KM over to a steady state organisation

          Treating KM as a series of incremental decisions has two main benefits.

          • Firstly, it allows incremental investment rather than ‘trust me, it will work out OK’ management. This is sensible prudent decision-making. The investment in each stage will be a little larger than the previous stage – a task force costs less than a team, which costs less than a series of pilots, which costs less than a roll-out campaign. Each incremental increase in cost is built on a decision, which depends on the results of the previous stage, and on how well KM has proven itself. And at any point up until decision 5, the company can change its mind, because it is not fully committed. Beyond step 5 the company is committed to roll-out.
          • And that’s the second advantage. If each decision is made by the right people, based on the right information and the right criteria, then you shouldn’t have to revisit the decisions later. Each decision should be documented, and should stand on its own merits; without assuming a benefit that hasn’t been delivered yet. You shouldn’t have to keep re-justifying, and remaking decisions.

          So who are the right people to make the decisions? They need to be senior, and they need to have authority to spend the money. Decision number 5 – the decision to roll out KM – needs to be made at the highest level. You need the support of the CEO to make a company-wide change like this.

          However by the time it comes to decision 5, you will have a series of successful trials and pilots that demonstrate that KM works in your organisation, and delivers real value.

          View Original Source (nickmilton.com) Here.

          The KM "proof of concept"

          In the early stages of Knowledge Management – even when you are still drafting the Strategy – you may need to deliver a “Proof of Concept” exercise.

          Proof of? by katmeresin
          Proof of?, a photo by katmeresin on Flickr.

          This is a small intervention with a Knowledge Management tool or process, just so that people can see it in action, and to show that “Yes, it can work here. No, it’s not all smoke and mirrors”.

          This is not the same as a full-scale pilot, nor is it part of implementation – it’s a “Look at this” exercise.

          Suitable proofs of concept might include the following;

          A retrospect on a tricky (or successful) project. For one of the companies we have worked with this was a project that had gone disastrously wrong, and they effectively said to us “if you can get learning from this project, then we will believe what you say about Knowledge Management. We did, and they did.  

          A Peer Assist for a high profile project. This  has been the proof of concept for many companies – a straightforward demonstration that valuable knowledge can be shared between projects teams, and can make a positive impact to project plans.  

          A Knowledge Exchange on a key topic. For another organisation, the proof of concept was getting experts together from all over the world to build company Best Practice on bidding and winning PFI contracts. 

          A Knowledge Asset on a key topic. For a third company, who was going through a series of mergers, this was a Knowledge Asset to summarise “what we have learned about mergers.” 

          A Community of Practice launch. One organisation was seeking to develop knowledge sharing behaviours, and a successful community launch gave them the evidence they needed to move forward 

          A retention interview from a departing expert. This has been the proof of concept for many a Retention strategy. Management want to see what is possible, and they want to see the output, in order to prove that retention can generate valuable output.

          In each case, you should seek to create two things from the Proof of Concept.

          The first is some valuable knowledge, either exchanged between people, or captured as lessons, guidance, tips and hints, or FAQs

          The second is stories, or feedback from the people involved, saying “Hey, we tried this knowledge management thing, it was great, it was not difficult, and it created real value”.

          It is through these stories that the concept is “proven”

          View Original Source (nickmilton.com) Here.

          Why do so many KM implementations not learn from the past?

          Why is it that so many KM implementations never seem to learn the lessons of the past?

          George Santayana quotes
          George Santayana quote by Mel_DJ on Flickr

          We know by now what makes KM work. We know the 7 secrets of success for KM, and the 7 most common reasons for failure. We know the principles, we know which KM strategies succeed and which ones fail.

          So why is it a sad fact that so many KM implementations continue to fail?

          Here are some potential reasons why this happens

          1. People who own KM initiatives are human beings, and as prone as other human beings to rush in without “learning before”. So they reinvent the wheel yet again. That’s why KM is needed in the first place – to influence people to value and to access and ro reuse knowledge, because this is not natural human behaviour; not even for the KM implementors.
          1. People are prone to the common fallacy that “we are different – the lessons of the past do not apply to us” (the “we are different” fallacy is one of the 5 most common objections that you have to face as a KMer). Sometimes this is expressed as “people these days (Gen Y, Gen Z, whatever) are different – the lessons of the past will not apply to them”.  Still a fallacy I am afraid, though one that KMers are prone to as much as anyone else.
          1. KM is simple, but difficult. It is very tempting to go for a mixture of an easy option and wishful thinking, though the easy option will fail.  The illusion of knowledge is one that applies to all humans.
          1. People will offer you miracle solutions – usually technology solutions. “Buy our software, and knowledge will manage itself”. In 20 years of knowledge management, technology has never been the solution (though it has always been part of the solution – about 25% of the framework is technology).  Believing that it will save you this time, is wishful thinking again.
          1. There is a lot of pressures from management to do KM on the cheap, quickly. and with minimal disruption. Unfortunately KM requires investment, it requires time, and (being a change process) causes disruption. You can fail quickly cheaply and non-disruptively, but you can’t succeed. It’s your job, as a KMer, to show management the investment of time and money that will be needed, and the value that KM will deliver in return. Be strong – make your case.
          1. Maybe you don’t know which lessons to trust. There are many dissenting voices in KM, and many people who will tell you many different things. In the past KM has no “authoritative voice”. Now at least we have the ISO Standard 30401:2018; the Management System standard for KM, and part of the reason this standard was written was to help people avoid the pitfalls of the past. If you do nothing else in your new KM program, buy the standard and use it as a guide.

          Those of us who have been working with KM for over a decade (since ’92 in my case, with BP for 7 years, then consulting) have a pretty good idea of how KM implementation can be done, and it is really frustrating seeing people jumping in and repeating the mistakes from the past. The collateral damage is that partial KM implementations, which deliver minor results then fizzle out, devalue KM, and spread a feeling that “KM doesn’t work”

          KM does work, when the KMers learn and apply the lessons from the past. The successes and the failures of past KM programs have generated a wealth of knowledge about the effective application and implementation of Knowledge Management. This is knowledge of huge value to you.

          Use that Knowledge, ladies and gentlemen. Others have striven to generate that knowledge, so that you, if you can avoid the temptations listed above, can guarantee success.

          View Original Source (nickmilton.com) Here.

          KM supports decision making, but which decisions?

          There is a strong argument that the purpose of Knowledge Management is decision support. But which decisions should KM support?

          Peter Senge tells us that Knowledge is the ability to make effective decisions, and the new ISO standard 30401:2018 tells us that knowledge is “human or organizational asset enabling effective decisions and action in context”.

          By giving staff access to knowledge, we allow them to make better decisions, leading to fewer mistakes, less rework, and more efficient and effective organisations.

          So if we want to improve the effectiveness of decision making in our organisations, then we look to KM to help us, and Km can be implemented by targeting a range of decision-related business issues. 

          But which decisions? Any organisation makes a whole range of decisions with a whole range of impact – from small decisions every hour or every day within an impact in the $100 region, such as sales decisions to a customer, up to massive billion-dollar decisions every 10 years, such as major investment decisions, or decisions related to mergers and acquisitions.

          When we start our KM journey, which are the decisions which it is most cost-effective for KM to support?

          Firstly, there is no point in supporting the tiny daily decisions, which have an impact in the $100 dollar range. There are too many of these to be able to handle them easily, and the amount of KM investment is likely to be high. We can tackle these later, through the development of guidance and procedures.

          Secondly, there is no point in trying to support the very rare decisions that happen once a decade or so (decisions about major acquisitions or divestment, or decisions about complete reversals of strategy).  You could do a lot of good KM work on these decisions, but it would be ten years before that knowledge was re-used, so you will not see the immediate impact that you will need in teh early days of KM.

          The ideal place to focus is in the middle – the decisions that are worth millions, and are made on an annual basis. Here the value of KM will be high, and the re-use of the knowledge will be relatively frequent, and a year is about long enough for people to have forgotten the details of the last decision, and to start to reinvent the wheel unless KM helps them.

          These medium value,. medium frequency decisions are a great place to start, as they allow you to deliver significant value through KM in a timescale which is short enough to drive KM forward.

          View Original Source (nickmilton.com) Here.