IT is one of the strategic assets shared throughout the enterprise. This makes IT and its cost structure sensitive to organizational changes in ways that executives may not immediately appreciate. An organizational structure defines the distribution of responsibilities; resources and reporting requirements drive both core transaction and business intelligence requirements.
How you design the organization
There is a general relationship between your organizational structure and the number, complexity, and cost of IT systems. More organizational units often means more applications, particularly when those organizational units arise from acquisitions, are based on geographies, or represent different business models. In each of these cases the need to support ‘unique’ business requirements leads to multiple sets of IT systems and structural cost.
The relationship between organization units and IT structural cost is accretive. The cost structure builds from individual decisions to support organizational specific systems that make sense at the time, particularly in light of go to market/cycle time needs. This leads companies to do what they think is expedient, just build one for me – I am only one unit – then we will be all set.
This is short-term argument without consideration for the long tail that IT bears. These individual decisions set the stage for a future ‘unification’ project that eliminates duplication through a massive systems reconciliation and consolidation effort. Such efforts are expensive, resource intensive and do not necessarily advance the company’s strategy or market position.
When you change the organization structure
A change in an organizational structure requires an IT response and a cost structure. The response is often in terms of the structure of the company’s accounting and reporting information. Change the organization and IT has to create new reports, adjust accounts, change directories, distribution lists, security access and the like. Its low level work, but its expensive and disruptive to the other things that IT has to stop until this work is completed.
A change from a structure based on countries to one based on multi-country regions offers and example. Companies take such a move to save money in executive staff by increasing spans of control. The decision to change the org structure was simple. However, when the CIO presents the bill for implementing the decision it can come as a surprise as the first year organization savings are eaten up by the IT costs to implementation the change.
Like the other drivers of IT cost structure, the implication of organization structure on IT cost surfaces when an organization changes it structure. Until then the cost of the organization is implied in the structure of IT systems, reports, information and the like. The cost to change can be contained through how the company manages its ERP, HR and other systems.
IT is a strategic resource that means that its cost structure is determined by the company’s strategic decisions around customers & markets, products & services, processes and organization structure. Understanding how these decisions set the context for IT’s structural cost raises the visibility of the impact of these decisions rather than leaving IT costs to be a ‘surprise’.
This is the final post in a series. The main post can be found here (link).
Read Complimentary Relevant Research
Top Strategic Predictions for 2019 and Beyond: Practicality Exists Within Instability
Technology-based change is happening continuously, and most organizations struggle to see the change in advance. Continuous change can...
View Relevant Webinars
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.