Ontario Ministry/ Ibm
Ontario Ministry/IBM Case Study
Executive Summary
As stated in the case EDU was divided into divisions, branches and different units, and as a single company employee’s need to feel as one with no boundaries. Implementing a document management system will help them come together as a company rather than a department. Getting people to feel they are part of a company rather than a department will help build trust between all employee’s and departments.
Once implementation is complete, I would anticipate employees will be able to find the information they need more quickly and increase the efficiency of support teams, which will in turn increase customer satisfaction and you should expect to see increased customer satisfaction
Regardless of where the document is the result will be in a unified manner.
Key Assumptions
· After my first recommendation they can implement the other options a year or two down the road. Like communities of practice and an Expert directory. As nowhere does it say they can’t implement another knowledge management solution.
· The document management system’s features and benefits are what I believe should be included in a document management system.
Statement of Issues
The Ontario Ministry of Education (EDU) from my eyes (K. Everest) has a couple of issues but one of the fore running issues is electronic data. Having the same document on more than one computer’s hard drive, or having up to 20 different version of that document should be unwarranted. There is an estimated 3 million different documents on EDU’s computers and if there is up to 20 different version of one document there could realistically be 1 million original documents. Another key issue is knowledge sharing as more than one person could be doing the same research. Having more than one person doing the same research without each other’s knowledge is inefficient and unacceptable business practice. A minor issue is security, having people get access or not get
Executive Summary
As stated in the case EDU was divided into divisions, branches and different units, and as a single company employee’s need to feel as one with no boundaries. Implementing a document management system will help them come together as a company rather than a department. Getting people to feel they are part of a company rather than a department will help build trust between all employee’s and departments.
Once implementation is complete, I would anticipate employees will be able to find the information they need more quickly and increase the efficiency of support teams, which will in turn increase customer satisfaction and you should expect to see increased customer satisfaction
Regardless of where the document is the result will be in a unified manner.
Key Assumptions
· After my first recommendation they can implement the other options a year or two down the road. Like communities of practice and an Expert directory. As nowhere does it say they can’t implement another knowledge management solution.
· The document management system’s features and benefits are what I believe should be included in a document management system.
Statement of Issues
The Ontario Ministry of Education (EDU) from my eyes (K. Everest) has a couple of issues but one of the fore running issues is electronic data. Having the same document on more than one computer’s hard drive, or having up to 20 different version of that document should be unwarranted. There is an estimated 3 million different documents on EDU’s computers and if there is up to 20 different version of one document there could realistically be 1 million original documents. Another key issue is knowledge sharing as more than one person could be doing the same research. Having more than one person doing the same research without each other’s knowledge is inefficient and unacceptable business practice. A minor issue is security, having people get access or not get