Intranet Journal   Earthweb  
Events Jobs Premium Services Media Kit Network Map E-mail Offers Vendor Solutions Webcasts

   Intranet Journal Subjects
Search Earthweb

Privacy Policy



internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

internet commerce
Be a Commerce Partner
















 

[ Home | Discussion Forum | How Do I... | Lotus Notes Intranets | Microsoft SharePoint | Products | Shopping  ]

free news!


Keep Your Intranet Off Life Support, Part 2


Paul Chin
(www.paulchinonline.com)
3/31/2008

Go to page: 1 2  Printer Friendly Version

The best way to curb this is to be responsive to users' needs in as timely a manner as possible -- don't brush them off. It's unrealistic to expect users to wait months for system deficiencies to be fixed. There's only so many times they can hear the words "we're working on it" before they stop believing you and take matters into their own hands.

And if you do notice the early stages of renegade development, try to get those non-IT developers involved in the intranet process. Don't get territorial and simply forbid them from coming up with a solution for their users. This can have the opposite effect. Instead have IT work with them on integrating the application with the intranet.

Last month, I identified some symptoms that can eventually lead to system-threatening ailments including a steady decline in usage, a loss of support from team members, and content atrophy. Here, I continue the discussion by exploring three more ailments that, if not treated properly, can potentially put your intranet on life support.

More From Jupitermedia

Intranet Journal Announces 2008 Product of the Year Winners

10 Open Source Apps for Enterprise Users

Why Ubuntu Linux Tops Debian

IDM Dreamweaver Tutorial

Creating a PHP-Based Content Management System

Top Intranet Trends: Usability, Access, Personalization

The 2008 IT Salary Guide

If you want to comment on these or any other articles you see on Intranet Journal, we'd like to hear from you in our IT Management Forum. Thanks for reading.

- Tom Dunlap, Managing Editor.

FREE IT Management Newsletters

Ailment: Technology or tools become obsolete

Intranet test: Review your intranet TO-DO and future features list and see whether your current technology backbone is limiting your ability to update your system.

Symptoms: You're finding it more and more difficult to implement new features with old technologies and tools -- in some cases it might even be impossible.

Causative factors: "If it ain't broken, don't fix it." This is the mentality taken by everyone from management to intranet section leaders. But sticking with obsolete technologies and tools will eventually render the intranet obsolete as well.

Rx: Updating an intranet to reflect changes in organizational structure or business processes is a no-brainer. But deciding on upgrades to your intranet's technology backbone is a bit trickier -- even a gamble at times.

While it's dangerous to blindly accept bleeding edge technology, failure to adapt to new technological standards and tools can shorten your intranet's lifespan. Systems based on old technology or obsolete proprietary tools can make it increasingly difficult to manage your intranet, implement new features, and find suitable personnel to support the system.

You should stay apprised of all the new technologies and tools in the industry, and trust enough in your IT staff to make the right call. They will know how to separate new technology standards from here today gone tomorrow fads. Although your intranet may not be broken, updating its obsolete technology backbone can greatly increase its life and give you the ability to implement features that might not have been possible in the past.

Time For Your Checkup

No matter how well your intranet is doing right now, it doesn't mean there's nothing you can do to make it better. Allowing something to operate for any length of time without an occasional checkup would be inviting disaster. The key to long intranet life lies not only in your ability to fix problems, but also in your ability to keep them from happening in the first place. Prevention, after all, is the best medicine.

Paul Chin (www.paulchinonline.com) is a freelance writer and journalist. He has previously worked in the aerospace and competitive intelligence industries as a software developer and intranet specialist. He currently writes on a wide range of IT topics, including systems development and security, digital communications and media, content management and web design.

Go to page: 1 2  Printer Friendly Version


Other Resources
from Intranet Journal
  • Intranet Journal Discussion Forum
  • Hasta La Vista, Windows
  • Ten Leading Open Source Innovators
  • from JupiterWeb

    email this page

    Tutorials
    and more at:
    Intranet Journal's Tutorials
    Intranet Journal Favorites

    Creating a PHP-Based Content Management System

    The Spyware Guide

    Introduction to Microsoft SharePoint Portal

    Intranet Journal
    Part of the EarthWeb Network

    Managing Editor
    Intranet Journal

    Tom Dunlap

    EarthWeb Home Page
    Jupitermedia Home Page

    Media Kit




    The Network for Technology Professionals

    Search:

    About Internet.com

    Legal Notices, Licensing, Permissions, Privacy Policy.
    Advertise | Newsletters | E-mail Offers