What Not To Ware: Buying Off-the-Rack Intranet Software
Paul Chin
(www.paulchinonline.com)
7/27/2006
Printer Friendly Version
Why is it mannequins always look so good modeling clothes? What's their secret? They don't have a head, can't stand under their own power, and let's face it, their range of motion is just plain sad. Yet it looks as though the clothes they're wearing were made specifically for them.
Well, the answer's simple: Mannequins are perfectly proportioned and symmetrical -- chiseled more to resemble Greek gods and goddesses than the majority of us -- to best show off the merchandise. But clothes aren't meant to be worn by mannequins; they're meant to be worn by people, in every shape and size. These variables can't always be addressed with a standard small, medium, and large -- at least not without a little bit of alteration.
When it comes to intranets, the question of tailoring from scratch versus buying off-the-rack comes up repeatedly. I'm often asked whether it's really worthwhile to build an in-house intranet with all the software packages floating around nowadays. Is there really a difference between the two? Yes, it's the difference between having something made to measure -- tailored specifically for your body -- as opposed to buying off-the-rack in a standard size that might not fit the way you want it to.
But tailor-made, as appealing as that sounds, isn't always the right decision. It really boils down to the particular needs of your organization and choosing the right tool for the job -- and if that tool already exists, why spend the time and effort remaking what's already available?
Why Companies Buy Off-the-Rack
The decision to buy and implement an intranet software package is sometimes made by choice and sometimes made by consequence. I've always maintained that large-scale corporate projects are a compromise between what you want to do and what you're able to do. Too many factors affect the outcome of such projects: deadlines; financial, human, and technical resources; pre- and post-production support; future plans for expansion. The list goes on and on.
Companies implement off-the-rack intranet software for many reasons. Some of the more common include:
Lack of in-house expertise
One of the main reasons for choosing an off-the-rack intranet solution is because there's simply no one in-house with the technical know-how to build one from scratch. Attempting to do so may force non-techies to a have to overcome a very steep learning curve -- in terms of technology and process. This is often the case with smaller, non-technology based organizations that don't have dedicated IT resources. Software, on the other hand, provides you with a ready-made solution to work off of.
Lack of time
Sometimes, even if you have the technical resources to build an intranet, you might not have the time to do it. IT staff might be tied up in other projects, and it might be financially infeasible to hire new IT staff or consultants. Buying a solution will make a lot more sense if you don't have the luxury of time -- especially if there's already a product on the market that does the majority of what the company requires.
No special requirements
If it fits, wear it. Software makers develop their wares with a standard set of the most commonly used features in today's intranets. So, if you find a product that already does what you need, why reinvent the wheel? Even if it's missing a few things, most software should be flexible enough to allow you to tailor it to your specific needs -- if it doesn't, move along and keep shopping.
Short system lifespan
When an intranet is only needed for a short period of time -- such as for a special project or event -- it doesn't make sense to build a system (unless you have very specific needs that aren't offered by any vendor). These types of systems are usually time sensitive, and the development time required to build something might end up exceeding the actual usage time.
Caveat Emptor: Problems with Intranet Software
With the convenience and plethora of off-the-rack software, it may take a bit of shopping time to find something that fits properly. Before buying anything, you need to be mindful of some off-the-rack pitfalls:
Limited feature set
Ever notice how European manufacturers' clothing runs smaller and fits closer to your body than the relatively loose and boxy fits of North American clothing? That's because every manufacturer has its own definition of what customers are looking for. Organizations' requirements vary and can't always be put into those standard software molds. You're often limited to what you can do by the software's feature set. That's when you'll have to compromise: Find something that fits you as close as possible and then tailor it to your specific needs -- provided the software is flexible enough to accommodate user changes.
Lack of support (or expensive support)
When intranets are built in-house and you have a question, all you have to do is pick up a phone. When you buy a software package, however, technical support may be hard to come by, or the myriad of options -- phone support, e-mail support, IM support, annual subscription, pay-per-call -- can become costly in the long run. It's possible to get third-party support from discussion groups, but you never really know who's on the other end of these forums or what their credibility and experience is. For all you know, it could be representatives of a competing company practicing some shadowy stealth marketing to discredit the software you just implemented.
Software and Vendor Longevity
Software makers and their wares come and go. Basing your intranet on someone else's tool puts you at the mercy of the vendor. If they decide to stop production of the software you're running or go out of business entirely, you'll be left with an obsolete system and no avenues of support.
Intranet Shopping Tips
Off-the-rack software varies from vendor to vendor, each with their own definition of what they believe their target audience will want. You, as a shopper, must filter through all the marketing and find a solution that will work for your organization and user-base. But before you go shopping, you need to follow some simple guidelines:
Take your time and don't settle -- Never rush the shopping process. If, at first, you can't find what you're looking for, keep looking. Don't impulsively buy the first package you see simply to get it over and done with. Settling on something that doesn't quite fit will cause you to regret it later -- especially after deployment. You'll then have to go through this whole process again (users won't be happy about the constant changes either).
Do your homework -- Never trust software makers' marketing and PR material. Dig around for non-partisan third-party reviews, articles, and user feedback. Discussion forums can be useful in locating others who have implemented the software you're evaluating (but as mentioned earlier, take these posts with a grain of salt).
Try before you buy -- You can't adequately evaluate software without actually trying it out. It's like buying shoes over the Internet; it just doesn't work -- not unless you want to walk with a limp. Most software vendors will provide downloadable trial versions of their wares. Take advantage of this opportunity. There's no better way to determine the appropriateness a particular software solution than to get some exposure to it.
Stay away from bloated software -- No need to buy an XL when you're only 5 foot 4! Some software vendors try to pack as many features into their products as possible under the misguided notion that "bigger is better." But top-heavy software will prove to be a millstone for company's who are only looking for a simple solution. You don't want to end up installing and paying for features that will never be used --features that might add undue confusion and complexity for the user community.
Avoid version 1's -- I've always believed that version 1's are really glorified betas. They always seem to have those gotchas that slip by software makers during initial testing stages. These issues are usually discovered through the course of day-to-day use by real life customers, not in the controlled environments of software makers' labs. At the very least, wait for a 1.x version.
Avoid startup software makers -- Choose intranet software from a reputable and established company with a healthy market share. If you implement a solution from a brand-new company that ends up being incapable of competing or surviving in the cutthroat software industry, you'll be stuck with orphaned software, no support, and no possibility for future upgrades and patches.
Stay away from proprietary technology -- Whatever software package you decide on, make sure that the tool doesn't "lock up" your content in non-industry standard technology. If you decide to switch software solutions in the future, content migration might be difficult, if not impossible.
Closing Thoughts
If you're looking for a long-term software solution, you'd better make sure that whatever you decide on is going to last. It's going to be a hassle -- for intranet stakeholders and users -- to have to change software tools every year. It's better to take that extra bit of time to shop around, find something that fits properly, and tailoring it to the specific needs of your organization rather than adopting a "one's just as good as another" attitude. The last thing you want is to find yourself at a haute couture show in a zoot suit.
Paul Chin is an IT consultant and a freelance writer. Previously, Paul worked as an intranet and content management specialist in the aerospace and competitive intelligence industries.
Printer Friendly Version