|
|
|
|
|
|
|
|
To Be, or Not To Be: Intranet Justification
Paul Chin (post 3/9/2005 Go to page: 1 2 Post-Production Justification An intranet doesn't have a definitive end-point after it's released into the production environment. At this stage, core development and deployment will have been accomplished — it's the content owners turn to take the reins. Depending on the size of the intranet, content management will involve any number of multidisciplinary content owners who feed the system. These content owners represent the various departmental or workgroup sub-sections within the intranet. This may eventually raise a few eyebrows and prompt the inevitable question, "What are these people doing, and why are they doing it?" Post-production intranet content management doesn't get the respect that it deserves; and it's unfortunate that you should even have to justify this. It's simple: unless an intranet is consistently updated with new and relevant content, the system will grow stale and die an early death. The importance of regular content update can't be overstated; it's an essential part of intranet ownership. If an intranet and its content is neglected, you'll have to deal with two very difficult obstacles to overcome:
In order to avoid these pitfalls, you need to ensure that your intranet is never allowed to fall into this state. If it does, the longer you wait to do something about it, the worse the situation will become. Aside from the content, running a long-term intranet will require the addition or upgrade of its technological backbone in order to maximize the system's lifecycle. Technology must be kept current for two reasons:
But remember, there must be reasonable justification for an upgrade in technology and not simply for experimentation with the bleeding edge. The Cost of Intranet Development and Maintenance I don't want to dwell too long on the issue of cost because this isn't an article about ROI. But you need to understand the general costs associated with building and managing an intranet because this issue is unavoidable. The needs of every organization varies and as such an intranet used in support of that organization will also vary widely—in terms of scale, personnel requirements, equipment, software, and security. But generally, the cost of an intranet involves three core areas:
Having a firm understanding of the total cost of your solution will be important when justifying the development and management of a system that requires long term commitment. The Benefits of Committing to an Intranet The most difficult part about trying to justify the existence of an intranet — whether pre- or post-production — is that you're trying to get management to invest hard dollars for mostly soft returns. These soft returns come in the form of improved employee productivity and self-sufficiency, a higher level of inter-departmental collaboration and communication, and easing the process of information gathering and dissemination. Among the many intranet benefits, the most obvious are:
Replacing Hard Copies
Reducing Content Search
Reducing Duplication of Effort
Promoting Employee Self-Sufficiency
Keeping Knowledge Within the Organization Final Thoughts Intranets can't be justified by using financial return as the sole measuring stick. While many of the soft returns I mentioned in this article can lead to financial savings by way of improved employee productivity, they tend to lead to them in an indirect manner. And maybe it's because of an intranet's latent value that we're forced to justify it's existence when other IT systems are accepted as a matter of fact. It's our job, as intranet professionals, to help management see the true worth of an intranet beyond the dollar. They need to understand a properly built and managed intranet has long-term benefits that will affect the company and its culture as a whole. It's not just a matter of how much money it will save or make — and if management doesn't have the foresight to realize this, then perhaps they have missed the whole point.
Go to page: 1 2
|
Intranet Journal's Tutorials |
|
Managing Editor |