Knowledge Capture Initiative Summary Report
•Download as PPT, PDF•
0 likes•753 views
An exit presentation to management following a knowledge capture initiative
![[object Object],[object Object],[object Object],[object Object],KMRM Consulting, LLC Continuous Improvement ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Knowledge Capture Initiative Summary Report
Similar to Knowledge Capture Initiative Summary Report (20)
More from Michelle Farabough
More from Michelle Farabough (11)
Recently uploaded
Recently uploaded (20)
Knowledge Capture Initiative Summary Report
- 1. Knowledge Capture Initiative Snapshot KMRM Consulting, LLC
- 16. Department Notebooks KMRM Consulting, LLC
- 20. Wiki Reminders KMRM Consulting, LLC
- 29. Appreciation Luncheon KMRM Consulting, LLC
- 30. KMRM.com KMRM Consulting, LLC
Editor's Notes
- Welcome. Thanks. Masters degree program “Death by powerpoint.” We’ll try not to kill you by powerpoint this morning.
- Graphic shows umbrella of continuous improvement at SCFM. Showing a few of these. Concern over too many initiatives. OUR perspective is that these are all part of a continuous improvement program.
- We were hired for the process capture initiative. Graphic of camera supports Bob’s desire for a snapshot of SCFM. Hard to develop map of where you want to go without knowing where you’re starting from.
- Heard over and over about deleting duplicate and contradictory documents. N-drive audit is important because it is the form of information management you use at SCFM. Looking through it gives us a good snapshot of company. This is a good first step toward Document and Records Management.
- Third objective… Examples are Emergency Action Plan, etc… We’ve worked with each one of you on one of these types of documents. Worked on which are current, which are outdated, which need to be revised. Not exhaustive list, these are just examples.
- As we’ve participated in the various meetings, we heard over and over again people express frustration over the uncertainty of job descriptions and responsibilities. Specifically, as a project moves through the organization, there is often confusion about who is responsible for what, when and how an aspect of the project takes place. There is a need to better identify job roles and responsibilities. Ball gets dropped when people are not clear about who’s responsible for what. Have tried to address some of these concerns by drilling into the kickoff meeting agenda and process flow diagram. Doing this helps us find more clarity in determining the who, what, when and how of each step in selling, designing, manufacturing, and delivering a project.
- Important to format. Not too long ago SCFM was small enough for people to pitch in and help or just talk across the desk if they needed to know something. The increase in numbers and separation by physical space requires a formal way of transferring information between departments and people. With standardization, people know what to expect and where they will find the information they are looking for.
- Might seem that we’re stating the obvious. Masters program debate of paperless. We’re not there yet. We think it is important to have a hard copy. We found it easier to reference several documents at once; also it is a concrete visual of the processes your department is on for. Later in presentation, we are going to deliver into your hands those notebooks.
- Brings us to the electronic deliverable. Affectionately known as SCFM Wiki. We’ll spend mend time later talking specifically about the wiki. Our hope that all within SCFM will use it for access to policies and processes and that it will be useful for findability, usability, etc… We also encourage you to use the wiki as an intranet or for internal communication.
- When Bob hired us for the process capture initiative we approached the project with a particular framework in mind. We wanted to spend just a few moments now helping you understand that framework. In broad terms it’s called Knowledge Management. More bang for your buck. KM new discipline. Academic term; tremendous value for organizations. KM is basically people + process + technology. Michelle to describe each.
- We began the project by focusing on people. This was to get a sense of where everyone was culturally, within the organization. It was important to us to identify the joys and frustrations in order to get flavor and sense of how people within organization feel about organization. The last thing you want is for a consultant to come up with a solution that doesn’t fit the organization. This is the component of Knowledge Management that is the least tangible part of what we did in terms of ROI. It is, however, intrinsic to the end product. People are always an organization’s most valuable asset.
- The 2 nd part of KM is the process people do day in and day out to conduct the everyday business of the organization. In order to help you better understand processes and the way they evolve within an organization, we’ve used the model of the five phases of process management. An article titled: “Scaling the Maturity Levels of Process Management” is a good piece of literature that describes these phases. It can be found by using the search box on the main page of the wiki. Use your own department to see where SCFM falls in these processes. Read through all five. It is important to understand that movement through these phases for an organization is typically NOT linear. We have been primarily focusing on the first three phases. We think this is a helpful tool to help you get your minds get around process management and how it fits into the overall continuous improvement program.
- We’ve been trying to help managers identify the processes for which they are responsible. Processes we’ve identified and that you’ve identified as important. We see processes that occur, but haven’t been formalized. We challenge you to look carefully at the suggested processes that have yet to be formalized (written). Although you may be resistive toward us telling you what processes you still need to write, or how to do things, we ask that you consider how our suggestions will help your department and the way in which your department interacts with other departments. We ask you to continue to identify and refine processes with a vision toward getting out of the reactive phase described in the previous slide and move steadily toward the stable and preventive phases of process management. Again, an intrinsic aspect of Knowledge Management is to facilitate communication between people so that you can better understand one another’s roles and what you can expect from one another. Michelle, Critical to transfer emails that contain agreed-upon policies and processes into a wiki page. This can be part of your continued document and records management efforts.
- Technology never stands alone. The way it is implemented is to first get a sense of where people are, then study processes, and only then to look at possible technological solutions. We didn’t begin our time at SCFM knowing we wanted to implement a wiki. It was simply the best solution to the communications and information findability issues unique to SCFM. In the end it’s only a tool. Ken’s story of brick, board and kitchen pan used as tools.
- Ready for a short break, but first answer any questions. Come back and hand out departmental notebooks and go through them.
- Spreadsheet not printed on purpose. Meant to be a live, working document. On wiki. Your process may not look like the last time you saw it because in the last few weeks, we’ve been spending a lot of time editing for standardization. Explain “work in progress.” This is on style sheet. Look at the process and see what is missing. When complete, replace work in progress with “original.” If you review a process and make change to an “original,” change to the current date, so you always quickly know the last time a process has been revised.
- Mention new word to wiki converter.