At some point in time, someone must have spent countless brain cycles planning your organization’s IT architecture before handing the grand plan off to someone else to build it out. Afterwards, it would have been handed out to someone else to maintain it as your computing environment inevitably grew. Best intentions faded in the face of expediency, departmental politics, and general mismanagement somewhere along the line. This eroded what was once a coherent architecture management strategy into an ongoing series of independent, case-by-case decisions about each technical component. Here are some of the ways to know if your organization has strayed from the path and bad IT architecture has taken hold of your organization.
Every business application solves business problems. While solving business problems is good, solving them more than once should be even better. However, that is not actually the case. Yet a lot of companies keep lots of redundant applications around, either because they’ve grown through mergers and acquisitions but aren’t very good at integrating everyone into one business after the papers have been signed or because they overlap but still have a few unique areas they support. The money spent to support all of this redundancy is a pure waste either way.
Architectural impact: Redundant applications drive a need for system interfaces and the number of platforms that must be supported.
Direct business impact: Redundant applications often create the need for manual re-keying by draining IT resources away from value-creating activity and wasting money on software licenses that don’t deliver new functionality to the business.