adv

9 warning signs of bad IT architecture

9 warning signs of bad IT architectureChances 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.

Collection of point solutions

Everyone wants their work supported by a “best of breed” solution. Define “their work” too narrowly, though, and everyone has to visit so many applications to get their work done that there isn’t enough time to get their work done.

Meanwhile, unless IT spends a lot of time building interfaces to connect all of these point solutions, you’re back to re-keying again.

Architectural impact: Point solutions drive need for system interfaces and the number of platforms that must be supported. Collections of point solutions also often creates need for manual re-keying.

Direct business impact: Collections of point solutions slow down business processes and drive up training costs — in addition to re-keying issues.



Comments