Key Mistakes Organizations Make With Intranet IT Architecture

 
 
By Chris Preimesberger  |  Posted 2015-04-06
 
 
 
 
 
 
 
 
 
  • Previous
    1 - Key Mistakes Organizations Make With Intranet IT Architecture
    Next

    Key Mistakes Organizations Make With Intranet IT Architecture

    by Chris Preimesberger
  • Previous
    2 - A Lack of Overall Structure to Start
    Next

    A Lack of Overall Structure to Start

    Intranets that lack structure are ticking time bombs in practically every manner. If your intranet isn't organized, it can easily turn into a muddled mess. Focusing on maintaining organizational structure can often mean the difference between an intranet that is well-suited for taking a company forward and one that simply will not stand the test of time.
  • Previous
    3 - Excessive 'Parent' Pages, Too Many Subcategories
    Next

    Excessive 'Parent' Pages, Too Many Subcategories

    Too many parent pages and subcategories are common on corporate wikis and in software documentation, user guides and online help systems. Intranet administrators should keep parent categories to a minimum to ensure as much clarity as possible. Many people believe that this gives license to outfit parent pages with an endless array of subcategories. This is one of the biggest mistakes that can be made when attempting to keep an intranet running smoothly. Subcategories are no doubt useful, but going overboard will do nothing but cause problems for everyone in your organization.
  • Previous
    4 - Hidden Navigational Tools
    Next

    Hidden Navigational Tools

    As intranets grow in size, they can also become more difficult to navigate. Providing the right navigational tools is crucial in making an intranet easy to maneuver. No one should have to look high and low for buttons and drop-downs that allow for simple recall of content.
  • Previous
    5 - Poor Tagging, Metadata and Labeling
    Next

    Poor Tagging, Metadata and Labeling

    Poor tagging practices can cause confusion. This often results from either a) using terms that are too broad or b) not taking the time to focus on spelling your keywords properly (misspelled tags can easily get lost in the mix).
  • Previous
    6 - Old Content That Lacks Value
    Next

    Old Content That Lacks Value

    An intranet should always be composed of a fair amount of content, but content alone is simply not enough to get the job done. Old content that lacks value won't do you or your social intranet's community members any favors, as it will most likely appear to be watered down if it was written years ago. Since things are constantly in flux, keeping your intranet updated with the best in value-driven, applicable content is essential.
  • Previous
    7 - Department Silos
    Next

    Department Silos

    This is a classic that is still worth talking about. Having separately defined spaces for each of your company departments is fine, but building walls between them is not.
  • Previous
    8 - No Way for Users to Prioritize Content
    Next

    No Way for Users to Prioritize Content

    Users who make everyone members of all spaces defeat the "My Spaces" and "My Account" filtering.
  • Previous
    9 - Permissions That Are Too Restrictive
    Next

    Permissions That Are Too Restrictive

    Controlling information is old school. Once you allow people to choose which groups are most important, give a secondary path for folks to find information that they may need less often but still could save them from having to bother someone else for it. Permissions should not be used as a tool to reduce clutter and information overload; there are better tools for that.
  • Previous
    10 - Duplicating Information for Different Groups
    Next

    Duplicating Information for Different Groups

    This issue comes up often. Customers ask how they can post the same information in two different spaces, almost always indicating a new space is called for—one that represents the union of those two groups. This returns to the notion of tailoring information access and updates based on interests and job function, since it is also possible that not everyone in both those groups could be as interested in that shared content.
 

With networking trends centering on private, public and hybrid clouds for the past few years, the old-school corporate intranet has taken a backseat. An intranet and a private cloud have two key facets in common: They run on central servers somewhere, and they connect employees and contractors so they can get their work done. At that point, however, their functions head in different directions. A private cloud is completely different from an intranet in that it offers a range of advanced capabilities (full stack virtualization, automated provisioning of servers, redundant failover sites and so on) with an application programming interface (API) sitting in front of it for programmatic access to the infrastructure to control resources. Many intranets are still deployed, however, but their infrastructures sometimes are not built as optimally. In this slide show, produced with eWEEK reporting and using industry expertise from Tim Eisenhauer, president of enterprise social network provider Axero Solutions, we point out some common errors to avoid in intranet development.

 
 
 
 
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
Rocket Fuel