What will be the role of IT for the organization in the future?
This question has been a constant concern of IT leaders and is more relevant than ever. Cloud transformation, big data, artificial intelligence, machine learning, cybersecurity – the IT universe is in constant flux. According to ISG Research, most companies believe their IT organizations’ performance is critical to the business’s ability to differentiate from competitors.
Figure 1: The significance of IT performance to competitiveness
This result shows the increasing importance of strong IT capabilities in the era of digital transformation. When we imagine the future role of IT in an organization, we need to think about how to organize the IT department and how to facilitate its interaction with the business units.
There are various traditional ways to organize IT.
Figure 2: Three typical ways to organize the IT function
Figure 3: Schematic view for typical ways of organizing IT
Each of the above models has advantages and disadvantages. Deciding which is best for a particular organization can be difficult because different challenges facing IT organizations require different approaches. Table 1 shows some common challenges and typical ways of organizing IT to solve them.
Table 1: Common IT challenges and typical ways of organizing the IT function to address them
IT Challenges |
Typical ways of organizing the IT Function |
Need for innovation |
Decentralized/hybrid |
Transfer of IT responsibilities to business units |
Decentralized |
Technical debt |
Decentralized |
Shadow IT |
Decentralized/hybrid |
No or low standardization |
Centralized |
Cost pressure |
Centralized |
Duplicate services |
Centralized |
Source: ISG
In the past, enterprises have periodically switched between centralized and decentralized IT to increase efficiency and standardization by realizing synergies or foster innovation by providing flexibility to the business units. In time, it became clear that a fully centralized or decentralized IT was not suitable to solve all major challenges IT organizations are currently facing. Therefore, the hybrid model is becoming increasingly present in the market because it combines the positives of centralization and decentralization by orchestrating IT to enable innovation through flexibility without sacrificing synergies through standardization.
Like a pendulum, contemporary businesses should strive to find the "golden middle" to fully utilize their capabilities. Otherwise, they will have to manage the drawbacks of a fully decentralized, centralized or poorly managed hybrid IT unit. Some of the drawbacks of each traditional organization model are described below.
To maximize the benefits of the traditional IT operating model, a combination of centralized and decentralized IT functions is necessary. This is what we refer to as the Hub-and-Spoke IT Operating Model. The goal of the Hub-and-Spoke IT Operating Model is to increase innovation and continuous improvement in an organization without slowing down the operative business or disproportionally increasing the costs.
To achieve a balance between flexibility and standardization that supports digital innovation without compromising cooperation, enterprise IT is coordinated centrally (with a central IT hub) but performed decentrally in the business units (segment IT spoke). This means some capabilities will be operated and delivered centrally (the hub), while others will be distributed (the spokes).
Figure 4: Orchestrated Hub-and-Spoke IT Operating Model
The Hub-and-Spoke IT Operating Model adheres to the following principles:
When new technologies or services are being implemented and operationalized at the enterprise level, specialized skills and expertise are necessary. Ultimately, a CoE should commoditize these skills in the organization, so that related responsibilities can be given to product teams or spokes and the CoE can be dissolved.
A CoE is a centralized team or function that concentrates on the incubation and adoption of solutions by offering leadership/orchestration, standards, best practices, research, training, measurements, skills and expertise. A CoE's main goal is to directly empower capabilities in the business unit IT teams or in the hub. CoEs are especially helpful for subjects that need centralized orchestration, for locations with limited resources and for expediting the adoption of innovative technology. Multiple CoEs (e.g. cloud, agile, automation, etc.) can serve as hubs for knowledge management, ongoing best practice improvement and encouraging reusability of spoke solutions. The duties are carried out through conventional governance, CoP facilitation, team coaching participation and member rotation.
A CoP is a cooperative group of practitioners that is frequently open to anybody who is interested in joining. CoPs are jointly responsible for concentrating on locating, disseminating and putting into action best practices in their own service or feature teams. It is important that clear mandates and responsibilities are set to open the full potential of a Hub-and-Spoke IT Operating Model.
Figure 5: Responsibility split between the IT hub and the spokes
Clear mandates and responsibilities need to be jointly defined between the IT hub and the spokes, as well as publicly and openly communicated and lived as such. While there are some typical responsibilities owned by either the central IT hub or decentralized business units, there are many decisions that must be made to determine the best possible setup for a particular company. Most importantly, the IT hub delivers standardization and supports innovation in a way that is suitable to the IT organization. The setup of these different areas of responsibility is highly specific to a company’s strategy, especially regarding its ways of working, governance and culture.
An exemplary distribution of the responsibilities is shown in the table below:
IT Hub
Enterprise-wide IT strategy is coordinated by a central IT organization led by the CIO.
Responsibilities:
Gray Area
Work that might be managed by the central hub or the decentralized spokes
Responsibilities:
Spokes (Business Unit)
For each distinct business unit or corporate function, a decentralized IT spoke implements solutions in feature and business services teams.
Responsibilities:
We have seen many companies without clear mandates and responsibilities. They run into problems such as multiple divisions or teams developing similar solutions in parallel, unnecessarily complicated processes and creating redundancies. Clearly defining mandates and responsibilities has many advantages and is especially important for a hybrid, interconnected model such as the Hub-and-Spoke Model.
The most important advantages of clearly defining the mandates and responsibilities are:
But how do we achieve these clear mandates and responsibilities?
We do so by setting up a central governing coalition that determines the responsibilities between the hub and spokes and ensures that the right degree of standardization and specialization is chosen for the individual solutions. This will enable digital innovation without sacrificing synergies.
To set it up for success, it should be staffed with representatives from both the IT hub as well as the IT spokes to create a collaborative environment. While the governing coalition is an essential part of the Hub-and-Spoke IT Operating Model, it should still be set up to be as lean as possible. The governing coalition creates the environment to discuss any topics with unclear responsibilities (such as the gray area mentioned above) and align the mandates and responsibilities to resolve them.
Employees are encouraged and enabled to work with an agile mindset and culture, in teams with end-to-end responsibility. As much responsibility as possible is pushed down to the business unit or the central IT hub to cut down on unclear responsibilities that need to be resolved with long governance meetings as part of a governing coalition. This keeps alignment needs to a minimum to maximize time spent working on the solutions. To achieve this, the value proposition of each service needs to be clearly defined and aligned to the business. Common examples where alignment is needed include IT strategy and architecture guidelines and practices for identity, access and cybersecurity.
Both the IT hub and the spokes need a “local” design authority that translates the decisions from the governing coalition into concrete actions for the respective hub / spokes as well as ensuring compliance to the jointly defined policies and standards within their respective organization.
To put it in a nutshell, the Hub-and-Spoke IT Operating Model has the following advantages:
ISG has a vast experience in designing and implementing hub-and-spoke operating models in IT organizations from various industries. Through our proven frameworks, tools and methods, we are able to accelerate the creation and implementation of a future-oriented hub-and-spoke operating model in your IT organization. If you want to find out more, don’t hesitate to contact us!