9 warning signs of bad IT architecture

A sound IT architecture keeps your company’s technology strategy humming. From kludges to manual re-keying to redundant apps, these are the telltale indicators of an IT environment on the brink of collapse.

Become An Insider

Sign up now and get FREE access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content. Learn more.

Chances are someone at some point spent countless brain cycles planning your organization’s IT architecture before handing the grand plan off to someone else to build it out, and then to someone else to maintain it as your computing environment inevitably grew. And, chances also are, somewhere along the line, best intentions faded in the face of expediency, departmental politics, and general mismanagement, eroding what was once a coherent architecture management strategy into an ongoing series of independent, case-by-base decisions about each technical component.

How do you know if your organization has strayed from the path? Here are nine warning signs that bad IT architecture has taken hold of your organization.

Manual re-keying

Manual re-keying might not be the biggest cost companies pay from bad architecture, but it’s certainly the most obvious one. Hiring human beings to serve as the interface engine connecting incompatible applications isn’t just expensive; it’s de-humanizing.

Architectural impact: Keying errors result in inconsistent data.

Direct business impact: Manual re-keying drains business resources away from value-creating activity.

To continue reading this article register now

NEW! Download the Fall 2018 digital issue of CIO