Planning Proposal on "Feasibility of developing an intranet" To whom it May Concern: Re: "Feasibility of developing an intranet" (Planning Proposal) Project Description Our company is an internationally-based company that is extremely spread out geographically, and even on an internal level, in its architectural structure. Managers often...
Abstract In this tutorial essay, we are going to tell you everything you need to know about writing research proposals. This step-by-step tutorial will begin by defining what a research proposal is. It will describe the format for a research proposal. We include a template...
Planning Proposal on "Feasibility of developing an intranet" To whom it May Concern: Re: "Feasibility of developing an intranet" (Planning Proposal) Project Description Our company is an internationally-based company that is extremely spread out geographically, and even on an internal level, in its architectural structure. Managers often wish to communicate efficiently and confidentially amongst themselves regarding the performance of other members of the staff. However, at present, this is difficult to accomplish.
Of course the company could build a new physical structure to accommodate needs for better face-to-face connectivity amongst individuals, but another and less expensive potential solution exists, that of the development of an in-house intranet, or online connectivity structure.
Why an intranet? Why not simply make use of the World Wide Web, given currently existing corporate computer structures allow for such connections? The establishment of an intranet would automatically give an additional level of secrecy and protection from viruses and external security threats that mere access through the Internet would not. An intranet has almost all of the quickness of the use of the Internet, once individuals are equipped with system passwords and knowledge of system protocols, but mitigates some of its damaging features without incurring additional costs.
Of course, the virtual form of communication is not as emotionally or logistically beneficial as face-to-face communication.
But when communication in the real world is not possible, the virtual one is an available substitute for a daily 'touching base.' Plan of Action The development of an intranet, in preliminary outline form, will require a three-pronged methodology of 'attack.' Firstly, it will require consultation with the mangers whom will make use of the intranet in greatest numbers, followed by an assessment of their daily needs and also an assessment of their technical prowess, given in both a dialogue format via Q & A.
They could even be given an anonymous a 'pop quiz' regarding how to use the proposed intranet, so the general level of competency of the users could be assessed in a fashion that would not affect their personal job assessment at present. Secondly, the technical designers in-house would be given this informational data, both qualitative and quantitative.
The designers would then come up with a collective plan to meet the needs of the managers, and determine if additional out of house personnel would be needed to be contracted to complete the project. Lastly, the technical staff must determine if training sessions will be required for the non-technical staff members who would use the intranet, to add to the existing necessary skills base of the company managers.
The research plan would thus involve questioning and 'testing' the managers who could use the intranet, questioning the staff whom will design it and determining their personnel and budgeting needs, and develop a form of educational timeline for the mangers who will use the intranet, as well as a timeline for the project.
Thus the scheduling, as such takes this form: (Figure 1) The Problem is: A Lack of Communication Leads to The Solution is: The Development of Company intranet Leads to Another problem Development issues surrounding said intranet A problem that can be solved by questioning, on a one on one basis, the affected managerial staff, the submission of their test answers to determine their competency, and finally an analysis of their skills.
All of this should evolve over a monthly basis, with a week devoted to the discussion and testing of managerial staff, two weeks for discussion with the technical staff regarding development and analysis of the managerial staff personnel's current skills, and then the rest of the time allocated for development of the intranet amongst technical staff, and the human resource department's needs to bring in out-of-house staff, train existing personnel, and conduct needed reshuffling of.
The remaining sections cover Conclusions. Subscribe for $1 to unlock the full paper, plus 130,000+ paper examples and the PaperDue AI writing assistant — all included.
Always verify citation format against your institution's current style guide.