I blogged a few days ago about project KM plans, but these are not the only type of plan you will need to create as part of your Knowledge Management implementation. Here are the four main types.
One of the key components in the strategy is an analysis of “What Knowledge do we most need to Manage? These strategic knowledge areas are identified through discussion at the highest level (CEO if possible).
One of our clients had an excellent discussion with their senior management, while preparing their KM strategy, on this topic of key knowledge, and were given a strong steer to “focus on driving growth in new consumer markets, through knowledge sharing networks”. That decision set their KM strategy, and formed a framework for the next 4 years of KM activity.
- the Knowledge Management strategy
- an assessment andbenchmarking of your current state of KM
- an outline “desired end state” (KM framework)
- a staged, change management approach
- a full analysis of the risks to Knowledge Management delivery
The KM implementation plan maps out the steps from the current state to the end state, guided by the strategy and the assessment. It defines your timeline, and the resource needs.
A KM plan has three main components.
- A Knowledge Register, which defines the key areas of knowledge needed by the project (“key knowledge inputs”), and the assigned actions to make sure this knowledge is accessed. It also defines the key areas of knowledge which the project will be learning about, and which they need to share with the rest of the organisation (“knowledge outputs”), and the actions to make sure this sharing happens.
- A KM Protocol, which defines the system by which knowledge will be managed in the project. It defines the roles and accountabilities, the technologies (such as lessons databases) which will be used, and the processes which will be applied and when they will be applied as part of the project timeline.
- An implementation plan for the project, to make sure the protocol is ready to use. This will require training of staff in the tools and technologies, induction of new staff, registration of staff onto the relevant communities of practice, installation of technology onto people’s desktops, and so on.
The plan is created at a KM Planning work-shop, early in the project, held as part of the set-up activities; about the same time the team are developing their risk management plan, their document management plan, and other front-end planning activities.
Operational KM plansJust as a project KM plan is built into the planning and review framework of a project, an Operational KM plan needs to be built into the operational planning and review framework. This should be done as follows;
- During the annual planning cycle, the operation will agree its annual objectives and budget. The next step will be to create the annual KM plan.
- The KM plan will contain the same components as a project KM, though the key topics in the knowledge register will be set by the new operational objectives. The operational management team will get together for a KM planning workshop, and start with the question – “What do we need to know (or to learn) in order to deliver our operational objectives”?
- The main deadline for the operation to capture new knowledge for other operations will be at the end of the year, when they review performance against objectives, and ask “What were the causes of any deviation from planned performance (either a positive or a negative deviation), and what have we learned from these to improve next year’s performance”? They will also review the application of the KM plan through the year.
Contact Knoco for help with KM planning at all scales