Let Business Drive Technology

By Edward Cone  |  Posted Tuesday, November 16, 2010 19:11 PM

by Samuel Greengard

Bad things happen when IT departments and top executives get bogged down in technical issues rather than business issues. At some point, everyone's left scratching their heads and pointing fingers at one another about what went wrong and who's responsible as another big investment fails to deliver the anticipated ROI..

Enterprise Architectural Management is one way to keep from ending up with misaligned systems and processes that don't jibe with technology.

IT must do a better job of pulling things together. Consider it one of life's little ironies that it's often necessary to let go in order to gain greater control. Specifically, IT must put technology ownership back in the hands of business owners and let them call the shots.

Enterprise Architectural Management (EAM), which creates standardized processes for keeping interests aligned, is one way to rationalize business/IT strategy. It creates a blueprint for systems based on business requirements while providing a framework for improving communication and interaction.

Consulting firm McKinsey reports that an effective EAM strategy lowers the need for architecture-development labor by as much as 30 percent and reduces implementation times for applications by 50 percent. Click here for a more detailed discussion about EAM.

Essentially, EAM allows an organization to map out a technology framework that creates a sense of business ownership. With it, an organization can design IT systems that are more closely synced with ongoing operational requirements.

Without it, well, you might be stuck with the same old problems.