In Knoco, we have long experience of facilitating Knowledge Management processes. We understand the principles, processes and ground rules that underlie the group conversations that build, exchange and co-create knowledge. Specific Knowledge Management processes include the following
The After Action Review (AAR) is a short focused meeting, for the team, conducted by the team, lasting half an hour or less. AARs allow to you capture useful operational knowledge which is of immediate short term benefit, and which can be ploughed back into the next shift, or the next day's operation.
A Peer Assist is a meeting, where a project team invites a number of people with knowledge and experience from which the project can benefit. It is one of the easiest and most effective ways of applying knowledge where it is needed.
We employ the Retrospect process; a proven way to bring out the key knowledge and experience developed by a project team, and capture it for future reuse and the benefit of future projects.
A knowledge exchange is a meeting where people from several teams (but usually from within the same community of practice) come together to share knowledge on a key operational topic. These can be very high-powered creative meetings, often pivotal in the development of an organisation's knowledge base.
A knowledge Handover is a meeting at the end of a project, after the project team has identified and captured their lessons learned, where they share and discuss these lessons for the benefit of other projects and other interested parties such as community leaders and subject matter experts.
A Knowledge Market is a meeting to match up people who need learning, with people who can provide their learning. It is a way of connecting people to stimulate knowledge, make new connections, and identify new collaborative relationships. Knowledge Markets are commonly used within Communities of Practice
A Learning History is the knowledge from a project or other piece of work, compiled through individual interviews with the people involved. A Learning History would be used when the team is too big or too busy to schedule a group knowledge capture session.
A knowledge-capture interview is often applied during Knowledge Retention, and involves capturing knowledge from one person, through in-depth knowledge harvesting.
Many of the processes listed above will allow knowledge to be discussed, captured and documented. A Knowledge Asset is a way to make this codified knowledge accessible, usable, and re-used (and re-use is needed if KM is to add value).
Using a proven methodology, we will facilitate a two-day launch agenda for your community, to help them develop their charter, identify their focus areas, agree their roles and behaviors, and build the culture and behaviors needed for success.
A knowledge gap analysis is a half day meeting where the members of a product development project team come together to define the missing knowledge which the team needs to find or create, in order to successfully deliver the project. It is a core component of Knowledge-based Product Development
This is a public, interactive interview with an expert, held in front of an audience of peers and colleagues, in order to share knowledge and stories.