Are Standardization from Enterprise Architecture

Are normalization and innovation in conflict? I have no doubt normalisation and innovation ar in conflict, at least to whatever extent, because standardization (almost by definition) reduces the amount of version of processes or systems simultaneously employ in a company. That is the whole point of standardization. If you reduce the variation allowed in the company, then inescapably you would lose some innovation that could have happened.I think if innovation is viewed in an evolutionary way, mass variation would be created by the local units focused on their individual needs and only the best innovations would e retained and scaled to the rest of the company. If all the companies departments are allowed to develop locally optimal solutions to their problems, certainly some of these variations exit be better (at least for the unit) than by using a standardized software or technologies company-wide.To continue with the evolutionary theme, using any centrally dictated standardiz ed process would reduce the thinkable variation in which could be selected from the environment of each business unit. Think the better to view standardization vs.. Innovation as an inescapable trade-off. Does an enterprise architecture that allows a company to incr tranquillize operational efficiency, ease of integration, reduce development costs, duplication of systems, simplify the acquisition of smart modules, and sometimes vastly reduced aid costs worth some drop in the rate of innovation?I would argue that is absolutely worth it in in most instances. The key is to view this as an optimal trade-off where you stomach retain almost all of the innovation while also increasing standardization. An endeavor Architecture that standardizes the types of technologies used across the many (PH/Dot. Net or Unix/Microsoft) is in the best interest of the company.When you intentionally limit the addressable options of each individual business units options (such as when Timberjack decide d to use Unix and that immediately removed many other eligible companies) you are going to reduce the chance of finding the better solution for every assertable module. Fortunately, most companies can settle on a very good but not perfect solution with any of the market leading platforms without getting a major drop in innovation.Agreeing on a standardized portfolio of technologies and processes, a company can then focus its resources on bringing new functionality to their users without wasting so many resources trying to hold together a Frankincense combination of heaps of systems, technologies and processes together that work perfect in isolation. Ultimately, using more resources on bringing new functionality will increase the total value of the IT department and the rate the department can innovate. Are Standardization from Enterprise Architecture and Innovation in Conflict? By Seasonableness